Yes Eranga. That's is a valid use case. AFAIR, we discuss about this use case with Kevin.
@Kevin : WDYT? On Tue, Dec 22, 2015 at 12:03 PM, Eranga Perera <eran...@wso2.com> wrote: > Hi, > > How can we facilitate broadcasting to a web socket channel. If there are > multiple subscribers to that channel can we discriminate what messages > should go to each subscriber. I am thinking how a web socket chat > application be implemented with ESB mediation sequences. > > Eranga. > > On Tue, Dec 22, 2015 at 11:12 AM, Kevin Ratnasekera <ke...@wso2.com> > wrote: > >> Hi all, >> Here are the main use cases we found with related to WebSockets support >> in 410. >> >> 1. Websocket client to Websocket endpoint via ESB >> >> >> >> 2. Websocket client to HTTP endpoint via ESB >> >> >> >> 3. HTTP client to Websocket endpoint via ESB >> >> >> In each of the main use cases we need to support following sub use cases. >> >> 1. Header based routing scenario. This will be depend on the HTTP header >> specified at the initial handshake stage. >> 2. Content transformation scenario. As Websockets allows two way >> communication, we should be able to support two way mediation. >> >> Configuration should include two dispatching sequences on for >> bidirectional message flows. one for the client to backend mediation other >> for the backend to client mediation. >> >> 3. Support different content types for Websocket frames dynamic way. This >> is handled using Websocket Sub protocol. >> >> Regards >> Kevin >> >> On Tue, Dec 22, 2015 at 10:22 AM, Kasun Indrasiri <ka...@wso2.com> wrote: >> >>> Hi all, >>> >>> We are working on adding WebSockets support into ESB 4.10. For the >>> default HTTP transport we won't be able to incorporate it as HTTPCore >>> doesn't offer native WebSockets support. However, with the concept of >>> inbound endpoints/connectors we will be able to implement it by leveraging >>> Netty. So that means we have to use a dedicated HTTP port with WebSocket >>> support. >>> >>> Kevin can you please share the main WebSockets use cases that we came up >>> with. >>> >>> Thanks, >>> Kasun. >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Eranga Perera > *Senior Lead Solutions Engineer* > *WSO2, Inc. * > Mobile : +94 72 778 4250 > eran...@wso2.com > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
