Depending on the situation, the value of being able to submit a request that will get done eventually (even if the "service" doing the work is currently down, busy, or being updated by a new version) -- which is one huge benefit of MSMQ -- could be extremely large.
How useful would your web app be, using web services, if the services are not running (or get "backed up" so that it takes a long time for them to run)? How much more useful would it be if your user can submit requests even though they will not be done for a while? There are other reasons as well -- for example, the security mechanisms are more advanced than those for (portable) web services. To quote from the main MS page about MSMQ -- [quote] Microsoft Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. MSMQ provides guaranteed message delivery, efficient routing, security, and priority-based messaging. It can be used to implement solutions for both asynchronous and synchronous messaging scenarios. [end quote] At 03:15 AM 6/27/2006, Paul Cowan wrote >> I would have went with a web service myself. >Me too, I seriously cannot think why we are using MSMQ in this way. We have >come into the project late and another company has set everything up to return >things via MSMQ. > >I personally do not like [EMAIL PROTECTED] J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
