Wait for ready state

• US 7,912,927 B2
• Filed: 03/26/2008
• Issued: 03/22/2011
• Est. Priority Date: 03/26/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Thangadurai, Shiva Shankar, Vainer, Moshe, Reddy, S Neeraja
• Primary Examiner(s): Dinh; Khanh Q
• Application Number:
  US12/055,325
• Publication Number:
  US 20090248850A1
• Time in Patent Office: 1,091 Days
• Field of Search: 709/220, 709/224, 709/228, 717/104, 379/221.08
• US Class Current: 709/220
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 2201/88 Monitoring involving counting

Abstract

Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Claims

1. A method for performing at least two recorded actions on a server system, comprising:

initiating a recorded action;

monitoring a status of one or more requests from the recorded action, comprising;

applying an adapter pattern to one or more request objects, the request objects comprising application programming interface request objects;

tracking state changes of the one or more request objects, comprising using references to an event handler specified by an application programming interface property;

determining when the one or more request objects are at a desired state, the desired state being one that corresponds to a request object being completed; and

upon detecting that a predetermined amount of time has elapsed, comprising detecting that a response to the request object has not been generated by the server system within the predetermined amount of time, setting the state of one or more request objects to the desired state;

upon detecting the desired state for one or more requests, comprising determining that the desired state for all of the one or more requests corresponds to a request being completed, performing a next recorded action; and

upon detecting that a predetermined amount of time has elapsed, comprising detecting that a response to a request has not been generated by the server system within the second predetermined amount of time, performing the recorded action.

2. The method of claim 1, monitoring a status of one or more requests comprising incrementing a monitoring counter when the request is initiated, and decrementing the monitoring counter when the status of the request is completed.

3. The method of claim 2, wherein all of the one or more requests have a completed status when the monitoring counter reaches zero.

4. The method of claim 3, performing a next recorded action comprising incrementally conducting a next action predetermined to occur by a record of actions.

5. The method of claim 1, the server system comprising a web server.

6. The method of claim 1, the server system comprising at least one of:

Internet protocol;

file transfer protocol;

user datagram protocol;

dynamic host configuration protocol;

hypertext transfer protocol;

Telnet remote protocol;

secure shell remote protocol;

post office protocol 3;

simple mail transfer protocol; and

Internet message access protocol.

7. The method of claim 1, comprising determining if the recorded action has timed out.

8. A computer readable device having computer-executable instructions, which when executed via a microprocessor perform actions, comprising:

initiating a recorded action;

monitoring a status of one or more requests from the recorded action, comprising;

applying an adapter pattern to one or more request objects, the request objects comprising application programming interface request objects;

tracking state changes of the one or more request objects, comprising using references to an event handler specified by an application programming interface property;

determining when the one or more request objects are at a desired state, the desired state being one that corresponds to a request object being completed; and

upon detecting that a predetermined amount of time has elapsed, comprising detecting that a response to the request object has not been generated by a server system within the predetermined amount of time, setting the state of one or more request objects to the desired state;

upon detecting the desired state for one or more requests, comprising determining that the desired state for all of the one or more requests corresponds to a request being completed, performing a next recorded action; and

upon detecting that a second predetermined amount of time has elapsed, comprising detecting that a response to a request has not been generated by the server system within the second predetermined amount of time, performing the recorded action.

9. The computer readable device of claim 8, monitoring a status of one or more requests comprising incrementing a monitoring counter when the request is initiated, and decrementing the monitoring counter when the status of the request is completed.

10. The computer readable device of claim 9, wherein all of the one or more requests have a completed status when the monitoring counter reaches zero.

11. The computer readable device of claim 8, performing a next recorded action comprising incrementally conducting a next action predetermined to occur by a record of actions.

12. The computer readable device of claim 8, the server system comprising a web server.

13. The computer readable device of claim 8, the server system comprising at least one of:

Internet protocol;

file transfer protocol;

user datagram protocol;

dynamic host configuration protocol;

hypertext transfer protocol;

Telnet remote protocol;

secure shell remote protocol;

post office protocol 3;

simple mail transfer protocol; and

Internet message access protocol.

14. The computer readable device of claim 8, comprising determining if the recorded action has timed out.

15. A system configured to perform at least two recorded actions on a server system, comprising:

a recorded action performer component configured to;

initiate a recorded action;

perform a next recorded action upon detecting a desired state for one or more requests, detecting the desired state comprising determining that the desired state for all of the one or more requests corresponds to a request being completed, the desired state being one that corresponds to a request object being completed; and

perform the recorded action upon detecting that a predetermined amount of time has elapsed, detecting that the predetermined amount of time has elapsed comprising detecting that a response to a request has not been generated by the server system within the predetermined amount of time; and

a request monitor component configured to monitor a status of one or more requests from the recorded action and apply an adapter pattern to one or more request objects comprising application program interface request objects, wherein the request monitor comprises;

a monitoring interface component configured to track state changes of the one or more request objects, comprising using references to an event handler specified by an application programming interface property; and

a request complete detector component configured to;

determine when the one or more request objects are at the desired state; and

set the state of one or more requested objects to the desired state upon detecting that a second predetermined amount of time has elapsed, detecting that the second predetermined amount of time has elapsed comprising detecting that a response to the request object has not been generated by the server system within the second predetermined amount of time.

16. The system of claim 15, comprising a wait-for-ready signaler component configured to send a signal to the recorded action performer component.

17. The system of claim 15, the request complete detector component configured to indicate to a wait-for-ready signaler component that the request has been completed.

18. The system of claim 15, the monitoring interface component comprising an object adapter pattern generator component configured to generate a custom object adapter pattern for the request object.

19. The system of claim 15, the monitoring interface component comprising a pending request counter component configured to account for requests to the server system and corresponding request complete responses from the server system.

20. The system of claim 19, the request complete detector component comprising a request counter monitor component configured to determine when the pending request counter component reaches zero.