TECHNIQUES FOR FACILITATING SERVER CALLBACKS

• US 20090276791A1
• Filed: 05/01/2008
• Published: 11/05/2009
• Est. Priority Date: 05/01/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Meijer, Henricus Johannes Maria
• Application Number:
  US12/113,211
• Publication Number:
  US 20090276791A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Various technologies and techniques are disclosed for facilitating server callbacks. A request is received from a client computer to monitor for one or more events for the client computer. The server computer monitors for the one or more events and detects one or more occurrences of the events. Information regarding the one or more occurrences of the events is added to an event queue. On a later communication with the client computer, the event queue is sent as part of a response so the occurrences of the events can be handled on the client computer by one or more event handlers on the client computer. Techniques are also described for enabling server callbacks in execution context splitting scenarios where a region of code has been split across different execution contexts.

Claims

1. A method for facilitating server callbacks comprising the steps of:

receiving a request from a client computer to monitor for one or more events for the client computer;

monitoring for the one or more events;

detecting one or more occurrences of the one or more events;

adding information regarding the one or more occurrences of the one or more events to an event queue; and

on a later communication with the client computer, sending the event queue as part of a response so the one or more occurrences of the one or more events can be handled on the client computer.

2. The method of claim 1, wherein the information added to the event queue includes one or more event delegates needed to handle the one or more events on the client.

3. The method of claim 2, wherein the information added to the event queue further includes one or more parameters needed to handle the one or more events on the client computer.

4. The method of claim 1, wherein the monitoring and detecting steps are handled by a server event handler proxy.

5. The method of claim 1, wherein the later communication with the client computer is a next communication with the client computer.

6. The method of claim 1, wherein the later communication with the client computer is a special ping requests that requests the event queue.

7. The method of claim 1, wherein the later communication with the client computer utilizes an already open connection with the client computer.

8. The method of claim 1, wherein the receiving, monitoring, detecting, adding, and sending steps enable the one or more events to be detected and raised on a server computer but handled on the client computer.

9. The method of claim 1, wherein the receiving, monitoring, detecting, adding, and sending steps are repeated for a plurality of client computers.

10. A method for handling events on a client that were raised on a server comprising the steps of:

receiving an event queue from a server computer on a later communication with the server computer, the event queue containing information regarding one or more events that were detected on the server computer; and

handling each of the one or more events in the event queue using one or more event handlers.

11. The method of claim 10, wherein the information regarding one or more events that is contained in the event queue includes one or more event delegates.

12. The method of claim 10, wherein the information regarding the one or more events that is contained in the event queue includes one or more parameters needed by the one or more event handlers to handle the one or more events.

13. The method of claim 10, wherein the later communication with the server computer is a next communication with the server computer.

14. The method of claim 10, wherein the later communication with the server computer is a special ping request sent to the server computer to request the event queue.

15. The method of claim 10, wherein the later communication with the server computer utilizes an already open connection with the server computer.

16. A computer-readable medium having computer-executable instructions for causing a computer to perform steps comprising:

generating a client proxy with an event handler, the event handler being operable to handle a certain event on a client computer; and

generating a server proxy with an event handler proxy, the event handler proxy being operable to detect one or more occurrences of the certain event on a server computer and put information regarding the one or more occurrences into an event queue for later handling by the event handler of the client proxy.

17. The computer-readable medium of claim 16, wherein the client proxy with the event handler is deployed to the client computer.

18. The computer-readable medium of claim 16, wherein the server proxy with the event handler proxy is deployed to the server computer.

19. The computer-readable medium of claim 16, wherein the client proxy and the server proxy are used to implement execution context splitting for a region of code.

20. The computer-readable medium of claim 16, further having computer-executable instructions for causing a computer to perform steps comprising:

prior to generating the client proxy, accessing one or more annotations associated with a region of code to determine an execution context regarding where the region of code should be executed; and

wherein the client proxy and the server proxy are generated to implement functionality needed to carry out the execution context for the region of code.