Ok, so let me double check: the low level socket in sandbox is allways read after a poll() / select(), and never with a blocking read() ?
After the poll(): the Comet servlet, in a tomcat thread will be able to call read() in the input stream, and that will return data or 0 if no more data is available ( or - call isReadable() and then read(), or whatever else - but the socket will not be put in blocking mode ) ? If this is true for sandbox - big +1. Costin On 6/15/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:
Filip Hanik - Dev Lists wrote: > Please note, that neither Remy nor I have yet really talked about non > blocking reads, so you might think sandbox is non blocking, well it is not. > It is buffering, but not non blocking. a true non blocking read, would > require a rewrite of all the buffer filters to keep state between read > invocations. It is non blocking, as the low level read is always non blocking (in the sandbox design). Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
