On Fri, Mar 23, 2012 at 06:20:45AM -0700, koen handekyn wrote: > > (...) > > An other reasoning we had is that another angle on it is that it > basically boils down to having multiple 'stores' in one 'engine' / > 'dashboard' and linking participants to a 'store' within an engine. in > the swf mapping a store would than map to a task list and for existing > stores it would just point to seperate stores. This would give a more > integrated feel to the engine participants.
Hello again, I guess you are referring to "engine participants" (http://ruote.rubyforge.org/part/engine_participant.html) You could totally have multiple engines using each a different ruote-swf storage (differentiated by task list (and it's just a transient name)). > another use case for this, just for information is the following : for > the overal workflow we want the workflow state to be persistent. so a > sql or nosql store makes a lot of sense for those. but for specific > subparts of the flow the intermedia state is not really that important > (if it fails, we just do it all over again). a redis store would make > a lot of sense there for example. as said today we can do it through > multiple engines with engine participants but for expressiveness also > here the possibility to link participants to 'stores' and workers to > 'stores' within one 'engine' seems to make sense. but also here it > might be that your ruote-swf generalization to ruote might give an > opening? I'm not sure the generalization is needed; unless clearly demonstrated as awkward, the current system (engine participants) may be used to have workflows with different storage implementations communicating. For example, the SWF backed engine could launch flows or segment of flows (they're not that different) on an Redis backed engine and back. I encourage you to explore what's available. If there really is a missing concept, we'll have to clearly identify it and we'll then find an elegant solution. Best regards, -- 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
