Shell operation flow change

• US 8,090,838 B2
• Filed: 08/31/2006
• Issued: 01/03/2012
• Est. Priority Date: 02/16/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: McCollum, Raymond W., Nosov, Alexander, Kumbalimutt, Vishwajith, Menzies, Steve, Lee, Stephen Wah
• Primary Examiner(s): Pwu, Jeffrey
• Assistant Examiner(s): Waqas, Saad A
• Application Number:
  US11/469,429
• Publication Number:
  US 20070192773A1
• Time in Patent Office: 1,951 Days
• Field of Search: 709/230
• US Class Current: 709/227
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality

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.

Claims

1. At a client in a network computing environment, a computer-implemented method of asynchronously controlling or changing the flow of a shell operation in a remote shell session using a signal message to execute an action as desired, the method comprising:

opening a remote shell session at a command-line shell processor by a client including a command-line interface, wherein the command-line interface allows a user to input commands, opening the remote shell session comprising;

sending by the client an open shell request message to the command-line shell processor; and

receiving a shell identifier from the command-line shell processor for identifying one or more execution request messages sent from the client as being part of the remote shell session;

during the open remote shell session with the command-line shell processor;

using by the client the command-line interface to send an execution request message of the one or more execution request messages that includes a command for execution at the command-line shell processor, wherein the command is sent as a unit that includes one or more of a command name and one or more switches, wherein the command is stored in a storage in the command-line shell processor; and

prior to receiving information about completion of the execution of the command, creating at the client and sending by the client using the command-line interface an asynchronous signal message rather than a special character in an input stream to the command-line shell processor, the asynchronous signal message terminating the execution of the command in-progress at the command-line

shell processor, wherein the open remote shell session between the client and the command-line shell processor continues operating after termination of the command.

2. The method of claim 1, wherein the information about the execution of the command includes one or more of an acknowledgement that the command has properly been received by the command-line shell processor, an acknowledgement that the command has properly been executed by the command-line shell processor, or output from the execution of the command by the command-line shell processor.

3. The method of claim 2, wherein the acknowledgement that the command has properly been received by the command-line shell processor includes a command identifier.

4. The method of claim 1, further comprising sending by the client a close shell message to the command-line shell processor for closing the shell session.

5. The method of claim 1, further comprising:

receiving a signal response message at the client indicating termination of the command.

6. The method of claim 1, wherein prior to sending the execution request message, the method further comprises:

sending input for the command as one or more streams of data, wherein the execution request message is sent prior to receiving streamed output data from the command-line shell processor.

7. A computer program product comprising one or more computer readable storage media having stored thereon computer executable instructions that, when executed by a processor, can cause the client to perform the method of claim 1.

8. At a remote command-line shell processor in a network computing environment, a computer-implemented method of asynchronously controlling or changing the flow of a shell operation using a signal message to execute an action as desired, the method comprising:

opening a shell session at a command-line shell processor, opening the shell session comprising;

receiving by the command-line shell processor an open shell request message from a client; and

sending a shell identifier by the command-line shell processor to the client for identifying one or more execution request messages received from the client as being part of the shell session;

during the open shell session;

receiving by the command-line shell processor from a client an execution request message of the one or more execution request messages that includes a command for execution at the command-line shell processor, wherein the command is sent as a unit that includes one or more of a command name and one or more switches, wherein the command is stored in a storage in the command-line shell processor; and

prior to completing the execution of the command and sending information about the execution of the command to the client, receiving by the command-line shell processor from the client an asynchronous signal message created by the client using a command line interface rather than a special character in an input stream, the asynchronous signal message terminating the execution of the command in-progress at the command-line shell processor, wherein the open shell session continues operating after termination of the command.

9. The method of claim 8, wherein

the information about the execution of the command including one or more of an acknowledgement that the command has properly been received by the command-line shell processor, an acknowledgement that the command has properly been executed by the command-line shell processor, or output from the execution of the command by the command-line shell processor.

10. The method of claim 9, wherein the acknowledgement that the command has properly been received by the command-line shell processor includes a command identifier.

11. The method of claim 8, further comprising receiving a close shell message at the command-line shell processor for closing the shell session.

12. The method of claim 8, further comprising:

sending a signal response message to the client indicating termination of the command.

13. The method of claim 8, wherein prior to receiving the execution request message, the method further comprises:

receiving input for the command as one or more streams of data, wherein the execution request message is received prior to sending streamed output data from the command-line shell processor.

14. A computer program product comprising one or more computer readable storage media having stored thereon computer executable instructions that, when executed by a processor, can cause the remote command-line shell to perform the method of claim 8.