> Has there been any discussion on building a connector around the NIO package > in Java 1.4?
Yes. > I just read an interesting article in the latest Java > Developer's Journal about a web server built using this support and it > looked excellent. Using NIO would lower the number of required threads No, because the J2EE model mandates 1 thread <-> 1 request, and implies blocking IO (because the servlet will use an IS to read the request body no matter what). You can save a few threads during the time you wait between requests when using HTTP/1.1 connection persistence, but IMO it is not worth the throughtput loss and increased complexity of the HTTP/1.1 processor. > and buffers/objects that would need to be created. Tomcat already uses NIO-like reusable buffers, so there's no gain here (and C2B conversion will automatically use the new NIO converters). > Obviously it would be > dependent on 1.4, so it could not be the default connector. But, I believe > it would be nice to have the option. I'm quite sure the connector is no longer a limitation for real world webapps (Jasper is, assuming you're not using a database too much, so we're now working on that instead). OTOH, NBIO is really cool if you want to build a HTTP/1.0 or HTTP/1.1 file server. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
