PRE-FETCHING IN DISTRIBUTED COMPUTING ENVIRONMENTS

• US 20090112975A1
• Filed: 10/31/2007
• Published: 04/30/2009
• 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 Velzen, Danny, Van Gogh, Jeffrey
• Application Number:
  US11/932,723
• Publication Number:
  US 20090112975A1
• 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:

an application component distributed across a client and server; and

a pre-fetch component that automatically identifies and pushes content likely to be needed to a client to facilitate client side application processing.

2. The system of claim 1, further comprising a use structure that defines application execution.

3. The system of claim 2, the use structure is a graph that identifies execution paths and associated content.

4. The system of claim 2, further comprising a monitor component that monitors application execution state with respect to the use structure.

5. The system of claim 4, further comprising a context component that identifies context information surrounding application processing.

6. The system of claim 5, further comprising a component that identifies content as a function of the execution state and context information.

7. The system of claim 1, the client requests units of content from the server as needed.

8. The system of claim 1, the pre-fetch component identifies and pushes content of various levels of granularity.

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

10. The system of claim 1, the content is one or more of programmatic code and data.

11. A client/server interaction method, comprising:

identifying client application requested content;

pre-fetching additional content as a function of current state and context; and

returning the requested and additional content to the client application.

12. The method of claim 11, further comprising monitoring application usage to determine the current state.

13. The method of claim 11, pre-fetching groups of additional content at various levels of granularity.

14. The method of claim 11, further comprising receiving context information from the client application for use in identifying the additional information.

15. The method of claim 11, further comprising identifying application dwell time, and limiting the additional data provided to the client as a function thereof.

16. The method of claim 11, further comprising measuring pre-fetching effectiveness, and updating the act of pre-fetching based thereon.

17. The method of claim 11, further comprising receiving user input specifying one or more modifications to the manner in which additional content is selected.

18. A client processing method, comprising;

requesting content in a piecemeal fashion to facilitate client side application execution; and

receiving the requested content and additional content likely to be need for future processing from a server.

19. The method of claim 18, requesting and receiving units of programmatic code.

20. The method of claim 18, further comprising providing application context information to the server to aid pre-fetching of the additional content.