You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Przemyslaw Bielicki <pb...@gmail.com> on 2014/06/17 15:10:39 UTC
Re: SOAP over WebSocket
Yes, you need some kind of correlation Id in your SOAP message (ideally in
the header part)
But, I just learned that there is already existing subprotocol extension for
websocket called MUX whose goal is to multiplex multiple ws connections over
single TCP conection. In this case we have multiplexing on lower OSI layer
e.g. implementation
http://maven-repository.com/artifact/org.eclipse.jetty.websocket/websocket-mux-extension
I'm going to play withit and compare. Single TCP connection to handle
multiple clients is a great solution and it normally scaleas much better
than one connection per client.
--
View this message in context: http://cxf.547215.n5.nabble.com/SOAP-over-WebSocket-tp5742556p5745269.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: SOAP over WebSocket
Posted by Przemyslaw Bielicki <pb...@gmail.com>.
Ordering is not needed at all. Correlation ID is enough as I expect that some
requests will take more time that another and it's OK.
Anyway, thanks a lot for your inputs!
--
View this message in context: http://cxf.547215.n5.nabble.com/SOAP-over-WebSocket-tp5742556p5745365.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: SOAP over WebSocket
Posted by Aki Yoshida <el...@gmail.com>.
I think there is a gap between mux and what you will need for doing
async request-response calls.
With mux, you can have multiple websockets layered on a single socket
connection.
With that, you can queue requests and response multiplexed over a single socket.
But this still won't give you a request-response correlation for those
requests and responses that are exchanged asynchronously (unless you
add some restriction like the ordering of the messages).
regards, aki
2014-06-17 15:10 GMT+02:00 Przemyslaw Bielicki <pb...@gmail.com>:
> Yes, you need some kind of correlation Id in your SOAP message (ideally in
> the header part)
>
> But, I just learned that there is already existing subprotocol extension for
> websocket called MUX whose goal is to multiplex multiple ws connections over
> single TCP conection. In this case we have multiplexing on lower OSI layer
> e.g. implementation
> http://maven-repository.com/artifact/org.eclipse.jetty.websocket/websocket-mux-extension
>
> I'm going to play withit and compare. Single TCP connection to handle
> multiple clients is a great solution and it normally scaleas much better
> than one connection per client.
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/SOAP-over-WebSocket-tp5742556p5745269.html
> Sent from the cxf-dev mailing list archive at Nabble.com.