Asankha Very cool! I think this is a key feature for Synapse - because it means we can scale up to any workload.
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. +1 Paul On 9/28/06, Ruwan Linton <[EMAIL PROTECTED]> wrote:
Hi Asankha, +1 from me. Ruwan. On 9/28/06, ant elder <[EMAIL PROTECTED]> wrote: > Sounds really good to me so I'll be watching and happy to help. > > ...ant > > > > On 9/28/06, Asankha C. Perera <[EMAIL PROTECTED] > wrote: > > This is just to let everyone know that I have started work on a basic > > non-blocking http/s transport implementation for Synapse (and Axis2). > > Some weeks back I was looking into AsyncWeb and HttpClient/HttpAsync > > projects, and built a basic non-blocking listener for Synapse around > > AsyncWeb. However, as I was yet unable to find a non-blocking client > > implementation from either of those projects that I could use, I decided > > to try writing a "basic" http 1.1 transport which will not be dependent > > on any other projects. I am currently working on the listener and > > chunking support and I hope to finish first cut rather soon. I will try > > to incorporate this into Synapse as soon as I get the client side > > working, and hope to receive feedback from all of you as non-blocking IO > > is something that is really important to Synapse. > > > > asankha > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
