[e2e] tcp connection timeout

[Joe Touch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Vadim Antonov wrote:
> On Fri, 3 Mar 2006, Joe Touch wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>>
>> Vadim Antonov wrote:
>>> On Fri, 3 Mar 2006, Joe Touch wrote:
>>>
>>>> Please explain the 20MB case.
>>>>
>>>> AFAICT, that only happens when the receiver window is 20MB, AND:
>>> TCP state is not the only state kept around when a connection is open. 
>>>
>>> I thought that it was obvious that I meant the user-space state.
>>>
>>> --vadim
>> Wouldn't that be the user-space (application-layer)'s decision then?
> 
> It does not matter whose decision it is as long as you have a way of 
> purging it for dead connections.  It was merely a counter-argument to the 
> assertion that dead connections are "cheap". There are numerous cases when
> they are not.

We HAVE a way for applications to purge resources for connections THEY
think are dead - CLOSE or ABORT.

> I think it is always a good idea to look at the whole picture, because 
> concentrating on one layer is bound to mislead.

Indeed - I (and others) are suggesting TCP isn't the place to focus in
this case.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFECKs2E5f5cImnZrsRApsqAKCz8i/da3S8Rd5XCpR1DUcV3w8vUACg6fUW
XqnS3By02YcJqQL7lC3rc18=
=26x+
-----END PGP SIGNATURE-----