Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
A server MUST use the wxf:ReceiveResponse WS-MAN message (section 3.2.5.3.8) to send PSRP messages to a client.
When sending a PSRP message (section 2.2.1), the message MUST first be placed at the end of the appropriate queue of outgoing messages (see sections 3.2.1.2.4 and 3.2.1.3.4), which will store the message until a wxf:Receive message comes from the client.
When the wxf:Receive message arrives from the client, the server MUST dequeue the entire PSRP message or a suffix of a PSRP message from the beginning of the appropriate queue (see sections 3.2.1.2.4 and 3.2.1.3.4), and fragment it (see section 2.2.4). If the appropriate queue is empty, then the server MUST block and wait for new items to be added to the queue (while following rules for keeping the connection alive specified in [MS-WSMV], section 3.1.4.14). The FragmentId fields for a particular PSRP message MUST be numbered consecutively beginning with 0, and the fragments MUST be sent in ascending order of the FragementID using wxf:ReceiveResponse (section 3.2.5.3.8).
If multiple fragments from step 3 can fit into a single WS-MAN message, then the single WS-MAN message SHOULD include as many fragments as possible (see [MS-WSMV], section 3.1.4.1.7). If any fragments did not fit into the wxf:ReceiveResponse message, then the suffix of the message associated with those fragments MUST be put back at the beginning of the appropriate queue (see section 2.2.4) to be processed when the next wxf:Receive message comes from the client. If more data could fit into the wxf:ReceiveResponse message and the queue is still not empty, then the server SHOULD go back to the previous step to generate more fragments for the wxf:ReceiveResponse message.