Re: Non-blocking method for reading writing objects to sockets
- From: Esmond Pitt <esmond.nospam.pitt@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 07 May 2005 09:53:03 GMT
Joseph Dionne wrote:
Technically there are not non blocking socket write methods in any language. There is either room enough in the socket write MCB to hold the data, allowing the method to return, or there is not enough room, and an error is returned to indicate a failure.
Technically and more accurately, there *are indeed* non-blocking socket write methods in both C and Java. In non-blocking mode, a socket write will put as much as it can of the application data into the socket send buffer without blocking and return that count, which can be zero if there was no room. This is not an error condition.
I don't know what is meant by 'MCB', it is not a term associated with sockets.
Either increase your transmit buffer size, which I believe defaults to 32kb
The default is platform dependent. It is 8k on Windows which is not sufficient.
, or find out why the data is not being transmitted to the network.
to which the answer can really only be that the client isn't reading fast enough, or at all.
.
- Follow-Ups:
- Re: Non-blocking method for reading writing objects to sockets
- From: Joseph Dionne
- Re: Non-blocking method for reading writing objects to sockets
- References:
- Non-blocking method for reading writing objects to sockets
- From: Sameer
- Re: Non-blocking method for reading writing objects to sockets
- From: Joseph Dionne
- Non-blocking method for reading writing objects to sockets
- Prev by Date: Re: Refresh HTTP java code
- Next by Date: Re: Non-blocking methods for transferring of Object
- Previous by thread: Re: Non-blocking method for reading writing objects to sockets
- Next by thread: Re: Non-blocking method for reading writing objects to sockets
- Index(es):
Relevant Pages
|