Hi all, During the implementation, I came across some issues. In Ballerina point of view, there can be multiple WebSocket client connectors for a given server endpoint. Which means according to the above diagram the step 9 is not valid for such a scenario. Because for a given server session there can be multiple client sessions available.
IMHO to avoid that we need to have a mapping in the application layer (Ballerina) rather than handling it in the transport layer. WDYT? Thanks, 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* *Lean . Enterprise . Middleware* On Mon, Jul 10, 2017 at 3:18 PM, Shafreen Anfar <[email protected]> wrote: > Hi All, > > Original purpose of this mail was to discuss websockets implementation > changes. Hence this mail :) > > With the new client-connector and server-connector api, it should be able > to return a webscoket session upon connection establishment. Since > websockets is full duplex both client and sever side implementations should > be symmetric. Hence, we are planning to alter the existing implementation a > bit. Suppose, we have a passthrue scenario where inbound and outbound > connections are websockets. In such case, what happens under the hood is > something as below, > > > > Basically what happens is when a client initiate a websockets handshake, > on the server side there will be a new SourceHandler instance. For that > SourceHandler instance, we will be associating the respective > client-session. Similarly on the client side there will be a new > TargetHandler instance for each websockets connection. For that > Targethandler instance will be associating the respective server-session. > None of these sessions will be shared between other users or services. > Numbers explain the order of events. > > Please let us know your opinion as well :) > > @Irunika - Please correct me if I am wrong. > > On Tue, Jul 4, 2017 at 6:14 PM, Irunika Weeraratne <[email protected]> > wrote: > >> Hi all, >> Current client connector is written to work with HTTP request-response >> model. But protocols like WebSocket are not work in that way. So it is >> difficult to implement and maintain the code with more complex logic in the >> application layer. >> This can be resolved by introducing new APIs to the Client Connector. >> >> Please find the doc below for the complete details >> https://docs.google.com/a/wso2.com/document/d/1FCO_-Q7hGR4u4 >> AWObTuuy5VwS2sXxKvYUDzkN5XCSqI/edit?usp=sharing >> >> Thanks, >> 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* >> >> > > > -- > Regards, > *Shafreen* > Software Engineer > WSO2 Inc > Mobile : 077-556-395-1 >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
