Howdy, This is a common, and will become even more prevalent, question. ;) Mr. Schnack's answer explains a big part of it: right now we still have a lot of users using JDK's older than 1.4. A JDK 1.4 requirement is not possible for the 4.x branch of tomcat.
For Tomcat 5.x, there may be some discussion about this requirement, but I doubt it's going to happen. I also think most people working on tomcat recognize that the Apache http is great at what it does: so why re-invent the wheel? Especially when we barely have enough time to keep our wheel (tomcat) rolling... NIO fits in, IMHO (and I'm not speaking for any other developers) as a cool thing to do once we have a JDK 1.4 requirement, but insufficient by itself to make JDK 1.4 required. Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Felipe Schnack [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, December 11, 2002 6:14 AM >To: Tomcat Users List >Subject: RE: The future of Tomcat and java.nio > > Yes... would be really cool, I took a look at these packages... but I >think probably tomcat will implement them in a year or more, 1.3 is >being used by a lot of people yet. > >> It seems like Java 1.4's NIO package offers some very high-performance IO >> capabilities, such as select loops, which could allow Java to serve >static >> content as fast as Apache can. Will Tomcat be going in the direction of >> using a NIO-based connector that might incorporate these high-performance >> features? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
