替代Windows工作流基础？ [英] Alternatives to Windows Workflow Foundation?
问题描述
我一直在使用WWF一段时间作为内部呼叫中心应用（ASP.NET）的一部分，而学习是了解一个很好的做法如何基于状态机的工作流系统的应工作，我绝对不是在爱与世界自然基金会本身。在我看来，它是：
I've been using WWF for a while as part of an internal call center application (ASP.NET), and while learning it was a good practice in understanding how a state machine based workflow system should work, I am definitely not in love with WWF itself. In my opinion it is:
- 过于复杂，尤其是对于Web应用程序中使用（所有的线程运行时的东西）
- 未成熟（曾经与那个可怕的设计师合作？）
- 贫血在其当前的功能设置
有没有人有一个更好的基于.NET框架的工作流程的建议？具体来说，我正在寻找以下特征：
Does anyone have a suggestion for a better .NET based workflow framework? Specifically, I am looking for the following features:
- 基于机器状态（映射状态可用动作）
- 系统注重用户的权限（控制谁可以访问哪些行动）
- 要运行工作流程作为后台定时任务（例如，发出提醒已经坐在某一状态X天的项目）的能力
这真是我所需要的。我并不需要能够拖放的任何活动或视觉设计流程。我完全舒适的实际code，一旦某个动作被触发。
That's really all I need. I don't need to be able to "drag and drop" any activities or visually design the flow. I am perfectly comfortable writing actual code once a particular action is triggered.
推荐答案
您可以尝试简单的状态机的。你将不得不实现访问控制和背景定时器自己，但是这不应该是一个大问题。 SSM还内置出于无奈与WF。 <一href=\"http://www.$c$cplex.com/Project/ProjectDirectory.aspx?ProjectSearchText=%22state%20machine%22\">There都在codePLEX 其他一些状态机实现为好。如果其中一个不适合他的法案开箱，他们都是开源的，应该让你足够接近。
You could try Simple State Machine. You would have to implement access control and background timers yourself, but that shouldn't be a big deal. SSM was also built out of frustration with WF. There are some other state machine implementations on Codeplex as well. If one of them doesn't fit he bill out of the box, they are open source and should get you close enough.
我完全同意你关于WF状态机 - 他们是不可测试的，太复杂，线程模型是独特而难以遵循，而我不知道一个可视化设计器可能被设想更差了设计状态机图形。我想这可能是因为状态机的概念感觉上涨到WF运行时，它被设计为顺序状态机，WF的东西确实有一个更好的工作，在我看来。问题是，状态机是真的不相同的动物为顺序的工作流程，并应被赋予了第一类实现他们自己的，因为WF的翘曲，使其似乎支持他们原来是或多或少得不到支持，如果不是实际上无法使用。
I wholeheartedly agree with you about state machines in WF - they aren't testable, are too complicated, the threading model is peculiar and hard to follow, and I'm not sure a visual designer could have been more poorly conceived for designing state machines graphically. I think this may be because the state machine concept feels tacked onto the WF runtime, which was designed for sequential state machines, something WF does a much better job with, in my opinion. The problem is that state machines are really not the same animal as a sequential work flow, and should have been given a first class implementation of their own, because the warping of WF to make it seem to support them turned out to be more or less unsupportable, if not actually unusable.
这篇关于替代Windows工作流基础？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
