On Thu, Apr 13, 2000 at 06:35:12PM +0530, Akshay Adhikari wrote:
> Hi,
>
> In what sense are TCP sockets full duplex? Sure, data can flow in each
> direction independent of the other direction, but it wont work if this
> happens at the same time.
>
> THat is, if a client and server process simultaneously send (thats
> full-duplex) one window's worth of data on their connection, theyll
> deadlock, each waiting for the other to acknowledge receipt, which is not
> going to happen.
>
> So the programming has to be symmetric right? One sends, other receives -
> that makes it half duplex. Could anyone shed some light on this?
I am routinely writing full duplex APPLICATIONS over TCP sockets.
One thread reads (and *only* reads), other one writes (and *only*
writes).
Things can also be done without threads by means of non-blocking
sockets, and local buffers. Fairly trivial.
> Thanks
> Akshay
/Matti Aarnio <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
