Re: Is there a way to "bridge" TCP/IP sockets?
Re: Is there a way to "bridge" TCP/IP sockets?
- Subject: Re: Is there a way to "bridge" TCP/IP sockets?
- From: Gordon Apple <email@hidden>
- Date: Tue, 23 Nov 2010 13:05:35 -0600
- Thread-topic: Is there a way to "bridge" TCP/IP sockets?
I'm certainly no expert, having only just completed my first messaging
system for a remote control. However, the obvious problem is that sockets
are not continuous communication. TCP, especially, has potentially a
variable availability delay, so somebody has to do some buffering. I don't
think there is anything equivalent to a "pipe" that could directly connect
the two.
On 11/23/10 12:44 PM, "Jonathon Kuo" <email@hidden> wrote:
>
> On Nov 23, 2010, at 10:36 AM, Satish Kilaru wrote:
>
>> 1) Try doing that bucket-bridging in kernel.
>
> Heh, thats a bit to scary for me. One mistake and the system freezes.
>
>> 2) Why can't client A connect to Client B directly. That is highly scalable.
>> :-)
>
> The main process is supposed to be kind of a enabler. Client A and B can't see
> each other directly (maybe they're wireless or behind routers or whatever) so
> they connect to the Main process that connects the two. Maybe theres a better
> way to do this...
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Macnetworkprog mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden