I have a task broker that I wrote in python that informs APE of when
the status of a task changes, and the browser listens in on a channel
and can display those status changes live.

Except that it really bogs down the browser. The task broker is
configured to run three thread at most, the changes happen fairly
quickly sometimes (2/3 per thread per minute) and this seems to bog
down the browser.

So what is best practice here? I suppose its possible to queue up
status changes into bursts sent to the browser, but seems to defeat
the purpose of why I wanted to try out APE / comet to make a live
reporting tool.

suggestions anyone?

-- 
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/

Reply via email to