No problem. Its just that server push is crucial in the new area of the internet and socket.io seams to became the standard of how to do it right now. Polling is so zeroish (2000+). So in the end this Atmosphere integration would be a good start for tapestry to support server push right out of the box. The play framework supports this as well.
By having this socket.io it would become easy to write more complex javascript application on the client side and connect to a tapestry backend server. Do you see a chance that we team up like 5 guys from the mailinglist and each one of us does some of the implementations or example codes or alike? Howard mentioned that he wanted server push to be part of Tapestry somehow. Maybe this can be a thing to pay something back (ok you are a good donor). For paying you, I need to know whats your price. Maybe we can start a mail-list threat asking who wants to have socket.io and server push right out of the box and maybe we fill the bucket so we can buy you some sort of compensation. So please tell me what your price is and we start a mail-list threat about this and see wheather we can find support for this or some who are willing to pay you some bucks to get this done. There are also some guys who said they did Atmosphere integration with tapestry so we have good resources of knowledge and sample-code. At the end we want two things: 1. being able to use socket.io right out of the box (or after installing a custom module) 2. A component(s) for pushing events / information to a client eliminating costly ajax polling techniques. Cheers 2013/8/23 Thiago H de Paula Figueiredo <thiag...@gmail.com> > I'm sorry, my messages above ended up way harsher then I intended. I don't > have anything that would earn me some money from next month on and it took > a toll on my humor. :( > > I've taken a look at Socket.IO. If I got it right, it has two parts: > server and client. The server one is written in JavaScript, targeted at > running at Node.js. And Atmosphere implementats the Server.IO server part. > Nice, I didn't know that. Interesting stuff. > > Next question: what do you mean by integration? There isn't a single way > of doing it. One way would be to create a module that sets up Atmosphere so > that Tapestry doesn't get in the way, provide ways of subscribing and > listening and sending messages in Tapestry-IoC and nothing else on > Tapestry-core itself. Another would be triggering events in Tapestry pages > and components. Without really having used Atmosphere before, I don't know > what would be the best way. Anyway, I'm sorry, I don't have the time to do > that now and I hope I do in the future. > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
