Window Workflow Foundation 是 AOP 吗？
我是 Window Workflow Foundation 和 AOP 的新手。我发现它们非常相似。所以我想知道WWF是AOP...我知道WWF的概念与AOP不同。然而，我认为他们将会实现类似的想法。
如果这是一个愚蠢的问题，我很抱歉。谢谢！
亚历克斯
I am new in Window Workflow Foundation and AOP. I found that they are quite similar. So I am wondering that WWF is AOP... I know the concept of WWF is different from AOP. However, I think they are going to achieve the similar idea.
If this is a silly question, I am so sorry. Thanks!
Alex
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为不——这些想法是不同的。
AOP的思想是开发更干净的代码，更好地封装它，使系统耦合更少，更容易维护。这是一个主要针对开发人员的想法。
WWF 的想法是从预构建的块中组装企业应用程序。针对开发人员和业务分析之间的某个位置。通过 WWF，您可以在新环境中重用某些模块，但通常 WWF 会尝试类似于业务流程建模的概念。
当然，你可以想象很多情况，你可以使用WWF作为工具来实现更好的封装和松散耦合或者其他方式——使用AOP来重用模块并将其组织在工作流中。但他们的总体想法的交集相当小。
I think no - those ideas are different.
AOP idea is to develop cleaner code, better encapsulate it, make systems less coupled and easier to maintain. It is an idea targeted mainly on developers.
WWF idea is to assemble enterprise applications from pre-built blocks. Targeted somewhere in between developers and business analytics. With WWF you can possibly re-use some modules in new contexts, but generally WWF tries to resemble concepts of business process modeling.
Of course, you can imagine a lot of situations where you can use WWF as the tool to achieve better encapsulation and loose coupling or otherwise - to use AOP to re-use modules and organise it in a workflow. But the intersection of their general ideas is rather small.