> > > In the future, the new (1.4) java.nio.* packages mean > that it should be possible to write an HTTP server just > as fast as Apache in pure Java. But we're not quite there > yet... > * Sorry for being off topic * Sorry, but I think you overestimate the nio package a bit. You can check out the new features with the beta of 1.4 As far as I get nio, it does not give you asynchronous IO the full scale like winnt and unix derivates provide with their systemcalls (e.g. completion queues for asynchronous operations are missing) Therefore I think that c/c++ solutions that take advantage of those features are and will always be faster than java, because they are closer to the machine in any aspect. And there are also portable c++ solutions like the great ACE-Framework that are not locked to just one platform. (can't recall the 'inventors' name, was it Doug Schmid) Don't get me wrong, I'm an enthusiastic java user and I clearly see and like the advantage of nio package over io, but it's 'only' a little step further. Peter ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
