Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This property specifies how Message Queuing delivers the message.
Syntax
HRESULT get_Delivery( long* plDelivery ); HRESULT put_Delivery( long lDelivery ); |
Parameters
- plDeliveryor lDelivery
-
Value that specifies how Message Queuing delivers the message. The following table shows the possible values.
Value Description MQMSG_DELIVERY_RECOVERABLE
In every hop along its route, the message is forwarded to the next hop or stored locally in a backup file until delivered.
This guarantees delivery even in the case of a computer crash.
MQMSG_DELIVERY_EXPRESS
The default. The message stays in memory until it can be delivered.
Return Value
The following table describes the common return values.
Value | Description |
---|---|
S_OK |
Success |
E_INVALIDARG |
One or more arguments are invalid |
E_NOTIMPL |
The function contains no implementation |
E_OUTOFMEMORY |
Out of memory |
Remarks
The Delivery property is used to specify express or recoverable messaging.
- Express messaging provides faster throughput.
- Recoverable messaging guarantees that the message will be
delivered, even if a computer crashes while the message is en route
to the queue.
Message Queuing always sets the delivery mechanism of transactional messages to MQMSG_DELIVERY_RECOVERABLE.
Equivalent Function Property
When using function calls, the delivery type can be set and retrieved using the PROPID_M_DELIVERYmessage property.
Requirements
Header | mqoai.h |
Library | mqoa.lib |
Windows Embedded CE | Windows CE .NET 4.0 and later |
Windows Mobile | Windows Mobile Version 5.0 and later |
See Also
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.