From: gah@ugcs.caltech.edu   
      
   Jorgen Grahn  wrote:   
      
   (snip)   
   >> I respectfully disagree. It enables the actual solution to   
   >> this problem by moving the retransmission logic into app space.   
      
   > What can you do with UDP which you cannot to with TCP?   
      
   Multicast.   
      
   > You can always reconnect and try to fix the situation, if   
   > the application protocol provides a way.   
      
   The point is, that with UDP the user program itself is responsible   
   for keeping track of retransmits and acks, as needed.   
      
   The other difference is that UDP maintains packet boundaries,   
   where TCP does not. With the change from NFS/UDP to NFS/TCP,   
   (and to RPC in general) there is the record marking standard to   
   allow including record boundaries in a TCP stream.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)