|
Home > Archive > Distributed Computing > April 2006 > TCP double connections bad idea?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
TCP double connections bad idea?
|
|
| Andersen 2006-04-11, 8:06 am |
|
What is wrong with designing your applications using one TCP socket in
each direction (I.e. dont make use of the bidirectionality of TCP). I.e
node A and B want to communicate, have one socket for communication from
A->B and another socket for communication from B->A.
The design avoids several problems, but I want to know what are the
negative consequences.
| |
| David DiNucci 2006-04-18, 12:11 am |
| Andersen wrote:
>
> What is wrong with designing your applications using one TCP socket in
> each direction (I.e. dont make use of the bidirectionality of TCP). I.e
> node A and B want to communicate, have one socket for communication from
> A->B and another socket for communication from B->A.
>
> The design avoids several problems, but I want to know what are the
> negative consequences.
I'd be interested in knowing the perceived advantages (problems avoided).
The first thing that comes to mind is that a two-way connection allows
returning acks to be piggybacked onto packets headed in the other
direction, and only one "stay alive" protocol needs to be active. But
for all I know, these decisions may be shared among all connections
between two hosts at a lower networking layer. (Disclaimer: I wouldn't
call myself a networking expert, though I've built reliable protocols on
top of UDP.)
A better place to get an answer might be comp.protocols.tcp-ip
-Dave
|
|
|
|
|