MAINTAINING AND CACHING SERVER CONNECTIONS

• US 20160337466A1
• Filed: 03/25/2016
• Published: 11/17/2016
• Est. Priority Date: 05/14/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Chang, MingChieh (Jackie), Shih, Sheng-Yao (George), Hu, Shu-Yu (Steve), Tsai, Ta-Chung (Terry), Huang, Hsin Hui (Ellen)
• Granted Patent: US 10,356,173 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session

Abstract

A set of runspaces with active connections are maintained in a pool. A set of timers are set and, based upon the timers, simple commands are submitted through the runspaces, to maintain the connections in an active state. The runspaces with the active connections can then be used from the cache, without having to open a new connection.

Claims

1. A computing system, comprising:

a user interface component;

a set of computing system functionality components that control the user interface component to generate functionality user interface displays with functionality user input mechanisms that are actuated to perform functionality on a remote endpoint computing system, over a set of connections to the remote endpoint computing system; and

a remote connection system that includes a set of runspace components, each having an associated connection in the set of connections, and a first timer component that generates a first timer output indicative of a first timeout period, the remote connection system intermittently submitting a request through the runspace components, based on the first timer output, over each of the connections in the set of connections, the remote endpoint computing system disabling the connections for lack of use based on a session timeout period, and the first timer being configured so the first timeout period is based on the session timeout period and a number of runspace components in the set of runspace components.

2. The computing system of claim 1 and further comprising:

a set of cache pool systems, each cache pool system corresponding to a different one of the endpoint computing systems and having an opened runspace cache pool that stores runspace components that have active connections to the corresponding endpoint computing system.

3. The computing system of claim 2 wherein the first timer is configured so the first timeout period varies dynamically based on a number of runspace components in the opened runspace cache pools.

4. The computing system of claim 3 wherein the first timer is configured so the first timeout period is a period comprising the session timeout period divided by the number of runspace components in the opened runspace cache pools.

5. The computing system of claim 3 wherein the remote connection system comprises:

a last known good queue that identifies the runspace components in the opened runspace cache pools in an order in which they were last used.

6. The computing system of claim 5 wherein the set of computing system functionality performs the functionality on the remote endpoint computing system by submitting a request through a selected runspace component and further comprising:

a server request component that receives a submit input indicative of the request and selects a runspace component to obtain the selected runspace component.

7. The computing system of claim 6 wherein the server request component selects the runspace component based on contents of the last known good queue.

8. The computing system of claim 6 wherein each cache pool system comprises:

a closed runspace cache pool that stores runspace components that have closed connections to the corresponding endpoint computing system.

9. The computing system of claim 8 and further comprising:

a second timer component that generates a second timer output indicative of a second timeout period;

an open component that selects a runspace component from the closed runspace cache pool and attempts to open a connection corresponding to the selected runspace component; and

a move component that, if the open component successfully opens the selected runspace component, moves the selected runspace component to the opened runspace cache pool and enters it in the last known good queue.

10. The computing system of claim 8 and further comprising:

a third timer component that generates a third timer output indicative of a third timeout period; and

a boundary checking component that, based on the third timeout period, determines whether a total number of runspace components meets a size change boundary.

11. The computing system of claim 10 and further comprising:

a size change system that changes the total number of runspace components in response to the boundary checking component indicating that the total number of runspace components meets the size change boundary.

12. A computer implemented method, comprising:

controlling a user interface component to generate functionality user interface displays with functionality user input mechanisms;

detecting actuation of the functionality user input mechanisms to perform functionality on a remote endpoint computing system, by submitting a functionality request to a runspace component, in a set of runspace components, that each have a corresponding connection to the remote endpoint computing system;

generating a keep alive timer output indicative of a keep alive timeout period; and

submitting a request through the runspace components, based on the keep alive timer output, over each of the connections, the remote endpoint computing system disabling the connections for lack of use based on a session timeout period, and the keep alive timeout period being based on the session timeout period and a number of runspace components in the set of runspace components.

13. The computer implemented method of claim 12 each of a set of cache pool systems corresponds to a different one of a plurality of endpoint computing systems and has an opened runspace cache pool that stores runspace components that have active connections to the corresponding endpoint computing system, and wherein generating the keep alive timer output comprises:

varying the keep alive timeout period dynamically based on a number of runspace components in the opened runspace cache pools.

14. The computer implemented method of claim 13 and further comprising:

identifying the runspace components in the opened runspace cache pools in a last known good queue in an order in which they were last successfully used.

15. The computer implemented method of claim 14 further comprising:

receiving a submit input indicative of the request; and

selecting the runspace component to receive the request based on contents of the last known good queue.

16. The computer implemented method of claim 15 and further comprising:

storing runspace components that have closed connections to the corresponding endpoint computing system in a closed runspace cache pool;

generating an open runspace timer output indicative of an open runspace timeout period;

selecting a runspace component from the closed runspace cache pool;

attempting to open a connection corresponding to the selected runspace component; and

if the open component successfully opens the selected runspace component, moving the selected runspace component to the opened runspace cache pool.

17. The computer implemented method of claim 16 and further comprising:

generating a check pool size timer output indicative of a check pool size timeout period;

determining, based on the check pool size timeout period, whether a total number of runspace components meets a size change boundary; and

if so, changing the total number of runspace components in the given cache pool system.

18. A computing system, comprising:

a set of cache pool systems, each cache pool system corresponding to a different one of a plurality of endpoint computing systems and having an opened runspace cache pool that stores runspace components that have active connections to the corresponding endpoint computing system;

a first timer component that generates a first timer output indicative of a first timeout period; and

a remote connection system intermittently submitting a request through the runspace components to the endpoint computing systems, based on the first timer output, over each of the active connections, the remote endpoint computing system disabling the connections for lack of use based on a session timeout period, and the first timer being configured so the first timeout period varies dynamically based, at least in part, on the session timeout period and a number of runspace components.

19. The computing system of claim 18 wherein each cache pool system comprises a closed runspace cache pool that stores runspace components that have closed connections to the corresponding endpoint computing system, and wherein the remote connection system comprises:

a second timer component that generates a second timer output indicative of a second timeout period;

an open component that selects a runspace component from the closed runspace cache pool and attempts to open a connection corresponding to the selected runspace component; and

a move component that, if the open component successfully opens the selected runspace component, moves the selected runspace component to the opened runspace cache pool and enters it in the last known good queue.

20. The computing system of claim 19 and further comprising:

a third timer component that generates a third timer output indicative of a third timeout period;

a boundary checking component that, based on the third timeout period, determines whether a total number of runspace components meets a size change boundary; and

a size change system that changes the total number of runspace components in response to the boundary checking component indicating that the total number of runspace components meets the size change boundary.