On Wed, 24 Oct 2012 22:14:56 -0200, sommeralex
<alexander.som...@gmail.com> wrote:
thx - sure. forget about this ;-)
:)
I think there are two different issues in your scenario, none related to
Tapestry:
1) Databases usually don't have any way of notifying changes to anything
outside them.
2) In web development, at least using HTTP, we don't have any way of
having a server trading information with clients (server-side push)*
except during a client doing a request to the server.
* There may be some specification or proposal about this right now, but I
can't recall any that can be used across different browsers right now, and
that's why we have Cometd and other packages that use polling (periodical
requests or keeping a connection open and making many requests before
closing the connection) to simulate server-side push.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
