Distributed publish-subscribe event system with routing of published events according to routing tables updated during a subscription process

• US 20080307436A1
• Filed: 06/06/2007
• Published: 12/11/2008
• Est. Priority Date: 06/06/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hamilton, Keith S.
• Application Number:
  US11/810,530
• Publication Number:
  US 20080307436A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 2209/546 Xcast
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A publish-subscribe event system for a set of communicating machines, where when a machine receives an event, whether a published event or a subscription event, it publishes locally the received event by an inter-process communication in the machine. In this way, the event is made available to other processes on the machine. For some embodiments, an event is published locally in a machine by placing it in shared memory. During a subscription process, each machine updates its routing table as subscription events are received. When a published event is received by a machine, it is published locally by the inter-process communication in the machine, where the one or more subscribing applications on the machine may have access to it. The received published event is also routed to other connected machines according to the machine'"'"'s routing table. Other embodiments are described and claimed.

Claims

1. A method comprising:

receiving at a machine a published event;

publishing locally in the machine the published event by an inter-process communication;

accessing the published event by a subscribing application running on the machine if the subscribing application subscribes to the published event; and

forwarding the published event according to a routing table stored in the machine.

2. The method as set forth in claim 1, wherein publishing locally in the machine the published event by the inter-process communication comprises placing the published event into a shared memory.

3. The method as set forth in claim 1, further comprising:

receiving at the machine a subscription event over a communication channel, the subscription event having a subscribed-to event type; and

managing the routing table in the machine so that the subscribed-to event type is associated with the communication channel over which the subscription event was received.

4. The method as set forth in claim 3, wherein the communication channel comprises a Transmission Control Protocol socket connection.

5. The method as set forth in claim 1, further comprising:

initiating a subscription event at the machine;

publishing locally in the machine the subscription event by the inter-process communication; and

forwarding the subscription event over all outgoing communication channels of the machine if the subscription event is not marked as local-only.

6. The method as set forth in claim 5, further comprising:

receiving at the machine a second subscription event over a communication channel, the second subscription event having a subscribed-to event type; and

managing the routing table in the machine so that the subscribed-to event type is associated with the communication channel over which the subscription event was received.

7. The method as set forth in claim 5, wherein publishing locally in the machine the subscription event by the inter-process communication comprises placing the subscription event into a shared memory

8. A method comprising:

receiving at a machine a subscription event over a communication channel; and

updating a routing table to associate the subscription event with the communication channel.

9. The method as set forth in claim 8, wherein the communication channel comprises a Transmission Control Protocol socket connection.

10. The method as set forth in claim 8, the subscription event having a subscribed-to event type, wherein when updating the routing table the subscribed-to event type is associated with the communication channel.

11. The method as set forth in claim 10, further comprising:

if a published event is received having an event type in the routing table, then forwarding the published event according to the routing table.

12. The method as set forth in claim 10, further comprising:

publishing locally in the machine a published event by an inter-process communication; and

accessing the published event by a subscription application that subscribes to the published event.

13. The method as set forth in claim 12, further comprising:

if the published event was received having an event type in the routing table, then forwarding the published event according to the routing table.

14. The method as set forth in claim 12, wherein publishing locally in the machine the published event by the inter-process communication comprises placing the published event into a shared memory

15. An article of manufacture comprising a computer readable media, which when read by a computer causes the computer to update a routing table to associate a received subscription event with a communication channel.

16. The article of manufacture as set forth in claim 15, the subscription event having an event type to which it subscribes to, the computer readable media further causing the computer to update the routing table to associate the event type to which it subscribes to with the communication channel.

17. The article of manufacture as set forth in claim 16, the computer readable media further causing the computer to forward a received published event according to the routing table if the received published event has an event type in the routing table.

18. The article of manufacture as set forth in claim 16, the computer readable media causing a subscription application running on the computer to access a received published event if the subscription application has subscribed to the published event.

19. The article of manufacture as set forth in claim 18, the computer readable media further causing the computer to forward the received published event according to the routing table if the received published event has an event type in the routing table.

20. The article of manufacture as set forth in claim 15, wherein the communication channel comprises a Transmission Control Protocol socket connection.