🚀 go-pugleaf

"Peter" <piotrtrzeciak@yahoo.com> wrote in message 
news:4798db8f$1@newsgroups.borland.com...

> When getting the binary data, first I get a piece that contains a
> binary code that says "image", and then I have to read that image
> (not knowing how big it is).

In that situation, there are only three reliable ways to detect when 
arbitrary binary data has finished being sent:

1) the server sends the data length beforehand (which it sounds like from 
yor descriptions that it is not)

2) the server sends a unique terminator byte/sequence to mark the end of the 
image data.  You would have to look for that terminator while reading so you 
don't accidentally receive too much data if another packet follows the image 
data right away.

3) the server disconnects the connection at the end of the file.

If the same socket connection is being used for both types of data 
transmissions, where your custom communication packets can arrive after the 
image is finished (without having to reconnect to the server), then #3 is 
not a viable option.  It has to be doing either #1 or #2 to ensure the 
integrity of the communication.

If the server is not doing any of those options, then the only other thing I 
can think of is to see if the image data itself has its own header that 
specifies the data size, assuming the same image format is being used each 
time.


Gambit