Re: Memory allocation

[PatrickConner@xxxxxxxxxxxxxxxxx]

This is the reason for my original question. I'm reading an XML document which varies in size per transaction. Many times it runs up to 200K. I have my read set to recieve 32K per read. However, the first read receives 108 bytes and most of the time the next reads will receive 16,832 bytes. My sockets program is communicating with a web-server from a Windows box (if that helps). Also, the 16,832 thing is not consistent. For an example: I received a document that took four reads that arrived in the following sequence. First read: 108; Second read: 16,832; Third read: 16,832; Fourth read: 8,586. I then received the exact same document again and it arrived as 108; 21,152; 16,832; 4,266. It seems to me that the iSeries is buffering the input somewhere.

Patrick Conner
www.ConnecTown.com
(828) 244-0822

 
You wrote:

The 3rd parameter to the read() (or recv()) API tells the system the
maximum number of bytes to read in that operation.


On Mon, 23 Jul 2001 PatrickConner@parkdalemills.com wrote:
>
> When reading a socket what determines the maximum size of data from a
> single read operation?
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---