Hi John. Thanks heaps for your answer...
On Aug 11, 3:39 pm, John Mettraux <[email protected]> wrote: > On Wed, Aug 10, 2011 at 07:56:44PM -0700, Tom wrote: > > I guess it's a misuse of listen. If your goal is to gather the "current state > of the workitems" maybe listen is not your friend. > I assumed listen was not build for this scenario. I try to explain in more detail what we're trying to accomplish: Our web-app (multiple users) is pushing documents through a ruote workflow. We're currently implementing a live-update feature, that allows us to notify other users if a document changed state / moved to a different participant. So we need a way to trigger an update on all connected browsers whenever a document arrives at a new participant, because some users will have to be notified. The only solution we got so far is a nasty Engine#reply and sleep for a couple seconds. We could try to use Engine#wait_for method, but that's almost as nasty ;) Is there maybe a way to hook into ruote to be notified as soon as something hits a participant? Or maybe you got a completely different option for the problem!?! Thanks mate, Tom -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
