|
>Dan: Speaking from experience with other TCP/IP/Sockets libraries, but not the AS/400's: That's the way it works. If you have to know how much data to expect at the receiver, you must devise some header of your own design that conveys this information to the receiver from the sender. I don't know the socket library that you are using, but for many you can control (a little) some of the behaviour using setsockopt() calls. See the documentation for setsockopt(), re: TCP_NODELAY, SO_SNDBUF, and SO_RCVBUF. The reason for the different results on different machines can be explained by having different defaults for some of the above values (or equivalent/others) in the TCP/IP stack that you are using. Good luck! JLM +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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 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.