0

I started looking into MSMQ very recently so i have basic doubts . If two application needs to communicate lets say server and client I think both will share the same MQ address and when the client update then the Server will be having the MSMQ watcher which will listen to the message pick and use it. So according to me there are three component we need

Client - which knows the Queue location

Queue watcher - which watches the queue

service -- to which queue watcher will send the message to

satish
  • 2,425
  • 3
  • 23
  • 40
  • 1
    What do you mean by "both will share the same MQ address"? Do you mean both machines put messages into a common queue and an application works out which message is for which machine? Why don't you have a queue on the server that the client sends to and a different queue on the client that the server sends to? – John Breakwell Apr 13 '11 at 08:13
  • Then you wouldn't need a separate MSMQ watcher. Each client and server application watches the queue. – John Breakwell Apr 14 '11 at 08:24

1 Answers1

0

Tom Hollander wrote an excellent series of three articles on WCF and MSMQ. They helped me alot when I had to build an application to communicate via MSMQ. There is a third article but Stack Overflow won't let me post since I'm a new user. You can find the link to it from the 2nd article.

MSMQ, WCF and IIS: Getting them to play nice (Part 1)

MSMQ, WCF and IIS: Getting them to play nice (Part 2)

MLF
  • 626
  • 4
  • 15