On Tue, Apr 15, 2014 at 3:24 PM, John Mettraux <[email protected]> wrote:
> > > On Tue, Apr 15, 2014 at 1:54 PM, John Mettraux <[email protected]> > wrote: > > > > > > On Tue, Apr 15, 2014 at 01:02:30PM -0700, ypz wrote: > > > > > > > > Neither of above two states tells me if the worker is currently > > > > busy/processing a message. Is there a way to determine if my worker > is > > > > doing a step or do we need to introduce a new worker state ? > > > > > > Hello, > > > > > > by "doing a step", do you mean "has handed a workitem out to a > > > participant" ? > > On Tue, Apr 15, 2014 at 03:09:02PM -0700, Yiping Zhang wrote: > > > > Yes. > > > > My understand is that the worker thread, after handing a workitem out to > a > > participant, will not process next step in workflow until that said > > participant has finished processing its workitem. > > ```ruby > concurrence do > step_a > step_b > end > ``` > > With that workflow, the worker will likely proceed step_b right after > having > proceeded step_a. > > Your understanding is not right. > > > Assuming participant's do_not_thread() returns false, worker instance would run above concurrent sample workflow in two new threads, correct ? In this situation, going back to my original question, since I want to restart worker instance, I still need to know if those two threads, handling step_a and step_b respectively, have completed their respective work or not -- -- 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 --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
