Private or Public MSMQ -


We are using queue for some of the WCF services. We use NSSMQ for WCF services using private MSMQ Using bindings. The system works fine on our QA environment. I am not sure about any real difference and private or public queue client applications are on different machines, yet the WCF service on other boxes is able to reach the personal queue. I'm not sure that this is the right thing. Is there any security related difference between the private and public MSMQ? Private or public MSMQ can use any light.

I also recommend using personal queues. I have used MSMQ since version 1.0 and ED has deployed the entire public queue before being assembled and in order to work on both types of public queue deployment, the opinion of the private queue is best for the needs of most groups. , Some Enterprise Messaging strengths have some limitations and for example, not being able to use the routing queue server Longer, but if your goal will only store and a decent reliable message delivery platform to further the trigger on the line right private line approach. My group processes more than 3 million messages per day through private queues and has been doing this for many years.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -