Context affinity in a remote scripting environment

Abstract

A global context object may be used to create context affinity between two or more commands executed at a remote computer. A local computer may access a connection pool to determine if a runspace exists for a particular context on the remote computer in which the command is to be executed. If the runspace does not exist in the connection pool, the local computer may create a runspace associated with a particular context and add the runspace to the connection pool. The local computer may receive result data of executed commands from a remote computer and store the result data for use by the global context object to create context affinity between two or more commands executed at the remote computer.

Description

Background technique [0001] In some conventional remote scripting environments, the data conveyed from the execution of one command at the remote computer to the execution of subsequent commands is limited or suppressed due to security concerns. Because of these and other limitations in conventional remote scripting environments, the context in which one command is executed at the remote computer is often separate and distinct from the context in which subsequent commands are executed. Thus, in a conventional remote scripting environment, two or more commands may not share a context with each other, and as a result, no affinity is provided between the individual commands. Current solutions to this problem include setting the context of the first command while running the second command. Another solution could be to package the commands. However, these solutions can be prone to errors and reduce the performance of the remote scripting environment. [0002] It is with regard ...

AI Technical Summary

Problems solved by technology

However, these solutions can be error-prone and degrade the performance of the remote scripting environment

Images