On 11/25/05, Bill Barker <[EMAIL PROTECTED]> wrote: > Urm, APR uses blocking sockets. It uses APR to get around the fact that (at > least with Sun's JVM) blocking NIO sockets totally s*ck. > > Just look at the differences between the logic for ChannelNioSocket and > AjpAprProcessor.
>From what I've seen, apr does some reads with short timeout and some non-blocking in sendfile. I'm not interested in anything more complex for my experiments - at least not right now. I kind of expect blocking NIO sockets to be comparable with blocking java sockets and apr sockets for normal I/O - maybe 1.4 has some problems, but probably 1.5 or 1.6 will improve things. I could try reading the http request in non-blocking mode - but what's the point when the servlet will spend most of the time in service and writing to a blocking stream ? It's more interesting how to do some of the service() with a non-blocking socket, for files and few other things. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
