I am restricted to Java at the backend. I might have evaluated something like node.js+redis for the socket.io. That would be good. And before switching to node.js I would also evaluate the PlayFramework since they have session.io support out of the box and also allow me to stick to the Java way. But I am restricted to Tapestry 5 (existing project) and Java only. Also the database is MySql (MariaDB).
2013/8/16 Alejandro Scandroli <[email protected]> > Hi Martin > > Are you restricted to a Java application server? can you use things > like NodeJS or Redis? > A couple of years ago, I used Tapestry+NodeJS+Redis to push location > information to a mobile webapp. > As a starting point I used this example by Robin Komiwes: > > http://spreadthesource.com/2010/11/bringing-realtime-to-your-java-applications-with-websockets-nodejs-redis-tapestry-5/ > > The article is old but still relevant and you even have access to the > source code. > > Cheers. > Alejandro. > > > > > > On Fri, Aug 16, 2013 at 4:43 PM, Lance Java <[email protected]> > wrote: > > Currently, the only integrated push is tapestry-cometd. Howard has > > mentioned a few times that he'd like to include a push implementation in > > tapestry core but that hasn't happened yet. > > > > As has been mentioned, there's nothing stopping you from using Atmosphere > > and Tapestry side by side. > > > > If you declare the Atmosphere servlet (filter?) outside of tapestry (ie > in > > web. xml) you will need to tell tapestry to ignore atmosphere URL's > > > http://tapestry.apache.org/configuration.html#Configuration-ConfiguringIgnoredPaths > > > > Or, you can have tapestry manage the atmosphere servlet in the same way > as > > I mentioned tapestry-cometd does. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
