Thanks, John. I'm using a single, embedded worker, so that should be fine for now. I will revisit this if/when I need more workers, and might at that point resort to safely polling the engine for the initiated process or updated workitem. Will let you know when that happens; I'll be more familiar with ruote by then, and maybe I can contribute a solution if it fits the project ethos.
I'm still very new to using ruote, but am liking it a lot so far. The current implementation is ruote-kit living side-by-side with our own event-processing sinatra app that shares a ruote engine with ruote- kit. Will be locking down the destructive/constructive ruote-kit resources with some middleware, since I only want it as a dashboard for now. Might even rip it out completely later. Still figuring it all out. Enjoy your weekend. Keep well. -Nic On Aug 5, 3:26 pm, John Mettraux <[email protected]> wrote: > On Fri, Aug 05, 2011 at 06:16:34AM -0700, Nic Young wrote: > > > Ah... it turns out that wait_for is exactly what I want! (Just an > > update for the benefit of others) > > > Somehow I missed that you can wait_for a specific wfid, in addition to > > number of processes (and more). > > Hello Nic, > > let me just point at the warning in the #wait_for description: > > https://github.com/jmettraux/ruote/blob/84ded303d6807eb76dd52969ac412... > > Cheers, > > -- > John Mettraux -http://lambda.io/processi -- 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
