If everything is working properly, that would mean that you sent 16,777,216 bytes -- but I'd be shocked if that's really the case. It would either mean that you have a network that's faster than your CPU speed, or that you have your TCP send buffer set large enough to hold 16 MB of data -- which AFIAK is not allowed. (And even if it were, it would be seriously sub-optimal.)

More likely, your prototype for send() is wrong.

Or, perhaps you're corrupting memory.

Bill Wragg wrote:
I the sockets programming, we are getting a return value on the
send() api of 16,777,216. we are not sure what this is trying to tell
us.

Can anybody clue me in on what this means? TCPIP down? No
communication with client ?


This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].