Implementing server push at server stack

• US 9,736,256 B2
• Filed: 02/13/2014
• Issued: 08/15/2017
• Est. Priority Date: 02/13/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Mazahir, Osama
• Primary Examiner(s): Tran, Philip B
• Application Number:
  US14/180,231
• Publication Number:
  US 20150229731A1
• Time in Patent Office: 1,279 Days
• Field of Search: 709203, 709223
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

In one embodiment, a server 120 may push linked resources 320 to a client device 110 using the server stack 124. The server stack 124 may detect a linked resource 320 associated with an active initial navigation request 402. The server stack 124 may generate a synthetic linked resource request 506. The server stack 124 may propagate the synthetic linked resource request 506 through the server stack 124.

Claims

1. A machine-implemented method, comprising:

receiving in a server stack an active initial navigation request for a main resource;

receiving the main resource from a server application in response to the active initial navigation request;

detecting a linked resource referenced by the main resource of the active initial navigation request;

generating at the server stack a synthetic linked resource request for the linked resource; and

propagating the synthetic linked resource request through the server stack.

2. The method of claim 1,

wherein the main resource is at least one of a dynamic resource and a static resource.

3. The method of claim 1, further comprising:

receiving a linked resource application programming interface call alerting the server stack of the linked resource referenced by the main resource of the active initial navigation request.

4. The method of claim 1, further comprising:

generating the synthetic linked resource request at least one of a kernel mode and a user mode.

5. The method of claim 1, further comprising:

routing the synthetic linked resource request to an associated server application associated with the linked resource.

6. The method of claim 1, further comprising:

applying a security protocol to the synthetic linked resource request.

7. The method of claim 1, further comprising:

receiving the linked resource in response to the synthetic linked resource request.

8. The method of claim 1, further comprising:

detecting a push capability for a client device.

9. The method of claim 1, further comprising:

storing the linked resource in a server stack cache in preparation for a subsequent linked resource request.

10. The method of claim 1, further comprising:

pushing the linked resource to a client device.

11. A computing device having memory to store a set of instructions detailing a method stored thereon that when executed by one or more processors cause the one or more processors to perform the method, the method comprising:

receiving an active initial navigation request for a main resource from a client device;

promoting the active initial navigation request to a server application;

receiving the main resource from the server application in response to the active initial navigation request; and

receiving a linked resource application programming interface call alerting the server stack of a linked resource referenced by the main resource of the active initial navigation request.

12. The computing device of claim 11, wherein the method further comprises:

detecting a push capability for the client device.

13. The computing device of claim 11, wherein the method further comprises:

generating a synthetic linked resource request with a server stack; and

propagating the synthetic linked resource request through the server stack to the server application.

14. The computing device of claim 11, wherein the method further comprises:

forgoing a synthetic linked resource request for the client device without push capability.

15. The computing device of claim 11, wherein the method further comprises:

storing the linked resource in a server stack cache in preparation for a subsequent linked resource request.

16. The computing device of claim 11, wherein the method further comprises:

maintaining a linked resource list in a server stack cache.

17. The computing device of claim 11, wherein the method further comprises:

pushing the linked resource to the client device.

18. A server, comprising:

memory configured to store a main resource referencing a linked resource;

a communication interface configured to receive an active initial navigation request for the main resource from a client device; and

a processor configured to;

execute a server application configured to send the main resource in response to the active initial navigation request and to call a linked resource application programming interface to alert a server stack to the linked resource associated with the main resource, and

execute the server stack configured to generate a synthetic linked resource request in response to a linked resource application programming interface call alerting the server stack of the linked resource associated with the main resource of the active initial navigation request and to propagate the synthetic linked resource request through the server stack.

19. The server of claim 18, wherein the communication interface configured to receive an indication of a push capability for the client device.

20. The server of claim 18, further comprising:

a server stack cache configured to store the linked resource in preparation for a subsequent linked resource request.