Windows Workflow 在大型 Web 应用程序中的使用
虽然，我在互联网上查到的大多数示例都使用 WF 来处理类似向导的步骤或设计基于工作流的 UI，并且由于 Windows Workflow 可以处理状态机，如果我们说，我们有一个像 Stackoverflow 这样的网站。 com，我们将在应用程序的哪些领域使用工作流基础？
示例：
- 用户的问题获得了 10 票赞成，授予其所有者一枚青铜徽章。
- 一个问题刚刚获得 10,000 次浏览，设置其 top_question 标志。
是否应该使用 Windows 工作流来处理这些小事件（但数量确实太多）？
是否有任何WF组件可以放置在内置WF的顶部以简化此类操作？
Although, most of the examples I checked on the Internet use WF to deal with wizard-like steps or designing a workflow-based UI, and since Windows Workflow can deal with state machines, and if we say, we have a website like Stackoverflow.com, In what areas of the application would we use the WorkFlow foundation?
Examples:
- A user's question has got 10 up-votes, give its owner a bronze badge.
- A question has just got 10,000 views, set its top_question flag.
Should these small (but there is really too many of them) events should be handled using Windows Workflow?
Is there any WF components to be placed on the top of the built-in WF to ease such operations?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我还没有看到使用 WF、BizTalk 或任何其他引擎等工作流引擎成功构建应用程序。我所说的成功是指：它已投入生产，并且与没有开箱即用的工作流引擎构建的应用程序相比，生成的应用程序更易于维护。
Udi Dahan 发布了关于该主题的非常有趣的博客 他详细说明了为什么这些东西通常只适用于演示，但不适用于现实生活。
公平地说，我应该澄清一下，我没有任何 WF 的实践经验，我不久前确实玩过 BizTalk，发现它完全超出了我的需要。。
I have yet to see a successful application build with a workflow engine like WF, BizTalk or any of the other engines out there. By successful I mean: it made it to production and the resulting application was easier to maintain than if it had been built without an out of the box workflow engine.
Udi Dahan posted a very interesting blog on the topic where he elaborates why this stuff usually only works on demos but not in real life.
To be fair, I should clarify that I do not have any hands on experience on WF, I did play with BizTalk a while ago and found it completely over the top for what I needed.
我没有使用wwf的状态机部分，而只使用了顺序工作流程。
一开始我很兴奋，因为我希望使用wwf能够真正解决我们的一些问题。
最后确实一团糟，我很高兴我们的项目只是一个小项目：
WWF 可以解决特定问题，但我很难想象有一个 Web 应用程序可以从 WWF 中受益。
I have not used the state machine part of wwf, but only sequential workflows.
At first I was excited because I hoped that using wwf could realy solve some of our problems.
At the end it was realy a mess and I was happy that our project was only a small one:
WWF can be solution to a specific problem, but I can hardly imagine a web application that benefits from wwf.
我已将状态机与 WF (.net 3.5) 一起使用并将产品发布到生产环境。这是ae采购系统，采购请求、采购订单需要经过几个状态（审批者、请求者等）。但是，我们遇到了一些问题，例如如果您的状态机在生产后发生更改，则数据库中已有的实例应该根据新的状态机手动运行，否则会出现错误。我认为状态机与简单应用程序一起工作，如果您有复杂的逻辑（例如与 UI 批准交互）可能会导致一些问题。我还没有检查 .net 4.0 WF，但可能它会有解决方案。
I've used state machine with WF (.net 3.5) and product released to production. It was a e procurement system that purchase request, purchase order need to go thru a several states (Approver, Requestor, etc). However, we come across few issues like if your state machine change after production, instances already in database should be run according to new state machine by manually otherwise, it gives an error. I think state machine work with simple application if you have complex logic like interacting with UI approval may be cause some problems.I haven't check .net 4.0 WF yet may be it will have solutions.