PRE-FETCHING IN DISTRIBUTED COMPUTING ENVIRONMENTS

• US 20140344344A1
• Filed: 07/29/2014
• Published: 11/20/2014
• Est. Priority Date: 10/31/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Beckman, Brian C., Meijer, Henricus Johannes Maria, Van Gogh, Jeffrey, Van Velzen, Danny
• Application Number:
  US14/445,216
• Publication Number:
  US 20140344344A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/55 Push-based network services
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics

Abstract

Client-side performance is optimized through server-side pushing of content. Portions of content are requested and retrieved as required by a client-side application. Moreover, content likely to be needed in the near future is pre-fetched and pushed to the client. This is beneficial from an overhead standpoint since all content need not be provided to the client at once. Rather, content provisioning is throttled based on need, and wait time is mitigated by pre-fetching.

Claims

1. A distributed computer system, comprising a memory having computer executable components stored thereon, and a processor communicatively coupled to the memory, the processor configured to execute the computer executable components, the computer executable components including:

an application component distributed across a client and a server; and

a pre-fetch component of the server that automatically identifies and pushes content likely to be needed to the client to facilitate client side application processing based on dwell time of a user on a client device.

2. The system of claim 1, wherein pre-fetching is applied to programmatic code of a distributed application, a portion of the distributed application executing on the client.

3. The system of claim 1, wherein the pre-fetch component is configured to ascertain content associated with at least one of a plurality of potential execution paths.

4. The system of claim 1, further comprising a monitor component configured to monitor a current state of the application with respect to a use structure, wherein the use structure defines application execution and identifies execution paths and associated content.

5. The system of claim 4, further comprising a context component configured to identify context information related to an execution of the application.

6. The system of claim 5, wherein the pre-fetch component is configured to ascertain content associated with at least one of the plurality of potential execution paths as a function of the current state and the context information.

7. The system of claim 1, further configured to process a client request identifying particular content associated with the application.

8. The system of claim 1, wherein the pre-fetch component is configured to identify content associated with the application according to various levels of granularity.

9. The system of claim 1, wherein the pre-fetch component is configured to determine a pre-fetch strategy as a function of global knowledge about the application prior to being split across the client and the server.

10. The system of claim 1, wherein the pre-fetch component further automatically identifies and pushes content likely to be needed to the client based on at least one of network bandwidth, network latency or processing time of the client device.

11. The system of claim 1, wherein the pre-fetch component further automatically identifies and pushes content likely to be needed to the client based on a user-specified pre-fetching algorithm controlling operation of pre-fetching by the server.

12. The system of claim 1, further comprising a history component that tracks and stores historical usage data which is used by the pre-fetch component to automatically identify and push content likely to be needed to the client.

13. The system of claim 12, wherein the pre-fetch component eliminates an execution path as unlikely based upon the historical usage data.

14. A client/server interaction method, comprising employing a processor to execute computer executable instructions stored on a computer readable storage medium to implement the following acts:

identifying content requested by a client application;

pre-fetching additional content by a server by identifying content likely to be needed by the client to facilitate client side application processing based on at least one of network bandwidth, network latency, processing time of the client device or a user-specified pre-fetching algorithm controlling operation of pre-fetching by the server; and

returning the requested and additional content to the client application.

15. The method of claim 14, further comprising monitoring an execution of the application to determine a current execution state.

16. The method of claim 14, further comprising identifying content associated with the application according to various levels of granularity.

17. The method of claim 14, further comprising receiving information pertaining to a context of the application from the client.

18. The method of claim 14, wherein pre-fetching is applied to programmatic code of a distributed application, a portion of the distributed application executing on the client.

19. The method of claim 14, further comprising receiving an input from the client specifying a manner in which content associated with the application is selected.

20. A computer-readable storage medium storing instructions, the instructions configured to, in response to execution by at least one computing device, cause the method of claim 14 to be performed.

21. The method of claim 14, further comprising requesting and receiving a particular content related to the application.

22. The method of claim 14, further comprising providing context information to a server, wherein the context information relates to an execution of the application on the client.