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-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
