Re: A basic non-blocking http/s implementation for Axis2/Synapse

[Asankha C. Perera]

Hi Oleg Sure, I will take a look at the NIO extensions again.. I think I looked at the wrong place (HttpAsync) earlier :-( regards asankha Oleg Kalnichevski wrote: On Fri, 2006-10-06 at 18:21 +0530, Asankha C. Perera wrote: Ant Yes I checked both AsyncWeb and thier code in the scratch and HttpAsync as well which is from HttpCore http://www.mail-archive.com/httpclient-dev@jakarta.apache.org/msg04400.html There are both good and bad things about us implementing our own transport... asankha Asankha, HttpComponents is still very much an evolving project, so the scope of its modules has not been always clearly demarcated, hence the confusion. HttpAsync is intended to be a set of API that sits on top of HttpCore and uses _blocking_ I/O to implement asynchronous HTTP services, which makes it highly specialized, and as such usually it gets lower priority compared to HttpCore and HttpClient. If you want a non-blocking client / server HTTP implementation based on NIO, HttpCore should basically suffice. There is already NIO based transport layer in HttpCore NIO extensions and I am presently working on the event-driven protocol layer to put on top of it. All this code will make it into the next public release of HttpCore. Axis2 1.1 is already dependent on HttpCore. It is also dependent on HttpClient, next version of which will be based on HttpCore as well. So, I do not know what your special requirements are, but you might actually want to consider collaborating with us (Jakarta HttpComponents) in your development effort on non-blocking HTTP transport and / or consider re-using some of HttpCore protocol primitives, since they are already being used by other parts of Axis2. This way Axis2 could indirectly benefit from your contribution. Anyways, take it for what it is worth. Cheers, Oleg ant elder wrote: On 9/28/06, Paul Fremantle <[EMAIL PROTECTED]> wrote: <snip> Is there any code we can re-use from - for example - commons http? It seems a shame to have to re-implement the HTTP protocol just because the IO has changed. I also wondered about this. From the description of HttpCore it sounds like they're trying to make something Synapse should be able to use, have you had a look at that? http://jakarta.apache.org/httpcomponents/http-core/index.html ...ant --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]