Re: Micro-workflow engine suggestion

Mike/Carlos,

> Quick word of history: Keel's workflow expert, Jeff, is sometimes off
> the list for a while, but I very much imagine he'll have some
> perspective to share on Keel's existing workflow. The workflow "service"
> went away because workflow in Keel was "driving" the Model objects, and
> was not a service called *by* the Models, so it became an application
> (app-workflow), rather than a service.
> 
> Just wanted to toss in those 2c while I was thinking of it...
> 
> I think BPM-style workflow is a somewhat different animal than the
> app-workflow, but I'd defer to it's author to say how different. Our
> current workflow does have a very nice GUI editor, though.

This is exactly right.  app-workflow is an entirely different flavor of 
  workflow than typical BPM engines; app-workflow is used mainly to 
chain multiple models and then to dispatch to other models based on the 
output of the preceding one.  I know Jeff started out by basing 
app-workflow on OSWorkflow from OpenSymphony, but switched over to his 
own engine (RedFlow) at some point.  I think if we started with a 
service API, it would be possible to make a RedFlow impl. of the 
service.  RedFlow doesn't have support for persisting flow states, but 
there (I think) are hooks for that to be added in pretty easily.

Shash