Replacing Message Queuing with System Messaging

The System.Messaging namespace provides classes that allow you to connect to, monitor, and administer message queues on the network and send, receive, or peek at messages. This namespace provides developers with the ability to send and receive messages primarily through two classes: Message and MessageQueue. The Message class encapsulates any data you are sending, as well as properties to control the routing, formatting, and security of the message. MessageQueue classes are used to represent the individual queues and contain the methods for working with the queues, such as Send() and Receive().

By using Message Queuing and the System.Messaging namespace, .NET developers can create highly scalable, reliable applications that are loosely coupled and share only the name of a common queue.

For more information about the upgrade of Message Queuing API access to the System.Messaging namespace, see the "MSMQ and Queued Components" section in Chapter 15, "Upgrading MTS and COM+ Applications."

Note: It is important to note that MSMQ 3.0 provides functionality not available in the System.Messaging namespace. For example, Message Queuing can provide information about the quantity of messages contained in a queue. If you need this functionality, you will need to implement it by using other .NET Framework functionality (for example a .NET Framework ServicedComponent that traces the quantity of messages in a queue).

For more information about the System.Messaging namespace, see "System.Messaging Namespace" in the .NET Framework Class Library on MSDN.

0 0

Post a comment