Hi Oleg, > Sure. Some people just insist on being able to write directly to the > output stream. I want to demonstrate that this is possible with the > HttpCore API. I am not trying to say this approach is any better than > using StringEntity.
Ok, then it is just the example which I don't like :-) > Now the Evil Plan (TM) is to start working on a asynchronous version of > HttpService that decouples the process of receiving HTTP requests, > generating response content and sending off resultant HTTP responses > using a fixed pool of worker threads. I am not sure how exactly this is > going to work (if at all) but I want to keep this idea on the back > burner for some while. Sounds pretty much like what I'm heading to on the client side with HttpDispatcher. Sooner or later (I'm afraid later) I'll reach the point where I have to look into NIO in order to avoid having one worker thread per connection just to detect incoming responses. Lifting NIO up to the API itself would probably require rewriting half of HttpCore. There's no point in thinking about that until we have much more contributors. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
