Question

我最近开始研究质量指数,我有一些非常基本的问题。

Answer 1

A message queue is mostly meant for asynchronous things where you dont have to wait for the response. You could block the caller until a response is sought, but thats typically what an MQ is not meant for. You would use it only in cases where a user is NOT waiting for an output. A webservice is the opposite. You get a request, process it and return it back in a finite time. The caller will mostly block until a response is received.
You can send String, Objects , Maps, Byte Arrays to an MQ.
There are no constraints regarding the placement of the MQs. Just like webservices they can be anywhere and you can write and read from the Queue.

Answer 2

核对链接

http://en.wikipedia.org/wiki/IBM_WebSphere_MQ

for more detailed info. There is a similar question posted:

宣传 Queue vs. Web Services?

Found this useful as well: http://www.hanselman.com/blog/ClassicWebServicesVersusPOXXMLOverMQAreYouReallyUsingXML.aspx