On Tue, 2005-12-13 at 13:41 -0500, David Smiley wrote: > Last I recall, the HTTPClient team abandoned the idea of an NIO based > HTTPClient implementation since testing that Oleg did turned up poor > results. >
David, This is not exactly what the outcome was. So far I have seen no evidence of NIO offering any advantages compared to classic IO for _blocking_ HTTP, that is when the request / response content is to be produced / consumed using OutputStream / InputStream interfaces. HttpComponents will support NIO as a separate module for event driven (non-blocking) HTTP API Hope this clarifies things Oleg > I happened upon some information today which may cause the HTTPClient > team to rethink this: > http://weblogs.java.net/blog/jfarcand/archive/2005/06/ > grizzly_an_http.html > It's a blog about "Grizzly", an HTTP Listener using NIO for GlassFish. > It's worth reading all of it. > > ~ David Smiley > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
