Hi Gihan, Thanks for the updates and information, please see my comments below. > > Hi Andreas, > > Thanks for your comment. I prepared following list of use cases and I > will try to find more use cases. > > 1. As WebSocket protocol is based on full-duplex single connection > above suggested new transport will reduce unnecessary network traffic > and latency. Due to above advantages WebSocket transport will be a > preferable choice for performance centric web service applications. > > 2. As far as i know existing Axis2 transports are not designed to > support use cases like notification from server side. Of course Axis2 supports that, in Axis2 you can send message from one transport and receive the response from another transport. > Another use case of this suggested new transport is it can be used to > develop a server side notification application. As an example after > opening a connection client can wait to receive notifications from the > server. It already there, and we have implemented that using callbacks. > > 3. I don't have much knowledge about Apache Synapse project but it > looks like suggested new transport can be used with Apache Synapse > too. I found following page from Apache Camel web site > (https://camel.apache.org/websocket.html) may be suggested new > transport can be used to develop similar use cases.
I am not sure who wants to do streaming application on top of very expensive message format like SOAP. So this transport is YAGNI to me. But if you really want, go ahead and add support for WebSocket. This is not mean to discourage you, but I do not see a real use case of a new transport. Deepal > > 4. Additionally following two pages contain number of other > advantages of WebSocket. > > https://www.websocket.org/quantum.html > https://www.engineyard.com/articles/websocket > > Regards, > > Gihan > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org