更改范例以使用工作流程
想知道在新开发中使用 WorkFlow 的优点/缺点吗？ 似乎有点范式的改变，想知道是否值得努力合并。
Was wondering advantages/disadvantages of using WorkFlow in new development? Seems like a bit of change of paradigm, wondering if it is worth the effort to incorporate.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
在深入研究 WF 之前，请确保分析您想要实施的工作流程。 如果它们相当简单和/或短暂，我会三思而后行。
我的经验是，当工作流可以持续很长时间（几小时/几天/几周）时，它确实会带来回报，特别是与持久性服务结合使用时。 在我使用它的项目中，我们意识到，在我们拥有的两个主要工作流程中，其中一个在不使用 WF 的情况下可能也能正常工作。
另一种（将信息打包在通过 SMPT 发送的邮件中，然后期望邮箱中的一些预定义响应之一，如果没有响应到达，则以一定的时间间隔重新发送消息）我发现这是一个很好的例子WF。
Before diving in to WF make sure to analyze the workflows that you want to implement. If they are fairly simple and/or short-lived I would think twice.
My experience is that it does pay off when the workflows may live for a long time (hours/days/weeks), especially in combination with a persistence service. In the project where I have used it we realized that of the two main workflows that we have, one of them would probably work just as fine without using WF.
The other one (which is packaging information in a mail that is sent over SMPT, and then expects one of a few predefined responses in a mailbox, and resending the message at certain intervals if no response arrives) I find to be a good case for WF.
不用担心桌面应用程序上的工作流程。 由于多线程设计（非常适合服务器，尤其是 Web 服务器），状态转换之间的延迟非常高。
Dont bother with Workflow on desktop apps. Due to the multithreaded design (which is perfect for servers, particularly web servers), latency is quite high between state transitions.
如果它看起来不适合您的项目，您可能不需要它。
If it doesn't seem like a natural fit into your project you probably don't need it.