-- Roland Weber <[EMAIL PROTECTED]> wrote: > 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
Actually, I think there are cases where this is not true: specifically, when server itself has to act as a client towards other systems. This is typically the way web services work: there are multiple layers of services, depending on other backend services. So, a server acting as a client may easily need to keep thousands of (usually high latency) connections open simultaneously And this is the specific case where NIO would be necessary for scalability: it doesn't help if server side can handle thousands of client-facing connections, if it can't serve those due to limitations with its own access-as-client. In fact, this is the main reason why I am very interested in HttpCore/HttpClient developments: for server-side NIO there are solutions, but for client-side there aren't. Anyway, just my 2c, -+ Tatu +- __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
