Hi All, During implementation an issue was raised on using the curl client to send messages to the echo server. Therefore in order for the Java echo server to be able to accept messages from the curl client I have included a JAX- RS web service in between.
I have attached a diagram showing the updated design for the POC. Regards. Sabra. On Fri, Jun 19, 2015 at 2:13 PM, Sabra Ossen <sabra...@gmail.com> wrote: > Hi Manjula, > > Okay, then I will focus on step 1 and 2. And I will also check if the > latest AS release supports web sockets, failing which I will proceed with > AS 5.1.0. > > Thanks for the help. > > Regards. > > On Fri, Jun 19, 2015 at 11:26 AM, Manjula Rathnayake <manju...@wso2.com> > wrote: > >> Hi Sabra, >> >> These notes cover most of the items of we discussed. >> IMO, we do not need to consider step 3 at this point of POC. It is more >> related to AF Wall functionality. After completing POC, we will have a demo >> and discuss next steps. >> >> I was checking if latest application server supports web sockets but for >> AS 5.1.0, I could find some samples at [1]. >> >> [1]. >> https://svn.wso2.org/repos/wso2/carbon/platform/tags/4.1.0/products/as/5.1.0/modules/samples/common/webapp/src/main/java/websocket/ >> >> thank you. >> >> >> On Fri, Jun 19, 2015 at 11:18 AM, Sabra Ossen <sabra...@gmail.com> wrote: >> >>> Hi All, >>> >>> Currently in AF the FE (AF Wall) polls the BE (Social Component) to >>> identify and display notifications. >>> >>> The method proposed below is for $subject. The PoC for $subject is as >>> follows. >>> >>> *1) The curl client pushes data to the Java Echo Server (Hosted in WSO2 >>> AS) which then writes to the client browser through the web socket.* I >>> have attached a screen shot of a diagram showing the design. Nginx is used >>> to emphasize on load balancing and as a proxy. >>> >>> 2) With the completion of the above step then we move on to the next >>> step of *creating a listener for the Social API replacing the Java Echo >>> Server* and then port the code to AF. >>> >>> 3) One issue raised during discussion of $subject was the >>> *rendering of relevant content in a switch happening between two pages.* >>> For example, the curl client pushes msg1 to page1 and msg2 to page2. >>> During this switch the same web socket connection should be used rather >>> than restarting a new connection. >>> >>> @Dimuthu and Manjula, Please let me know if I have missed anything and >>> any further opinions you have on $subject. >>> One clarification I require is that should the point mentioned in step 3 >>> be completed, after step 1 or after completion of steps 1 and 2. >>> >>> Thanks in advance. >>> >>> -- >>> Sabra Ossen <http://lk.linkedin.com/in/sabraossen> >>> Undergraduate | Department of Computer Science and Engineering >>> University of Moratuwa >>> Sri Lanka >>> >> >> >> >> -- >> Manjula Rathnayaka >> Software Engineer >> WSO2, Inc. >> Mobile:+94 77 743 1987 >> > > > > -- > Sabra Ossen <http://lk.linkedin.com/in/sabraossen> > Undergraduate | Department of Computer Science and Engineering > University of Moratuwa > Sri Lanka > -- Sabra Ossen <http://lk.linkedin.com/in/sabraossen> Undergraduate | Department of Computer Science and Engineering University of Moratuwa Sri Lanka
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
