I have some code that reads an HTTP response into a large buffer.
I first read in the http header.
Then I read the data after the header into a large buffer. The buffer
(6096 bytes) is definitely large enough to read the entire contents of
the data from the http response. On a few treos (out of 1000's),
sometimes all of the data is not read into the buffer even though it is
large enough. So the next time i do a receive in a later function, i
get the rest of the data.
I noticed in the http header that the transfer-encoding is "chunked".
How do i properly read the data in using netlibreceive when I have no
idea how much data I am going to get. Do I just keep calling
netlibreceive until I get 0 bytes read? I assumed that getting 0 bytes
back from a netlibreceive indicated the remote host closed the socket.
Thanks
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
