Hi Irunika, +1 for the idea. As you mentioned we need to have a separate registry for websockets. We need support this for both OSGi and fat jar mode.
Thanks On Wed, Dec 7, 2016 at 3:31 PM, Irunika Weeraratne <[email protected]> wrote: > Hi, > I'm currently working on the implementation of WebSocket support for MSF4J. > > *Overview* > > > Currently, Carbon-Transport only supports HTTP. So we need to give it the > ability to handle WebSocket Frames. > Also, we are planning to use existing Carbon-Messaging to process incoming > messages. But in WebSocket, a response for a request is not a must. User > has to handle it if there is a need of sending a response. > Also, we need to give the user the ability to do server pushes using the > WebSocket Sessions and to do so we need to have the reference of Netty's > Channel Handler Context. > > In MSF4J > > - Need a separate Registry to register WebSocket EndPoints since > WebSoocket EndPoints are different from MicroServices > - Message Processor gets the correct EndPoint from the registry and > dispatch the message > > > Any thoughts? > > Thanks & Best Regards, > Irunika > *Irunika Weeraratne* > *Software Engineer | WSO2, Inc. <http://wso2.com/>* > *Email : [email protected] <[email protected]>* > *LinkedIn : https://lk.linkedin.com/in/irunika > <https://lk.linkedin.com/in/irunika>* > *Mobile : +94712403314 <+94%2071%20240%203314>* > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com About http://about.me/thusithathilina <http://wso2.com/signature>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
