Full Duplex

This functionality relies on the ability to send a single HTTP request or response into separated packets, referred to here as chunks, as defined in [RFC2616].

Each chunk MUST contain a full SOAP envelope, with the exception of the final terminating chunk.

The client SHOULD create and maintain two concurrent HTTP connections so it can send input, if necessary, along with the operation, as when executing WMI operations with PowerShell semantics (see Messages sent on the two connections MUST have the same OperationID GUID.

Under some conditions, two special messages SHOULD<138> be sent as chunks. For more information, see and