×
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 a socket server program. The client is sending 1869 bytes of data,
but the socket Read function only returns 1392 bytes, and on the
subsequent read it returns the remaining 477 bytes (1392+477=1869).
When I look at the TCP connection status via netstat *cnn I can see Bytes
In listed as 1869 but then paging down I see the Maximum Segment Size is
1392.
I've tried to use the set socket option for SO_RCVBUF to override the
number of bytes per socket read.
Funny thing is that if I disconnect the client, and re-issue the Socket
Accept to create a new socket, and then reconnect and resend the 1869
bytes, I get all 1869 bytes in one read. But then if I resend the same
data again it reverts back to the original problem (1392 bytes read first
time and subsequent 477 bytes read the second time).
How can I correct this so that I can in one read accept the entire string
of data sent by the client?
Regards, Jerry
Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.
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.