On Fri, 23 Aug 2013 19:13:15 -0300, Martin Kersten
<martin.kersten...@gmail.com> wrote:
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.
I wouldn't do that kind of statement, but yes, I agree that server push is
quite interesting. :)
Polling is so zeroish (2000+).
Atmosphere, according to its documentation, supports many transports (ways
of doing communication from server to client), including polling and
WebSockets. This example
(https://github.com/Atmosphere/atmosphere/wiki/Getting-Started-with-AtmosphereHandler,-WebSocket-and-Long-Polling)
even uses WebSocket as main transport and long polling as a fallback.
So in the end this Atmosphere
integration would be a good start for tapestry to support server push
right out of the box.
"Out-f-the-box" can have different meanings. If it's about to put it in
tapestry-core, I wouldn't think this is a good idea. The Tapestry
philosophy for this kind of stuff is to have basic, core features in the
tapestry-core package and additional packages to provide more specific
stuff. I think a tapestry-atmosphere package would be something quite nice
to have. :)
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).
:D
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.
Please don't use the word threat. People can feel threatened and we don't
want that to happen. :P Instead of discussing here, I can investigate some
more, define an estimate and create an Indiegogo campaign (I'm Brazilian
and Kickstarter only accepts campaigns from inside USA). Deal? :)
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)
A think a separate drop-in package is the better option here, so projects
which don't use Atmosphere are not forced to have it.
2. A component(s) for pushing events / information to a client
eliminating costly ajax polling techniques.
I'm not sure how a Tapestry component would fit here, as this is much more
about client-side and JavaScript, but I think this is a part of 1 above
anyway, or at least a natural next step. If you have an idea, I'd love to
hear it.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
