# US 2008/0307436 A1 · Distributed publish-subscribe event system with routing of published events according to routing tables updated during a subscription process

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0307436 A1
- Document ID: US20080307436A1
- Status: Published application
- Kind: A1
- Application number: 11/810,530
- Filed: 2007-06-06
- Published: 2008-12-11
- Earliest claimed: 2007-06-06
- Assignees: Microsoft Corporation
- Inventors: Keith S. Hamilton
- Web page: https://patentgrep.com/patent/US20080307436A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 2209/544: Remote
- G06F 2209/546: Xcast
- H04L 67/63: Routing a service request depending on the request content or context
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## 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

### Claim 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.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

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.

### Claim 4 (depends on 3)

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

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 5)

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.

### Claim 7 (depends on 5)

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

### Claim 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.

### Claim 9 (depends on 8)

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

### Claim 10 (depends on 8)

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.

### Claim 11 (depends on 10)

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.

### Claim 12 (depends on 10)

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.

### Claim 13 (depends on 12)

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.

### Claim 14 (depends on 12)

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

### Claim 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.

### Claim 16 (depends on 15)

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.

### Claim 17 (depends on 16)

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.

### Claim 18 (depends on 16)

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.

### Claim 19 (depends on 18)

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.

### Claim 20 (depends on 15)

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