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:/
Hi Alek,
The value of the non-blocking approach here is not to support longer
asynchrony on the client side but rather simply more clients being
mediated thru Synapse.
Without this the # of messages that synapse can mediate simultaneously
is bound by the number of threads it can spawn. Clearly no
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 +, Paul Fremantle wrote:
> Michele
>
> We (the Synapse team) have written a pure non-blocking HTTP transport
> for Axis2. Its currently in the Syn
Alek
I agree that the blocking socket doesn't work as reliably as WS-A.
However, many clients still only support basic SOAP which is why we
added the Non-Blocking approach to Synapse.
Paul
On 2/13/07, Aleksander Slominski <[EMAIL PROTECTED]> wrote:
Paul Fremantle wrote:
> Michele
>
> We (the S
Angel
No, the WSA approach doesn't work through firewalls with HTTP. We just
published a spec as part of the WSRM initiative that solves this
problem (WS-MakeConnection).
However, other protocols like SMTP and Jabber solve the firewall problem.
Paul
On 2/13/07, Angel Todorov <[EMAIL PROTECTED]
Hi Paul,
What about firewall issues and WS clients staying behind NAT ? Is this
possible with the current Axis2 WS-Addressing impl, if a client brings
up a HTTP server and the "real" server connects back to it ? Thanks.
Best,
Angel
On 2/13/07, Aleksander Slominski <[EMAIL PROTECTED]> wrote:
Pa
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
> cl
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
Hello Michele,
I would expect the addressing module to work with the jms transport.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it
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.
10 matches
Mail list logo
