in reply to Reading a GZIP network stream

I am already not sure about the reading of the data from the network for binary data - I have used recv sofar only with text - does recv also work for binary data?

According to docs, if you didn't set anything special on socket with binmode(), it will receive bytes.

I don't know if it is important, but do all the message fit in 1024 bytes?

I'd also check compression/decompression starting with a simpler test: take a string, compress it, then decompress it and see if you received the original data back again. If it's fine, then try the same method on the socket.

You may also try with other modules, like IO::Uncompress::Gunzip.

Replies are listed 'Best First'.
Re^2: Reading a GZIP network stream
by weismat (Friar) on May 13, 2009 at 09:13 UTC
    I have found one error with reading the bytes as the first parameter of the receive is where the actual data goes.
    But I still think that I am not reading the full required set of bytes. What is the correct way to determine if there are more bytes to read ? Do I need to use select?

      If you're not reading all of the bytes, then the decompression is never going to work. I (and you also, apparently) have doubts that all of your data is fitting into 1024 bytes.

      Where is this data coming from? Did you write the server code? If not, then I don't know that I can help you. If yes, then you probably need to modify the server (and client) to follow some sort of sane protocol.

      Typically, a simple way to handle this is to send the length of the message in the first x bytes of the message. You can use 4 bytes (32 bits), or if that's too much or too little, adjust to your liking. Then instead of using recv, you'll have to use read or sysread in a loop until you've got all of your data.

      ## Warning: Incomplete and untested ## my $buffer; my $got_bytes = 0; while ($got_bytes < $total_bytes) { my $bytes = sysread $s, $buffer, $total_bytes - $got_bytes, $got_b +ytes; }