Updated: July 19, 2016
Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista
Sending and receiving applications can use direct messaging at any time. However, direct messaging is designed to be used when messages must be sent to the destination queue in one hop, or when the application needs to open a queue (for sending or retrieving messages) that is not in the same enterprise. Direct messaging should be used to send messages whenever routing, authentication, and encryption by Message Queuing are not needed.
Note that when direct messaging is requested, Messaging Queuing uses the information provided by the application in the direct format name to locate and open the queue. Except in the case of a local public queue, Message Queuing does not contact the directory service to open a queue for direct messaging.
To send or retrieve messages directly, the application must use a direct format name to open the queue. Direct format names include the address specification of the computer where the destination queue resides, followed by the local name of the queue.
Direct format names can be used in distribution lists or multiple-elementformat names when sending messages to multiple destination queues.
|For information on||See|
|How Message Queuing opens queues for direct messaging||Opening Queues with a Direct Format Name|
|The syntax of a direct format name and security-related limitations created by using direct format names||Direct Format Names|
|Other format names (public, private, distribution list, multicast address, and multiple-element format names)||Format Names|