Abstract: Embodiments described herein are based on the principle that shells execute commands as units of characters. Accordingly, embodiments herein provide for a sending side with enough intelligence to isolate each command, examine it, perform some levels of validation, and deliver a structured representation of the command to the remote processor before doing any network operations. More specifically, embodiments herein provided for a mechanism of identifying a command and encapsulating the command into a single message (e.g., a SOAP, HTTPS, or other type message), which is then sent to a remote shell for processing as an entire unit. Accordingly, embodiments herein treat the command as a single unit, rather than as a character-oriented transmission.

Abstract: Embodiments described herein are based on the principle that shells execute commands as units of characters. Accordingly, embodiments herein provide also provide for some special cases of asynchronous control signals that change the shell operation flow. For example, signal messages may be used to terminate, pause, resume, or otherwise modify the execution of a command. In other words, if a user wishes to change the execution state of a command, a client can create a signal message and send such message to the shell processor, which can take the appropriate action as desired. Note that by modeling the control or signal commands as discrete messages (as well as other embodiments modeled and described herein), such commands are not mistakenly executed on a command as is the case for current protocols that use a character-by-character transmission.

Abstract: Embodiments described herein are based on the principle that shells execute commands as units of characters. Accordingly, embodiments herein provide for a sending side with enough intelligence to isolate each command, examine it, perform some levels of validation, and deliver a structured representation of the command to the remote processor before doing any network operations. More specifically, embodiments herein provided for a mechanism of identifying a command and encapsulating the command into a single message (e.g., a SOAP, HTTPS, or other type message), which is then sent to a remote shell for processing as an entire unit. Accordingly, embodiments herein treat the command as a single unit, rather than as a character-oriented transmission.

Abstract: Embodiments described herein are based on the principle that shells execute commands as units of characters. Accordingly, embodiments herein provide also provide for some special cases of asynchronous control signals that change the shell operation flow. For example, signal messages may be used to terminate, pause, resume, or otherwise modify the execution of a command. In other words, if a user wishes to change the execution state of a command, a client can create a signal message and send such message to the shell processor, which can take the appropriate action as desired. Note that by modeling the control or signal commands as discrete messages (as well as other embodiments modeled and described herein), such commands are not mistakenly executed on a command as is the case for current protocols that use a character-by-character transmission.