COMMUNICATING EVENTS OR DATA BETWEEN APPLICATION COMPONENTS

• US 20100257540A1
• Filed: 04/03/2009
• Published: 10/07/2010
• Est. Priority Date: 04/03/2009
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Schuler, Patrick, Pettit, Bradley R.
• Granted Patent: US 9,135,091 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

This document describes tools capable of communicating events or event data between application components. These tools allow an application component to communicate an event and event data to another application component even if the two application components are in separate layers or do not exist at the same time.

Claims

1. A method comprising:

receiving an event from a first application component, the event including data that is associated with the event;

communicating a notification of the event to a second application component without the data that is associated with the event; and

communicating the data to an event-data store that maintains the data for access by the second application component.

2. The method as recited in claim 1, wherein the event-data store allows a third application component to access the data, the third application component not having received a notification of the event.

3. The method as recited in claim 2, wherein the third application component binds to a data source associated with the event.

4. The method as recited in claim 3, wherein the data source associated with the event is set to expire at a specific date/time, after a specific duration, when the first application component exits, or when a computing device on which the event-data store is located restarts.

5. The method as recited in claim 2, wherein the second and third application components exist within a different layer than the first application component.

6. The method as recited in claim 2, wherein the first, second, and third application components are components of different applications.

7. The method as recited in claim 2, wherein the third application component is not in existence at the time that the event is received.

8. The method as recited in claim 2, wherein the first, second, and third application components are not aware of each others'"'"' existence.

9. The method as recited in claim 1, further comprising receiving, from the second application component, a registration to receive a notification of the event.

10. The method as recited in claim 1, wherein the second application component is configured to perform an action upon receiving the notification of the event.

11. The method as recited in claim 1, wherein the first application component attaches the data to the event in the query portion of a Uniform Resource Identifier.

12. The method as recited in claim 1, wherein the first application component attaches the data to the event through a data container declared within the first application component.

13. An apparatus comprising:

an event-dispatching module; and

an event-data store,

the event-dispatching module capable of;

receiving an event from a first application component, the event including data that is associated with the event;

communicating a notification of the event to a second application component without the data that is associated with the event; and

communicating the data to the event-data store, and

the event-data store capable of;

receiving, from the event-dispatching module, the data associated with the event; and

maintaining the data for access by the second application component.

14. The apparatus as recited in claim 13, wherein the event-data store is capable of allowing a third application component to access the data, the third application component not having received a notification of the event.

15. The apparatus as recited in claim 14, wherein the first application component is not in existence at the time that the third application component accesses the data.

16. The apparatus as recited in claim 14, wherein the first, second, and third application components exist within different layers.

17. The apparatus as recited in claim 13, wherein the first and second application components are components of the same application.

18. The apparatus as recited in claim 13, wherein the event-dispatching module is further capable of receiving, from the second application component, a registration to receive a notification of the event.

19. The apparatus as recited in claim 13, wherein the second application component is configured to perform an action upon receiving the notification of the event.

20. One or more tangible computer-readable media having stored thereon computer-executable instructions that, if executed by a computing device, cause the computing device to perform a method comprising:

receiving, from an application component, a registration to receive notifications of a predefined application-specific event;

receiving the predefined application-specific event from another application component, the predefined application-specific event including data that is associated with the predefined application-specific event;

communicating a notification of the predefined application-specific event to the application component without the data that is associated with the predefined application-specific event; and

communicating the data to an event-data store that maintains the data for access by the application component, the application component being configured to access the data maintained in the event-data store upon receiving the notification of the predefined application-specific event, the event-data store configured to maintain the data for access by an application component different than the application component or the other application component, the different application component not having received a notification of the predefined application-specific event.