Is it really an Apache License? If you click on the license link they mention CDDL and GPL2?
Other than the license issue, any idea what the stability or activity of this project is. Seems like its worth a look at least. ~Michael On Apr 10, 2011, at 7:32 AM, Nelson Silva wrote: > Atmosphere (http://atmosphere.dev.java.net <http://atmosphere.dev.java.net/>) > has an Apache License (at least that's the one in GitHub) and v0.7 has: > > - Native GWT support > - WebSocket emulator support (Iike Flash) > - Easier integration with Guice > - Servlet 3.0 support > - Jersey support > - Atmosphere > Meteor > module > which allows > any > existing > Servlet > based > application > (Wicket, > JSP, > JSF, > etc.) > to easily > add > asynchronous > support > - Massive scalability with a Cluster plugin architecture (JGroups, > JMS/ActiveMQ, Redis, XMPP,i etc.) > - Runs on any Java based Web Server, including Tomcat, Jetty, GlassFish, > Weblogic, Grizzly, JBossWeb and JBoss, Resin, etc > > v0.8 due before the summer will have : > > - Socket.IO support > - Cometd 2.2.x support > > What do you think ? > > On 10-04-2011 10:16, Yuri Z. wrote: >> Then we can't use it. >> >> Sent from my iPhone >> >> On 10 באפר 2011, at 11:37, Scott Wilson<scott.bradley.wil...@gmail.com> >> wrote: >> >>> On 9 Apr 2011, at 22:49, Yuri Z wrote: >>> >>>> By the way, it seems that JWebSocket is licensed under LGPL, is it >>>> compatible with Apache license? >>> Nope. >>> >>>> 2011/4/10 Nelson Silva<nelson.si...@gmail.com> >>>> >>>>> Hi all, >>>>> >>>>> I'd really like to be able to create a WAIB WAR deployable in as many >>>>> servers as possible. >>>>> With Guice servlet injection and a proper GuiceServletContextListener we >>>>> can already have a WAR deployable on Jetty>= 7 but if we want to support >>>>> other servers websocket support really makes this difficult. >>>>> >>>>> I'd like to get everyone's input on jWebSocket vs Atmosphere vs Cometd in >>>>> order to try and develop an alternative RPC server. >>>>> >>>>> Having automatic negotiation between the client and the server and with >>>>> proper fallback mechanisms we could have WebSockets ( with and without >>>>> Flash) and Comet support. >>> Isn't this what Socket.io is for? >>> >>>>> We should keep the protobuf stuff and keep in mind that we need to support >>>>> proper authentication and everything should work across firewalls. >>>>> >>>>> Looking forward for some of your thoughts on this. >>>>> >>>>> Regards, >>>>> >>>>> Nelson >>>>> >
