学习,使用,开发工作流引擎这么长时间了,AgileFlow也开发到了0.8版,但在这整个期间,一直
没有发现一个让我感觉兴奋的引擎;怎么样合理的定位工作流引擎的边界,合理的设计它提供
给外界的接口,怎么样合理的让用户进行非编译方式的扩展,一直困扰着我;我试图在AgileFlow
中给出答案,但给的算不上好,很多问题我是知道的,但就是找不到办法.

这两天学习osworkflow,终于找到了那种很high的感觉!
osworkflow基本上解决了我以前考虑的98%的问题,而且在很多方面和我的思路是一样的;它在
保证代码最简单逻辑最清晰的条件下,给出了最强的功能,而且这种功能是不需要对用户有什么
强制性的限制的.

下面是它的说明:
OSWorkflow can be considered a "low level" workflow implementation.
 Situations like "loops" and "conditions" that might be represented by a graphical
 icon in other workflow systems must be "coded" in OSWorkflow.
That's not to say that actual code is needed to implement situations like this,
 but a scripting language must be employed to specify these conditions.
It is not expected that a non-technical user modify workflow.
We've found that although some systems provide GUIs that allow for
simple editing of workflows, the applications surrounding the workflow
usually end up damaged when changes like these are made.
We believe it is best for these changes to be made by a developer who
 is aware of each change. Having said that, the latest version provides
a GUI designer that can help with the editing of the workflow.

osworkflow对工作流引擎应该做什么,不应该做什么,应该达到什么目标,和我的思路完全
一致.兴奋,今天算是找到了知己.

发表于 @ 2004年11月26日 15:13:00|评论(loading...)