Michele AsyncWeb has some HTTP client code but its in scratch and hasn't been touched in a while.
MINA supports anything you want, but you have to write the HTTP handling code. That is effectively what AsyncWeb is - HTTP on top of MINA. The Jakarta HTTPComponents HTTPCore NIO extensions (http://jakarta.apache.org/httpcomponents/index.html) are basically an equivalent to asyncweb built directly on top of the Java NIO library. They support both client and server side which we needed in Synapse. They also can be layered on top on MINA if there is a need to. Paul On 2/14/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Paul, what do you mean when you say "AsyncWeb doesn't support a client model"? And what about Mina? Thanks, Michele On Tue, 2007-02-13 at 19:55 +0000, Paul Fremantle wrote: > Michele > > We (the Synapse team) have written a pure non-blocking HTTP transport > for Axis2. Its currently in the Synapse repository, but we will check > it into the core Axis2 SVN when its stable. > > However, I wanted to clear up the asynchronous model. This isn't a > clear area by any means! > > The current Axis2 with Addressing is actually already asynchronous. > What happens is that if the replyTo address is a real HTTP URL > (useSeparateListener), then the client will start up a mini HTTP > server. The service will respond instantly with an HTTP 202 OK > (accepted message but not yet processed), and the HTTP connection will > be closed. When the response is ready, the server will open a new > connection to the client's HTTP server and pass the response over > that. > > The reason we wrote the non-blocking transport is that we wanted to be > asynchronous even in the case where WS-Addressing ISN'T being used. In > other words, the client has an open socket to the server, but we > didn't want to block a thread waiting for the socket. > > We looked at both Mina and AsyncWeb but AsyncWeb doesn't support a > client model, so we based our code on the Jakarta HTTPCore project > which also has NIO support. > > BTW Another truly asynchronous protocol we support is SMTP. > > Paul > > On 2/13/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > the addressing module allows for asynchronous messaging. However the > > used transport mechanisms are synchronous (at least tcp and http). Since > > alternatives exist (e.g. [1, 2]), is there any future plan to take > > advantage of fully asynchronous computation? > > > > > > Thanks, > > Michele > > > > > > [1] http://mina.apache.org/index.html > > [2] http://docs.safehaus.org/display/ASYNCWEB/Home > > > > > > --------------------------------------------------------------------- > > 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]
-- 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]
