Humm, I defintely do not want to do NIO for M4 and do not want to require JDK5 for SSL until its more on the back burner. I prefer refactoring the entire framework not to require a 1:1 correllation between threads to connections as the main stream protocol. However, I'm thinking you're right that might be best done in parallel (if you look I have an NIOServer in CVS already which started that) just to avoid a labor constraint vs a period with a non-working server or some kind of massive long running CVS transaction... The new non 1:1 correlation stuff ought to work for both non-blocking and blocking IO and eventually the mainstream stuff should be deprecated for it. I suggest looking at the work being done on Tomcat 5.5's HTTP11 and new AJP connector stuff for a guide on how to pull that off. I think they manage to do that W/O NIO!!! Thoughts?
-Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875313#3875313 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875313 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
