On Fri, Mar 6, 2009 at 12:43 PM, J B <[email protected]> wrote: > > So when would it be appropriate to use a state machine versus a workflow > engine? Our new system needs to make decisions in a more complex way (i.e., > if a field has a value > n, route this way, else route that way...things > like that). I'm betting aasm would be a lot simpler, but I'm not sure it's > ilk supports these sorts of flows.
Kenneth explored aasm / ruote : http://www.opensourcery.co.za/2009/03/04/ruote-in-20-minutes/ State machines are great for resource lifecycle. If you can stick with 1 document 1 state then go for it. If you want to deal with [business] processes and not only resources, change the processes often (sometimes "in fly"), have resources taking part in multiple processes (of different versions...), then ruote is worth exploring. >> OK, back to ruote-web2. ActiveRecord >= 2.2 is no friend of mine :( > > Ah, so you've hit problems with rails 2.3 now as well? Rails 2.3 is fine, ActiveRecord, since 2.2 is very finicky with multithreaded apps like Ruote. Seriously thinking about using DataMapper for all the database things occurring outside of the HTTP request/response thing web frameworks are thought for. I already have a DataMapper process runtime persistence implemented : http://github.com/jmettraux/ruote/blob/dd5c9d3e1ae50a78daabd1e3f85939c1b82dd014/lib/openwfe/extras/expool/dm_expstorage.rb (I'm clueless when it comes to Rails). 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 -~----------~----~----~----~------~----~------~--~---
