Flexible subscription-based event notification
First Claim
1. A computer program product for use in a computer system that includes one or more event sources and one or more event consumers, the computer program product comprising one or more computer storage media having computer-executable instructions for implementing a method for conditionally processing events fired by the one or more event sources based on subscriptions received by one or more event consumers, wherein the method comprises:
- receiving an event notification from an event source for an event structured in accordance with a schema definition;
receiving one or more subscriptions from one or more event consumers, wherein the receiving one or more subscriptions from one or more event consumers comprises receiving a subscription request from a requesting entity for event notifications having particular characteristics to be sent to a receiving event consumer and wherein the subscription request represents a node characteristic within the schema definition;
determining the position where the event notification would fit into the schema definition based on a classification of the event notification;
matching the event notification against the one or more subscriptions received from the one or more event consumers, wherein matching the event notification comprises;
determining whether the schema definition position represented by the subscription request corresponds to the position where the event notification would fit into the schema definition; and
determining whether the node characteristic represented by the subscription request corresponds to the node characteristics corresponding to the position where the notification would fit into the schema definition; and
filtering the event notification based on the one or more subscriptions.
1 Assignment
0 Petitions
Accused Products
Abstract
Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.
28 Citations
16 Claims
-
1. A computer program product for use in a computer system that includes one or more event sources and one or more event consumers, the computer program product comprising one or more computer storage media having computer-executable instructions for implementing a method for conditionally processing events fired by the one or more event sources based on subscriptions received by one or more event consumers, wherein the method comprises:
-
receiving an event notification from an event source for an event structured in accordance with a schema definition; receiving one or more subscriptions from one or more event consumers, wherein the receiving one or more subscriptions from one or more event consumers comprises receiving a subscription request from a requesting entity for event notifications having particular characteristics to be sent to a receiving event consumer and wherein the subscription request represents a node characteristic within the schema definition; determining the position where the event notification would fit into the schema definition based on a classification of the event notification; matching the event notification against the one or more subscriptions received from the one or more event consumers, wherein matching the event notification comprises; determining whether the schema definition position represented by the subscription request corresponds to the position where the event notification would fit into the schema definition; and determining whether the node characteristic represented by the subscription request corresponds to the node characteristics corresponding to the position where the notification would fit into the schema definition; and filtering the event notification based on the one or more subscriptions. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
Specification