since the the images are not rendered properly I am attaching the google document [1] herewith
[1] https://docs.google.com/document/d/1rPmJT-NVsPTC1SlUZUGw4gUQJjZ2R_K1rBIAY2a1dBc/edit Regards Kevin On Tue, Dec 22, 2015 at 11:12 AM, Kevin Ratnasekera <[email protected]> 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 <[email protected]> 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 [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
