First let us understand why MSMQ came in to picture and then rest will
follow. Let us take a scenario where your client needs to upload data to
a central server. If everything will works fine and the server is
available 24 hours to client then there are no issues. In case the
server is not available, the clients will fail and the data will not be
delivered. There is where MSMQ comes in to picture. It eliminates the
need of persistent connection to a server. Therefore, what you do is
deploy a MSMQ server and let the clients post message to this MSMQ
server. When your actual server runs, it just picks up the message from
the queue. In short, neither the client nor the server needs to be up
and running on the same time. In WCF we have a client and service model
and in real world it is very much practical possible that both the
entities will not be available at one time.
Join MindStick Community
You need to log in or register to vote on answers or questions.
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
Can you answer this question?
Write Answer1 Answers