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.
