Peter Huber wrote:
>
> I clearly see and like the advantage of nio package
> over io, but it's 'only' a little step further.
>
I wrote a dirty little HTTP server using the nio
classes, and did some quick benchmarking against
Apache and thttpd. The results indicate that it's
a fairly big step forward in Java's ability to
handle reasonable numbers of connections without
bogging down in infinite-number-of-threads-land.
The idea isn't to replace Zeus on your 100 gazillion
dollar 32 processor wonder machine. The idea is to
avoid having to install Apache on your departmental
server just because you have to serve a few static
files in addition to servlets. The new nio classes
allow you to do that quite nicely.
Check out specifically FileChannel.transferTo and
MappedByteBuffer in addition to Selector. There are
some bells and whistles missing (like the ability
to CORK with transferTo), but they appear to get the
job done quite nicely for the vast majority of users
who don't need to fill a multi-gigabit pipe or
handle 500k simultaneous users...
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
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
