3.1.1.2.2 RunspacePool State

Each RunspacePool has an associated state. Section 2.2.3.4 specifies available states and describes the data types used to encode the states in the PSRP messages.

For details about how a RunspacePool state transitions from its initial state of Opening to the state of Opened, see the RunspacePool creation process specified in section 3.1.4.1.

From the Opened state, a RunspacePool can reach either the Closed or Broken state specified in section 2.2.3.4.

A client can close a RunspacePool by sending a wxf:Delete message (section 3.1.5.3.11). Before sending this message, the client changes the RunspacePool state to Closing and stops any executing pipelines (section 3.1.4.4) using the pipeline table (section 3.1.1.2.6). If there is a successful response (section 3.2.5.3.12), the client changes the RunspacePool state to Closed; otherwise, the client changes the state to Broken.

For details of how a client can disconnect from a RunspacePool, see section 3.1.4.9. For details of how a client can connect to a RunspacePool, see section 3.1.4.10.

Figure 2: Client RunspacePool states and transitions