|
Hi Rick,
The programmer responsible for the socket has written a few before but they have had this same issue. The 'fix' was to increase the buffer size on the sending Windows system.
That's not really a fix. :) But I think you knew that, because you put 'fix' in quotes! That's a rather fragile workaround... it may make the connection fast enough that the errors don't show up for awhile, but lots of other things can happen that will cause them to resurface later.
The program needs to be written properly. It's really not any harder, and doesn't take any additional work, to write it properly. It's just a matter of educating the programmers so they know how to write the code...
BTW, we are using TCP-IP for the communications.
TCP/IP is the "blanket term" for any of the protocols in the suite. They include TCP, UDP, ICMP, IP, TCP6, UDP6, ICMP6 and IPv6. I guess I was looking for a more specific answer than "one of these 8 protocols".
I'm going to assume that, like most people, you're using the TCP protocol.
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.
midrange.com
