eeea6e7a   
   From: rick.jones2@hp.com   
      
   David Schwartz  wrote:   
   > The issue is that if your accumulation level isn't larger than the   
   > largest amount of data that fits in a single segment on the wire,   
   > Nagle will engage. If you accumulate, say, 1024 bytes and more than   
   > that fits in a packet, if you send 1,512 bytes, the last 512 bytes   
   > will be Nagled.   
      
   Be very careful with "send" (and I will be careful with reading) - I   
   nearly went asymptotic thinking you were trying to suggest that a   
   send() call of 1512 bytes would hit Nagle :)   
      
   Yes, if the accumulation point is < MSS one might run into Nagle.  If   
   one is interposing with the broken library anyway, and "know" the   
   quantity of data presented to TCP will not be epsilon each time, it   
   might be acceptable to actually have the interposed code disable Nagle   
   - it is, afterall, doing essentially the same thing Nagle would be   
   doing.   
      
   rick jones   
   --   
   The glass is neither half-empty nor half-full. The glass has a leak.   
   The real question is "Can it be patched?"   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)