Thanks all. To take this a step further - does/could the API Manager support APIs over websockets? I know this doesn't fit the current API Manager model well but I love the ability in the MGR to create/publish APIs and to control user access.
Thanks On Wed, May 29, 2013 at 9:56 PM, Supun Malinga <[email protected]> wrote: > Hi Mike, > > On Thu, May 30, 2013 at 7:10 AM, Ajanthan Balachandran > <[email protected]>wrote: > >> Hi, >> We are shipping Websocket samples(java) with wso2 as 5.1.0 please have a >> look at [0] and [1]. >> Hope this will help you. >> Thanks >> >> [0] >> http://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/products/as/5.1.0/modules/samples/common/webapp/src/main/java/websocket/ >> [1] >> http://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/products/as/5.1.0/modules/samples/common/webapp/src/main/resources/websocket/ >> > >> On Thu, May 30, 2013 at 7:04 AM, Nuwan Bandara <[email protected]> wrote: >> >>> Hi, >>> >>> App Server is on top of Tomcat 7.0.4 + which supports websockets, if not >>> jaggery you can write it in java, and the docs are at [1] from tomcat >>> >> > +1. We do have websockets support. > The sample Ajanthan pointed out ships with the default deployed example > webapp in AS. > Basically in AS it should work just as it works in tomcat. So tomcat > documentation is good enough to refer. > > thanks, > > >>> Regards, >>> /Nuwan >>> >>> [1] http://tomcat.apache.org/tomcat-7.0-doc/web-socket-howto.html >>> >>> >>> >>> On Thu, May 30, 2013 at 3:55 AM, Mike Stoddart <[email protected]> wrote: >>> >>>> 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 >>>> >>>> >>> >>> >>> -- >>> *Thanks & Regards, >>> >>> Nuwan Bandara >>> Technical Lead & Member, MC, Development Technologies >>> WSO2 Inc. - lean . enterprise . middleware | http://wso2.com >>> blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 >>> 9629 >>> * >>> <http://www.nuwanbando.com/> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> ajanthan >> -- >> Ajanthan Balachandiran >> Senior Software Engineer; >> Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ >> >> email: ajanthan <http://goog_595075977>@wso2.com; cell: +94775581497 >> blog: http://bkayts.blogspot.com/ >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Supun Malinga, > > Senior Software Engineer, > WSO2 Inc. > http://wso2.com > http://wso2.org > email - [email protected] <[email protected]> > mobile - 071 56 91 321 > > _______________________________________________ > 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
