+1. NIO is very important to creating a J2EE application server that is high performance. I/O (to file or network) is the biggest bottle neck in application servers (and just about everything else for that matter.). Using NIO should be a priority for this project.
"Noel J. Bergman" wrote: > Michael Remijan wrote: > > > I thought it would be assumed that the NIO packages would be the way to > go. > > I agree. The problem is that most people have no idea how to use NIO and > J2EE properly. I have had this discussion with the NIO lead, and I hope > that if we can provide a high signal, low noise opprotunity, he can provide > his input. As a start, I've a pending e-mail to him asking for an outline > of how he sees NIO employed in a J2EE container. I know how *I* believe it > should work (and works well), but I want to have his input for everyone. > > -- Noel -- Richard Monson-Haefel Author of J2EE Web Services (Addison-Wesley 2003) Author of Enterprise JavaBeans, 3rd Edition (O'Reilly 2001) Co-Author of Java Message Service (O'Reilly 2000) http://www.Monson-Haefel.com
