Interesting you should bring this up. I am in the planning and
discovery stages for this component. Once I get an api planned and a
skeleton created, I will propose it for consideration to be included in
the core.
The quick overall idea is that it will be a component (not completely
unlike Acl in a sense) that will be able to define workflows and spawn
"jobs" of a specific workflow type. As far as defining the workflow,
there is a wealth of information (very academic) here
http://www.workflowpatterns.com/patterns/index.php
There are a few projects that I have tried out, and or talked to the
authors of:
OpenWfe - http://www.openwfe.org/manual/
Spiff Workflow - http://pypi.python.org/pypi/Spiff%20Workflow/
Features I'd like to implement/see:
- full workflow pattern coverage
- participants (resource allocation)
- workflow data collection
- workflow data callbacks (basically checking if a condition is met
before allowing the job to proceed)
- interface for job state storage, persistence
Long term:
- generation of colored petri nets to display workflow
- ability to import/export workflow definitions
Of course I am actually building it for a current project, so I wont be
backing off, if it doesn't get approved for core inclusion, I will
gladly host as Xend_Workflow.
-ralph
Tobias Gies wrote:
what exactly should this component do?
2007/9/23, Jeunejean Pierre <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
Any Zend_Workflow or Proof-Of-Concept planned in the future ?
TIA, Pierre
--
Pierre Jeunejean
gérant
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
www.adnexus.be <http://www.adnexus.be>
Wirtzfeld 3a, B-4760 Büllingen
Tel: 0478556586
A D N E X U S
Solutions informatiques Internet en sous-traitance pour les agences
publicitaires.
Solutions informatiques de gestion sur mesure pour les entreprises.
