On Thu, Apr 15, 2010 at 4:07 AM, Olle <[email protected]> wrote: > >> Note that for a participant that threads, the dispatched flagging is >> done right after the thread is launched. > > I don't know much about ruby threads implementation... Does it mean > that participant expression can be flagged as dispatched before it > really executed 'consume' in case of threaded dispatch?
Hello Oleg, you are right. Fixed : http://github.com/jmettraux/ruote/commit/c0368492d5ebd983bc28cbb10303cd98a89fd77b >> I'm wondering if it should be a default operation for a [re]starting >> engine or if it should be an engine method like >> engine.re_apply_stalled_participants >> >> Not sure. What do you guys think ? >> > > Same for me, not sure ). > Imho, it's better to re-apply by default in most of cases. But I can > also imagine a participant implementation which may not be re-applied > without hand work before... Maybe I can provide this re_apply_stalled_participants and make sure it only re_applies participant expressions that are at lease two minute old (to avoid re_applying just launched processes). Many thanks ! -- John Mettraux - http://jmettraux.wordpress.com -- 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 To unsubscribe, reply using "remove me" as the subject.
