[Zope-CMF] [DCWorkflow] active workflows

[Dieter Maurer]

Thank you for your feedback!

Julien Anguenot wrote at 2005-1-7 16:51 +0100:
> ...
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Dieter Maurer wrote:
>| ... "active" workflows (transitions performed automatically) ...
>| I plan to use this extension as follows to implement an
>| "active" state:
>|
>|   Such a state has
>|
>|    * variables "initial_delay" and "repeated_delay",
>|
>|    * a special transition "probe" that remains in state and
>|      has a "script_before" "reschedule"
>|
>|    * a "script_on_entry" "schedule" and a "script_on_exit"
>|      "unschedule"
>|
>|    * at least one automatic transition that can leave the state
>|
>|   The "*schedule" scripts use a scheduling service to
>|   schedule the "probe" transition after
>|   "initial_delay" (for 'schedule') and 'repeated_delay' (for
>'reschedule').
>|   'unschedule' cancels the scheduling request.
>| 	
>|   The scheduling service calls "probe" at the given time.
>|   This reschedules and then checks for automatic
>|   transitions. If one is electable and leaves the state,
>|   the schedule request is canceled.
>|
>|
>| What do you think about this approach?
>|
>
>Actually, I don't think I would like to see that kind of scheduling
>features hooked on the workflow. Another service should take care of that.

Indeed, the scheduling service should be an independent service
which is just used by the workflow. It is useful for other features
as well.

-- 
Dieter