From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Cross Message-Id: <200111271859.NAA16425@augusta.math.psu.edu> To: 9fans@cse.psu.edu Subject: Re: [9fans] Nagle algorithm In-Reply-To: <87bshowweg.fsf@becket.becket.net> References: <20011126112312.80AC9C7901@cesium.clock.org> <200111261928.OAA12147@augusta.math.psu.edu> Cc: Date: Tue, 27 Nov 2001 13:59:06 -0500 Topicbox-Message-UUID: 2b588574-eaca-11e9-9e20-41e7f4b1d025 In article <87bshowweg.fsf@becket.becket.net> you write: >cross@math.psu.edu (Dan Cross) writes: >> It has to do with abstraction, on one hand, and proper seperation >> of function. The TCP has no business trying to guess what my >> application is doing; that's for my application to decide. TCP >> should be abstracted away from that stuff. > >But now, under your model, in order to get adequate network behavior, >your application needs to know things like the MSS! No, it doesn't. It just has to pick a reasonable default. I have yet to hear a justification of why buffering in the user land libraries or applications has to know about the MSS to get ``adequate network behavior.'' - Dan C.