Could you? :) On 2013-05-29, at 3:26 PM, Paul Fremantle <[email protected]> wrote:
> Mike > > You can do it in Java as well as Jaggery. Not sure if we've documented that > yet :-) > > Paul > > > On 29 May 2013 20:25, Mike Stoddart <[email protected]> wrote: >> Thanks Paul. So it's not possible to run a Java based websocket server using >> the App Server or API Manager? Only Jaggery? >> >> >> On Wed, May 29, 2013 at 3:19 PM, Paul Fremantle <[email protected]> wrote: >>> Hi >>> >>> Yes we support websockets in Jaggery in the App Server now. The ESB is >>> adding support for websockets, but doesn't yet have it. >>> >>> Paul >>> >>> >>> On 29 May 2013 20:18, Mike Stoddart <[email protected]> wrote: >>>> I realise this may not be the right place to ask this question but it is >>>> architecture related so I hope you'll forgive me! >>>> >>>> I'm prototyping a new solution using WSO2 and one requirement I have is to >>>> provide real-time data updates to web users over a websocket. Our current >>>> solution uses websockets but I'm trying to use WSO2 to rewrite from the >>>> ground up. >>>> >>>> Someone mentioned on Stackoverflow that one could use a class mediator, >>>> but my understanding is that the mediator is uni-directional and not >>>> flexible enough. Though mediators are for the ESB, which doesn't actually >>>> solve the problem of allowing a websocket connection. >>>> >>>> I have a custom Java application that runs on a server, which stores data >>>> in an in-memory Hazelcast grid. I need to serve this data to web clients >>>> over a websocket. >>>> >>>> Is there any way in WSO's API Manager or Application Server to support >>>> websocket connections in this manner? If not, are there any plans to >>>> implement this and how might it be done? >>>> >>>> Thanks >>>> >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >>> >>> -- >>> Paul Fremantle >>> CTO and Co-Founder, WSO2 >>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>> >>> UK: +44 207 096 0336 >>> US: +1 646 595 7614 >>> >>> blog: http://pzf.fremantle.org >>> twitter.com/pzfreo >>> [email protected] >>> >>> wso2.com Lean Enterprise Middleware >>> >>> Disclaimer: This communication may contain privileged or other confidential >>> information and is intended exclusively for the addressee/s. If you are not >>> the intended recipient/s, or believe that you may have received this >>> communication in error, please reply to the sender indicating that fact and >>> delete the copy you received and in addition, you should not print, copy, >>> retransmit, disseminate, or otherwise use the information contained in this >>> communication. Internet communications cannot be guaranteed to be timely, >>> secure, error or virus-free. The sender does not accept liability for any >>> errors or omissions. >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > [email protected] > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other confidential > information and is intended exclusively for the addressee/s. If you are not > the intended recipient/s, or believe that you may have received this > communication in error, please reply to the sender indicating that fact and > delete the copy you received and in addition, you should not print, copy, > retransmit, disseminate, or otherwise use the information contained in this > communication. Internet communications cannot be guaranteed to be timely, > secure, error or virus-free. The sender does not accept liability for any > errors or omissions. > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
