为什么Nservicebus不使用WCF？
我看到 NServiceBus 使用 MSMQ 作为其传输。为什么它不使用 WCF 和 MSMQ 作为底层传输？
I see that NServiceBus uses MSMQ as its transport. Why doesn't it use WCF with MSMQ as the underlying transport?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
主要原因是 MSMQ 代码是在 WCF 存在之前编写的。随着时间的推移，大部分工作都集中在添加新功能，而不是重新审视已有的 MSMQ 集成解决方案。
NServiceBus 还对 MSMQ 做了一些 WCF 没有做的事情。例如，如果队列不存在，NServiceBus 将创建一个队列。这使得使用 NServiceBus 比使用 WCF 更加顺畅。
这并不意味着如果迁移到 WCF/MSMQ 之上就无法保留此功能，但主要是与下一版本中计划的所有其他功能相比，它的优先级太低了。
The primary reason was that the MSMQ code was written before WCF even existed. As time progressed, most of the work focused on adding new features rather than revisiting the already solution MSMQ integration.
There's also things that NServiceBus does with respect to MSMQ that WCF doesn't do. For example, NServiceBus will create a queue if it doesn't exist. This makes it much smoother to work with NServiceBus than with WCF.
This does not imply that this functionality could not be preserved if migrated to work on top of WCF/MSMQ but the main thing is that it is just too low a priority as compared to all the other things slated for the next release.
一旦你意识到今天的微软有很多团队，他们可能（或者很可能）不会使用彼此的代码。 NserviceBus 人员做出了决定，无论出于何种原因，他们都不想使用 WCF，仅此而已。
几年前，我参加一个会议，一位来自微软的人向我们介绍 MTS，我问他为什么那里的安全组不使用本地组（即 WinNT 安全组）。他嗯了一声，然后说：“是的，我明白你提出这个问题的出发点，请提出下一个问题”。看，MTS 中的组安全性与本地组的设计目的完全相同 - 但 MTS 人员决定他们将实现自己的组并忽略底层 NT 安全系统。如果我们能够有 1 个地方来设置安全性并将其应用于所有 Microsoft 产品，我会非常高兴，但事实并非如此。甚至是微软自己的开发人员。
Once you realise that the Microsoft of today is a lot of teams who may (or most likely) may not use each others code. The NserviceBus guys made a decision that they didn't want to use WCF for whatever reason, and that's that.
Years ago, I was at a conference where a guy from MS was telling us about MTS and I asked him why the security groups in there didn't use Local Groups (ie WinNT security groups). He ummed and ahhem and said "yes, I see where you're coming from with that question, next question please". See, the group security in MTS was exactly the same as local groups were designed for - but the MTS guys decided that they would implement their own groups and ignore the underlying NT security system. I would be really nice if we could have 1 place to set security and have it apply to all Microsoft products, but that's not the way it goes. even by Microsoft's own devs.