[e2e] Number of persistent connections per HTTP server?
touch at ISI.EDU
Tue Oct 15 09:34:06 PDT 2002
Vadim Antonov wrote:
> On Mon, 14 Oct 2002, Joe Touch wrote:
>>>Doing multiplexing within single TCP session effectively shares the timing
>>>and congestion control information between flows, which is a good thing
>>>(this can be achieved by storing that info on per-peer-host basis in the
>>>TCP stack, instead of TCBs - however, this technique breaks down in case
>>>of NATs which can make different boxes appear to be the same box, or in
>>>case of per-flow load sharing in the network).
>>Since the NAT likely shares the majority of the path that determines RTT
>>and bandwidth, it won't hurt sharing.
> Very often, this is not the case. What you have in a typical organization
> is single NAT/firewall, and a VPN behind it. Quite often parts of that
> VPN are on different continents :)
That is just a broken installation for a number of reasons. How it hurts
sharing is the least of its problems.
More information about the end2end-interest