Hi Oleg, > At this point of time I tend to think NIO on the client side makes no > sense at all, as it makes little sense for an HTTP client to keep > hundreds of connections open.
I agree. Server-side use will also be confined to very special purposes, as common server-side APIs like Servlet API and Portlet API are based on traditional IO. But special purpose server applications is just the niche where HttpComponents can shine. > No need to review the NIO code. Just take a look at the public API and > let me know if it "feels" okay. Ok, I'll find time for that. > I do not expect any changes in the HttpServerConnection. It is the > client side of the story that needs work. Once we have stabilized a new design on the client side, we should at least consider to restructure the server side based on the same principle. Implementation classes at least - AbstractHttpConnection will loose it's purpose, I'm afraid. > I'll start checking in classes, which I have a certain degree of > confidence in not being completely wrong. Go ahead. I'll let you know about JavaDoc warnings :-) cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
