I see, makes sense. Thank you for your explanations, hopefully I won't have to bug you as much in the near future once Ruote's secrets have all been revealed to me :)
-- Raphael. On Thu, Feb 10, 2011 at 10:50 PM, John Mettraux <[email protected]>wrote: > > On Thu, Feb 10, 2011 at 10:44:37PM -0800, Raphael Simon wrote: > > > > So a follow up question: Why doesn't the storage participant take > advantage > > of that? Is it because of the 'store name'? > > Hello, > > it's because the storage participant is meant as a "work list", people (or > apps) fetch workitems from it, modify them and put them back in. When > they're done with the work, they put it back in and tell the storage > participant they want it to be given back to the engine, and the modified > workitem (not the applied workitem) is replied back to the engine. > > Every expression keeps a copy of its applied workitem. > > Best regards, > > -- > 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 > -- 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
