> If we look a bit further, placing a queue between ruote and some of the > participants has an interesting advantage: not only ruote can queue work for > those non-ruote workers. Ruote becomes just a[n orchestration] client among > other clients that can place work orders.
Yes, I see that as the true advantage of taking Ruote into an SOA environment. Ruote dictates the workflow (my understanding is that's what Ruote is designed for, but John, you'll have a bigger say, coz you're the author :p), everything true processing unit just worry about their own discrete task. I actually get a bit confused about your work on ruote-swf. I'm not sure where swf fits in the puzzle now ... My guess is if that one single job step/expression/participant is doing a hell lot and need to break down the sub task into sub-sub tasks, that's when you need swf? I realised it's a bit off topic now to what Nicola asked in this thread. My apology! -- 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
