45f070b0   
   From: gah@ugcs.caltech.edu   
      
   Jorge wrote:   
      
   > To clarify, the chunks are small so that the recipient   
   > can receive them in "real time".   
   >  I am streaming financial market data. The recipient   
   > must receive the data in a timely fashion.   
   >   
   > Is there a better protocol than TCP for this type of application?   
      
   If the data is naturally chunked, and you would rather lose   
   whole chunks and keep the rest coming than waiting for the lost   
   chunk before continuing (which sounds to me like market data)   
   then UDP packets containing compressed chunks might be best.   
      
   With TCP, if one packet is lost you won't get any data sent   
   after that until it is retransmitted after the sender   
   receives the NAK.   With UDP, you still get later data, and   
   your program must request the retransmission.   
      
   TCP of a gzipped file works well for file transfer when you   
   want all or nothing, or at least no holes in the middle of the   
   data stream.  That doesn't seem as appropriate for market data.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)