3.1.4.10.2 Connecting to a RunspacePool from a Previous Client Session

  • Article

A client session that has previously disconnected from a remote RunspacePool can reconnect by using the wxf:Reconnect message (section 3.1.5.3.18). The client sends the same wsmv:SessionId (see [MS-WSMV] section 3.1.4.1.37) value that it used in the original connection to that RunspacePool.

  1. The client sends a wxf:Reconnect message, using the ShellID as specified in section 3.1.1.2.4.

  2. The client receives a wxf:ReconnectResponse message (section 3.2.5.3.19) from the server. The client changes the RunspacePool state (section 3.1.1.2) to Opened. If the client receives a wxf:Fault message, it instead changes the RunspacePool state to Broken.

  3. If the client received a wxf:ReconnectResponse message in the previous step, it MUST send a wxf:Receive message (section 3.1.5.3.7) to the server to start receiving data from the server.

  4. The client MUST send additional wxf:Receive messages in response to any further wxf:ReconnectResponse messages it receives from the server, as long as the RunspacePool is not in either the Closed or Broken state.