+1 for moving NIO code to Axis2. Btw at the moment we have a number of transports and all of them are in the core. And we know that Axis2 is totally independent of the transports so what if we move all the transports into a new module ?
Thanks Deepal > Asankha, > > Can we please move this transport to Axis2 in time for 1.3? > > thanks, > dims > > On 6/2/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote: >> >> Hi Raimund >> >> The default http/s client transport of Axis2 is based on the commons >> HttpClient. Please see the following links for some direct solutions for >> your issue. >> http://wso2.org/library/87 >> http://wso2.org/library/230 >> >> You may also find more articles through a search on the OxygenTank >> library. >> >> >> I know that Asankha has been working on a non-blocking HTTP client >> for Axis2 >> that re-uses connections. As I understand it this code is only in the >> Synapse release so far ( http://ws.apache.org/synapse). But I know >> there is >> a plan to get it into the core of Axis2. It is just an Axis2 >> transport so >> the code will work under Axis2. >> >> Asankha - am I right? >> >> Yes, the transport we developed for Synapse is tuned for a high >> throughput >> environment where you would actually gain from a non-blocking client >> implementation. Thus, if you just want to send a message and read its >> response, this transport is not right for you; as it will create an IO >> Reactor, a thread pool to handle the requests, and prepare to send >> multiple >> messages out reusing connections where applicable. We have plans to move >> this transport into Axis2, but the client side should be used with >> care for >> the above reasons. >> >> asankha >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
