aa5dd7e3   
   From: barmar@alum.mit.edu   
      
   In article   
   <472a48a7-cd68-4c89-9bad-6a2a4e28dca8@c36g2000yqn.googlegroups.com>,   
    Jorge  wrote:   
      
   > On Mar 3, 7:04 pm, Martijn Lievaart  wrote:   
   > > On Tue, 03 Mar 2009 12:59:10 -0800, Jorge wrote:   
   > > > Hello,   
   > >   
   > > > I am researching the most efficient method for streaming text over the   
   > > > internet. The text is compressed. Currently, I am zipping the text, and   
   > > > sending it over a tcp socket. This is a "real-time" application, so the   
   > > > zip file is sent in small pieces. Problem is, the header to payload   
   > > > ratio is quite large, so not very efficient.   
   > >   
   > > On the risk of being obvious, how about not zipping?   
   > >   
   > > OTOH, you are saying 'his is a "real-time" application, so the zip file   
   > > is sent in small pieces.'. This does not make sense. Care to explain?   
   > >   
   > > M4   
   >   
   > Thanks for your reply. Let me clarify my situation:  I start with a   
   > block of text.   
   > This block of text is compressed using ZLIB compression. The   
   > compressed   
   > file is then sent in small chunks over a socket to a recipient. ZLIB   
   > allows the recipient   
   > to begin decompressing the file incrementally, so they can decompress   
   > some of the   
   > text with each received chunk.   
   >   
   > What I am wondering is if there's a more efficient method for sending   
   > this data. i.e better   
   > compression method, better header/payload ratio. Would UDP be   
   > appropriate?   
      
   Why are you sending it in small chunks?  Send it in the biggest chunks   
   possible, to reduce the header overhead.   
      
   --   
   Barry Margolin, barmar@alum.mit.edu   
   Arlington, MA   
   *** PLEASE don't copy me on replies, I'll read them in the group ***   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)