× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



>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.

It isn't the iSeries; it's the network.  Depending on the route and routers,
TCP/IP can break a packet into smaller ones as it sees fit.  That's just the
way it works.

Buck Calabro
Commsoft; Albany, NY
Visit the Midrange archives and FAQ at http://www.midrange.com
"Where so many hours have been spent convincing myself that I am right,
 is there not some reason to fear that I may be wrong?" -- Jane Austen
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.