cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aki Yoshida <elak...@gmail.com>
Subject Re: SOAP over WebSocket
Date Tue, 29 Apr 2014 13:15:13 GMT
Hi Przemyslaw,
Andrei's blog (the one linked in his earlier reply
http://ashakirin-cxf-async.blogspot.de/) has some examples about
asynchronous soap calls over HTTP. But the limitation of this approach
is that you will need two separate HTTP connections: one from the
client to the service and the other from the service to the client
(the so called decoupled endpoint).

If you can have these two connections, a conventional one shot request
and response interaction (I mean each invocation results in one
request and one response transferred at some time, not necessarily
synchronously) works fine with this decoupled endpoint approach.

If you use a websocket, you can run these two logical connections over
a single websocket.

And this is what is meant but the bottom entry in the todo list of the
cxf websocket wiki page, namely to utilizing the websocket connection
instead of opening a separate HTTP back connection for those decoupled
scenarios. I think this probably will work with some minor
modification in the current code. We need a dedicated decoupled URI
name to indicate back conduit associated with the socket at the server
side.

regards, aki

2014-04-29 9:21 GMT+02:00 Przemyslaw Bielicki <pbielicki@gmail.com>:
> Hi Aki,
>
> Btw. what do you call asynchronous SOAP over HTTP? How do you get a response
> when it's ready?
>
> For me, HTTP is out of question as it's synchronous protocol, whatever
> tricks you make after :)
> My multiplex needs is a real bidirectional, full-duplex protocol.
>
> Cheers,
> Przemyslaw
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/SOAP-over-WebSocket-tp5742556p5743400.html
> Sent from the cxf-dev mailing list archive at Nabble.com.

Mime
View raw message