System and method for tracking notifications in a publish subscribe system

• US 8,165,992 B2
• Filed: 11/20/2007
• Issued: 04/24/2012
• Est. Priority Date: 11/04/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Rooney, Sean G.
• Primary Examiner(s): Radtke, Mark Andrwe X
• Application Number:
  US11/943,567
• Publication Number:
  US 20080082562A1
• Time in Patent Office: 1,617 Days
• Field of Search: 707/627
• US Class Current: 707/627
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

A system and method are provided for tracking notification messages from a message publisher to a message subscriber. The system includes a plurality of entities that are operatively coupled to one another via an electronic network, and each entity includes at least one processor configured as a message publisher, a channel and/or a message subscriber. According to the invention, at least one entity is configured as a channel, which is assigned to the function of acting as a meta-channel and comprises (i) means for receiving one or more channel descriptions; and (ii) means for publishing a digest of one or more channel descriptions and/or message transformations to facilitate tracking of message transformations from raw forms to processed forms. The system may have more than one meta-channel, and the meta-channels may subscribe to or publish to each other.

Claims

1. A method for tracking notification messages from a message publisher to a message subscriber, in a publish/subscribe system having one or more entities each configured as one or more of a message publisher, a channel and a message subscriber, the method comprising:

subscribing to a meta-channel, said meta-channel receiving descriptions of one or more associated channels, each said channel description indicating how notifications are presented by a publisher, or aggregated or transformed by a publisher so as to supercede notifications received by the publisher acting as a subscriber and thereby reduce a load upon the system, so that a subscriber to a channel having aggregated or transformed notifications receives the aggregation or transformation rather than the superceded notifications, the aggregation or transformation then becoming incorporated into subsequent notifications when the subscriber is configured as a publisher after having further aggregated or transformed what has been received from the channel;

receiving a digest of said channel descriptions from said meta-channel, said digest indicating how notifications are superceded thereby enabling a subscriber or a publisher, respectively, to discriminate between channels and to switch to channels providing superceding notifications based on said discrimination, wherein said switching of channels based on said discrimination serves to automatically reconfigure said publish/subscribe system in response to overloading or failure of one or more channels in said system;

receiving a digest of one or more transformation description messages from said meta-channel, said digest enabling a subscriber to track evolution of message transformations from raw forms to processed forms and to switch publishers based on said tracking, the evolution progressing from superceded to superceding notifications; and

using said transformation description messages to track said evolution of message transformations in order to determine where to subscribe.

2. The method of claim 1, further comprising:

subscribing to a first channel in response to the tracking of message transformations; and

dropping a subscription to a second channel in response to determining that the first channel publishes one or more notifications in a more processed form than a notification from the second channel.

3. The method of claim 1, wherein the message transformations in processed form comprise aggregations of messages in raw form.

4. The method of claim 1, wherein the message transformations in processed form comprise transformations of messages in raw form.

5. The method of claim 1, further comprising publishing aggregated notifications.

6. The method of claim 1, further comprising publishing transformed notifications.

7. The method of claim 1, wherein the message transformations are formatted in accordance with XML specifications.

8. The method of claim 1, wherein the digest of said channel descriptions describes one or more of a channel and the meta-channel.

9. The method of claim 1, wherein each of the one or more channel descriptions comprises one or more of:

the publish/subscribe system'"'"'s type;

information needed to connect to a channel associated with the channel description;

one or more message types that is accepted by the channel associated with the channel description; and

one or more message types that is currently being published or subscribed to by the channel associated with the channel description.

10. The method of claim 1, wherein each of the one or more channel descriptions comprises load information pertaining to the channel associated with the channel description.

11. The method of claim 10, further comprising:

in response to the load information, discriminating between first and second channels offering similar functionality.

12. The method of claim 11, further comprising:

subscribing to the first channel in response to determining that the second channel is overloaded.

13. The method of claim 11, further comprising:

publishing to the first channel in response to determining that the second channel is overloaded.

14. The method of claim 1, wherein each of the one or more channel descriptions comprises information pertaining to a refresh period between a publication of a first channel description and a publication of a second channel description.

15. The method of claim 14, further comprising:

in response to the information pertaining to the refresh period, and in response to nonreception of a second channel description after a time period proportional to the refresh period, determining that a channel has stopped publishing notifications.

16. The method of claim 15, further comprising adjusting a refresh period for a channel in response to information pertaining to a refresh period for the meta-channel.

17. The method of claim 1, wherein the transformation description message pertaining to an entity comprises one or more of:

information identifying a set of channels and message types for messages that the entity is reading;

information identifying a set of channels and message types for messages that the entity is writing; and

a refresh period.