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 provides the size of an HTTP message, including the SOAP envelope and the SOAP attachments associated with it.
- Property ID
-
PROPID_M_COMPOUND_MESSAGE_SIZE
- Type Indicator
-
VT_UI4 (or VT_NULL)
- MQPROPVARIANT Field
-
ulVal
- Property Values
-
The size, in bytes, of the HTTP message, including the SOAP envelope and the SOAP attachments, provided by PROPID_M_COMPOUND_MESSAGE.
Remarks
The PROPID_M_COMPOUND_MESSAGE_SIZE property is a read-only property that is only used when retrieving HTTP messages.
To retrieve the contents of an HTTP message, including the SOAP envelope and the SOAP attachments associated with it, see PROPID_M_COMPOUND_MESSAGE.
Equivalent COM Property
There is no COM equivalent for this property.
Examples
The following code example shows how PROPID_M_COMPOUND_MESSAGE_SIZE is specified in the MQMSGPROPSstructure when retrieving an HTTP message.
Copy Code | |
---|---|
MsgProps.aPropID[i] = PROPID_M_COMPOUND_MESSAGE_SIZE; MsgProps.aPropVar[i].vt = VT_UI4; i++; DWORD dwMsgBufferSize = 4096; UCHAR *pucMsgBuffer = (UCHAR *)malloc(dwMsgBufferSize); if (pucMsgBuffer == NULL) { // Error handling code (not included for clarity) } MsgProps.aPropID[i] = PROPID_M_COMPOUND_MESSAGE; MsgProps.aPropVar[i].vt = VT_VECTOR|VT_UI1; MsgProps.aPropVar[i].caub.pElems = (UCHAR*)pucMsgBuffer; MsgProps.aPropVar[i].caub.cElems = dwMsgBufferSize; i++; |
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.