私有或公共 MSMQ
我们将队列用于少数 WCF 服务。 我们将 NetMSMQ 绑定用于使用专用 MSMQ 的 WCF 服务。 该系统在我们的 QA 环境中运行正常。 我不确定私人或公共队列之间有什么真正的区别。 位于单独计算机上的客户端应用程序仍然能够访问其他机器上的 WCF 服务的专用队列。 我不确定这是否是正确的做法。 私有和公共 MSMQ 之间是否存在与安全相关的差异？ 有人可以阐明何时使用私有或公共 MSMQ。
We are using Queue for few of are WCF services.
We are using NetMSMQ binding for the WCF services which use Private MSMQ.
The system works OK on our QA environment.
I am not sure of any real difference between and private or public queue.
The client application are on seperate machine still are able to access Private queue of the WCF service on other box.
I am not sure if this is the right thing to do.
are there any security related differences between private and public MSMQ.
Can someone put some light on when to use Private or Public MSMQ.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我还建议使用专用队列。我从 1.0 版开始就使用 MSMQ，并在 AD 集成之前完成了整个公共队列部署，并且在两种类型的公共队列部署上工作过，我认为私有队列方法最适合大多数组的需求。是的，整体企业消息传递稳健性存在一些限制和一些差距，例如无法使用路由队列服务器，但如果您的目标只是拥有一个可靠的消息传递平台来存储转发和使用在队列上触发，那么专用队列方法就可以了。我的团队每天通过私有队列处理超过 300 万条消息事务，并且已经这样做很多年了。
I also recommend using private queues. I've used MSMQ since version 1.0 and did the whole public queue deployment back before the AD intgration and having worked on both types of public queue deployment the private queue approach in my opinion is the best for most groups needs. Yes, there are some limitations and some gaps in overall enterprise messaging robustness, like not being able to use Routing Queue servers for example, but if your goal is to simply have a decent reliable message delivery platform for store-and-forward and use of triggers on queues then the private queue approach will be fine. My group processes well over 3 million message transactions per day through private queues and have been doing this for many years now.
您需要的信息隐藏得很好（像往常一样），但可以在这里找到：
http://msdn.microsoft.com/en-us/library/ms706878(VS.85).aspx
这很大程度上取决于您的部署、Active Directory 集成级别以及您的队列的分布要求。如果是 WCF，我假设队列是通过 IIS/WPAS 公开的，这会将队列从应用程序中抽象出来，因此在该模式下它可能不太相关，并且本地队列就足够了。
The info you need is well hidden (as per usual), but it can be found here:
http://msdn.microsoft.com/en-us/library/ms706878(VS.85).aspx
It's pretty much down to your deployment, your level of Active Directory integration and your distribution requirement for the queues. If it's WCF, I assume the queue is being exposed via IIS/WPAS which would abstract the queue away from the application so it may be less relevant in that mode and local queues are sufficient.
如果必须使用大量使用公共 MSMQ 的应用程序，我会坚持使用私有队列。主要优点是您不会受到活动目录的束缚。我曾多次遇到对本地 MQ 所做的更改无法复制到 AD 的情况，因此我必须让服务器管理员登录到域控制器并为我删除队列，以便我可以重新创建它并确保所有设置正确。
这是 Microsoft 的一篇文章，探讨了一些差异。
http://technet.microsoft.com/ja-jp /library/cc753440%28WS.10%29.aspx
Having to work with an application that is heavy on using public MSMQs, I'd stick with private queues. The primary advantage is that you won't be tied to the active directory. I've had many times where changes made to a local MQ wouldn't replicate to the AD, so I had to have an server admin log into the domain controller and delete the queue for me so I could recreate it and make sure all the settings were correct.
Here is an article from Microsoft going into some of the differences.
http://technet.microsoft.com/ja-jp/library/cc753440%28WS.10%29.aspx