Fragment response cache

• US 20040167961A1
• Filed: 02/26/2003
• Published: 08/26/2004
• Est. Priority Date: 02/26/2003
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ye, Chun, Jain, Neel Kamal
• Application Number:
  US10/375,840
• Publication Number:
  US 20040167961A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

The invention is directed to methods and data structures that enable a server to respond to a request for a web page by storing data fragments that are at least partially responsive to the request in a cache that is resident in kernel mode physical memory. The cache, a fragment cache, enables the server to respond efficiently, by receiving the request in a kernel mode; composing a response to the request by addressing the fragment cache in kernel mode to retrieve one or more data fragments at least partially responsive to the request; and transforming the data fragments into a composed response. The data fragments are addressable via a universal resource locator (URL) and in a hierarchical data structure, and are addressable by an application responding to the request.

Claims

1. A method of responding to a request for a web page, the method comprising:

receiving the request in a kernel mode;

composing a response to the request, the composing including;

addressing a fragment cache in kernel mode to retrieve one or more data fragments at least partially responsive to the request; and

transforming the one or more data fragments into a composed response; and

responding to the request using the composed response.

2. The method of claim 1 wherein the data fragments are addressable via a universal resource locator (URL).

3. The method of claim 1 wherein an HTTP driver receives the request in the kernel mode.

4. The method of claim 1 wherein the one or more data fragments are addressable by an application responding to the request.

5. The method of claim 1 wherein the transforming the data fragments includes adding a header to the one or more data fragments.

6. The method of claim 1 wherein the composing the response and the responding occurs in kernel mode and independent of a user mode.

7. A method for a server to generate a response to a request, the method comprising:

receiving the request in a kernel mode;

parsing the request in the kernel mode;

interacting with a responsible application, the responsible application controlling the response to the request;

processing the request in the application, the processing including identifying one or more content fragments stored in kernel mode, the content fragments at least partially responsive to the request; and

composing the response in kernel mode using the identified content fragments.

8. The method of claim 7 wherein the processing the request includes specifying one or more offsets and one or more lengths from any files specified by the application, the files being at least partially responsive to the request.

9. The method of claim 7 further comprising:

providing a sequence of content fragment identifiers and data buffers; and

providing an order for the sequence of content fragment identifiers and data buffers.

10. The method of claim 7 wherein the composing the response in kernel mode further includes adding data from one or more files identified by the application.

11. The method of claim 7 wherein the composing the response in kernel mode further includes adding one or more data buffers provided by the application from a memory associated with the application, the data buffers at least partially responsive to the request.

12. The method of claim 7 wherein the composing the response in kernel mode further includes adding one or more headers provided by the application.

13. The method of claim 12 wherein the headers are hyper text transfer protocol (HTTP) headers.

14. The method of claim 7 wherein the composing the response in kernel mode further includes adding one or more headers as determined in kernel mode.

15. A computer readable medium having computer executable instructions for performing the method of claim 7.

16. A method for a server to respond to a request, the method comprising:

receiving the request in a kernel mode;

parsing the request in the kernel mode;

interacting with a responsible application, the responsible application controlling a response to the request; and

identifying one or more content fragments stored in kernel mode, the content fragments at least partially responsive to the request.

17. The method of claim 16 wherein the controlling the response to the request includes one of adding content and sending the response, altering content and sending the response, and sending the response without altering or adding to the content.

18. A computer readable medium having computer executable instructions for performing a method of responding to a request for a web page, the method comprising:

receiving the request in a kernel mode, the method comprising;

receiving the request in a kernel mode;

composing a response to the request, the composing including;

addressing a fragment cache in kernel mode to retrieve one or more data fragments at least partially responsive to the request; and

transforming the one or more data fragments into a composed response; and

responding to the request using the composed response.

19. A computer readable medium having computer executable instructions for performing a method for a server to respond to a request, the method comprising:

receiving the request in a kernel mode;

parsing the request in the kernel mode;

identifying one or more content fragments stored in kernel mode, the content fragments at least partially responsive to the request; and

interacting with a responsible application, the responsible application controlling a response to the request.

20. The computer readable medium of claim 19 wherein the controlling the response to the request includes one of adding content and sending the response, altering content and sending the response, and sending the response without altering or adding to the content.

21. A method for an a user mode component to interact with a kernel mode cache configured to hold one or more data fragments responsive to a universal resource locator (URL), the method comprising:

calling a first application programming interface (API) configured to store the data fragments in the kernel mode cache, each of the data fragments identified by a URL;

calling a second API configured to flush the data fragments and any data fragments that are hierarchical descendants;

calling a third API configured to read the data fragments from the kernel mode cache; and

calling a fourth API configured to send a response using the data fragments from the kernel mode cache.

22. The method of claim 21 wherein the first API functions to overwrite any existing associated data fragment in the kernel mode cache.

23. The method of claim 21 wherein the data fragments are identified by a URL contained in a data structure pFragmentName and the first API is an AddFragmentToCache API.

24. The method of claim 21 wherein the second API is a FlushResponseCache API called with a URL prefix, the identification of the URL prefix enabling the second API to delete the data fragments within the URL prefix and the hierarchical descendants.

25. The method of claim 21 wherein the third API is a ReadFragmentFromCache API enabling reading of a data fragment from the kernel mode cache and enabling reading of a portion of a data fragment if the portion is identified.

26. The method of claim 21 wherein the fourth API is a SendHttpResponse API configured to send a response with one or more of the data fragments.

27. A structure for enabling an application to interact with a kernel mode cache holding one or more data fragments, the data fragments capable of at least partially forming a response to a universal resource locator request received by a server, the structure comprising:

a response data structure; and

an array of data structures within the response data structure, wherein each data structure of the array is configured to specify a block of memory and a name of an associated data fragment.

28. The structure of claim 27 wherein the array of data structures are each HTTP_DATA_CHUNK structures, and the response data structure is an HTTP_RESPONSE structure.

29. The structure of claim 27 wherein each of the data structures in the array of data structures has one of a plurality of types, the plurality of types including:

HttpDataChunkFromMemory, HttpDataChunkFromFileHandle, and HttpDataChunkFromFragmentCache.

30. The structure of claim 27 wherein the response data structure is configured to use a full response from the kernel mode cache.

31. The structure of claim 27 wherein the response data structure is configured to provide a matching count that specifies the dimension of the array of data structures.

32. The structure of claim 27 wherein the memory is a physical memory.