Re: TCP double connections bad idea?
- From: David DiNucci <dave@xxxxxxxxxx>
- Date: Tue, 11 Apr 2006 12:23:38 -0700
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
.
- References:
- TCP double connections bad idea?
- From: Andersen
- TCP double connections bad idea?
- Prev by Date: TCP double connections bad idea?
- Next by Date: ANN: CompTorrent: Applying BitTorrent Techniques to Distributed Computing
- Previous by thread: TCP double connections bad idea?
- Next by thread: ANN: CompTorrent: Applying BitTorrent Techniques to Distributed Computing
- Index(es):
Relevant Pages
|
|
