Hi Thiago,
On 12/9/2010 1:10 PM, Thiago H. de Paula Figueiredo wrote:
On Thu, 09 Dec 2010 18:33:13 -0200, Chuck Kring <cjkr...@pacbell.net>
wrote:
I use onActivate() to return an image for a heartbeat to an Ajax
dashboard.
Why the heartbeat? Are you talking about the Tapestry heartbeat concept?
No, this is different. My application uses an Ajax dashboard on a
kiosk. Components on the dashboard are periodically polled to produce
updated charts, status icon changes, etc. In addition to the
component updates the dashboard refreshes every few minutes and when
objects (beds, this is a medical application) are added or removed.
This is required because the icon components represent beds and the
number of icons (components) changes when the number of beds changes.
This dashboard has to run 7/24 and to reconnect when the server or the
network are down.
I use the image (essentially a web bug) before a page update. If the
image fails, I continually poll the image until I get a response, then I
do a page refresh. This prevent a page failure when the server is down.
When I proposed that, I was warned that using onActivate() to return
an image can create performance issues.
I can't see why, specially in T5.2, which doesn't use page pooling.
I agree that this is likely not an issue for T5.2 - I'm currently on
5.1.05.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
