On Thu, 15 Jul 2010 16:28:35 -0300, Chuck Kring <cjkr...@pacbell.net>
wrote:
Hi, Chuck!
Our application consists of several dashboard pages that are used like a
network management console works: the pages automatically refresh as
things change, users can click on icons to drill down, etc. The page
relies heavily on Ajax calls to update icons and charts
Nice observation! You're absolutely right. This remebered me of this
discussion about reverse AJAX (Comet) in Tapestry:
http://old.nabble.com/comet-implementation-issue-to28531634s302.html#a28570596.
The scenario described in the first message of the discussion isn't an
issue without the pool. The implementation Rajesh did would work without
problems in the poolless Tapestry. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
