4.1.8 Changing Minimum Runspaces Count of the Server’s RunspacePool
The typical PSRP sequence for changing the minimum runspaces count of the server's RunspacePool is described in the following table:
|
Step |
Client |
Direction |
Server |
|---|---|---|---|
|
1 |
The RunspacePool is in the Opened state on the client. |
|
|
|
2 |
The client constructs an integer identifier to represent the message, to be sent, and stores it in the RunspacePool's CI table (section 3.1.1.2.5). The client constructs a SET_MIN_RUNSPACES message (section 2.2.2.7) and sends it using wxf:Send message (section 3.1.5.3.5) targeted to the RunspacePool. |
> |
The server changes the Minimum number of runspaces as per the guidelines specified in section 3.2.1.2.9. |
|
3 |
The client sends a wxf:Receive message (see section 3.1.5.3.7) to the server, if none is pending for this RunspacePool. |
> |
|
|
4 |
The client processes the RUNSPACE_AVAILABILITY message (section 2.2.2.8) and removes the corresponding entry from the RunspacePool's CI table (section 3.1.1.2.5). |
< |
The server sends a wxf:SendResponse message (section 3.2.5.3.6) to the client. The server constructs a RUNSPACE_AVAILABILITY message (section 2.2.2.8) and sends it to the client using a wxf:ReceiveResponse message (section 3.2.5.3.8). |
|
5 |
The client can send the response to the higher layer as required. |
|
|