Page #104 (Queued Components)

< BACK  NEXT >

[oR]

Summary

The first part of the chapter provided an overview of MSMQ.

MSMQ facilitates asynchronous communication between two software programs by way of messages. A message can contain any data, including persistable objects. The sender and the receiver have to agree on the format.

An MSMQ enterprise is built as a hierarchical topography of sites. An MSMQ server can be installed in a number of ways including a Primary Enterprise Controller, a Primary Site Controller, a Connecter server, a Routing server, etc.

An MSMQ client could be installed to be dependent or independent.

An MSMQ message can be sent as express or guaranteed. An MSMQ message can also participate in a transaction internally, as well as one coordinated externally.

In the first part of the chapter, we also observed how to develop scalable applications using MSMQ components.

In the second part of the chapter, we looked at Queued Components (QC), a service provided by COM+ that uses the MSMQ infrastructure for asynchronous communication but hides the details of MSMQ programming from the developers. We looked at the QC architecture and examined ways to respond to messages, and participate in transactions.

For more information on MSMQ and QC, I have included some references. The MSDN library is also a good reference source (and the documentation keeps on getting better).

< BACK  NEXT >