• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
RE: Is there a way to "bridge" TCP/IP sockets?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Is there a way to "bridge" TCP/IP sockets?


  • Subject: RE: Is there a way to "bridge" TCP/IP sockets?
  • From: Satish Kilaru <email@hidden>
  • Date: Tue, 23 Nov 2010 14:07:36 -0500
  • Acceptlanguage: en-US
  • Thread-topic: Is there a way to "bridge" TCP/IP sockets?

I wish there is a set of APIs that take an input fd and output fd.

--Satish

-----Original Message-----
From: macnetworkprog-bounces+skilaru=email@hidden [mailto:macnetworkprog-bounces+skilaru=email@hidden] On Behalf Of Gordon Apple
Sent: Tuesday, November 23, 2010 2:06 PM
To: Mac Network Programming
Subject: Re: 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













******************Legal Disclaimer***************************
"This communication may contain confidential and privileged material
for the sole use of the intended recipient.  Any unauthorized review,
use or distribution by others is strictly prohibited.  If you have
received the message in error, please advise the sender by reply
email and delete the message. Thank you."
****************************************************************
 _______________________________________________
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

  • Follow-Ups:
    • Re: Is there a way to "bridge" TCP/IP sockets?
      • From: "Quinn \"The Eskimo!\"" <email@hidden>
References: 
 >Re: Is there a way to "bridge" TCP/IP sockets? (From: Jonathon Kuo <email@hidden>)
 >Re: Is there a way to "bridge" TCP/IP sockets? (From: Gordon Apple <email@hidden>)

  • Prev by Date: Re: Is there a way to "bridge" TCP/IP sockets?
  • Next by Date: Re: Is there a way to "bridge" TCP/IP sockets?
  • Previous by thread: Re: Is there a way to "bridge" TCP/IP sockets?
  • Next by thread: Re: Is there a way to "bridge" TCP/IP sockets?
  • Index(es):
    • Date
    • Thread