Abstract: A network routes update messages containing updates to properties of live objects from input sources to clients having the objects. When the clients receive live objects, the clients identify the object IDs associated with the objects and register the object IDs with the routing network. The routing network is adapted to selectively send update messages to nodes in the network and the nodes forward the messages to the clients. One implementation uses a hierarchy of registries to indicate which nodes and clients receive which update messages. Another implementation assigns update messages to one or more of N categories and nodes to one or more of M types, and the gateways maintain mapping between categories and types. To ensure that clients receive all of the update messages for which they register, the clients connect to client proxies that in turn connect to at least one node of each type.

Abstract: Each of a plurality of thread boundaries comprises functionality to be performed for a given event by a single thread. A plurality of queues through which events may be routed may be coupled to the thread boundaries. A plurality of tasks may be configured in a defined relationship, each task being associated with a thread boundary and comprising a unit of code for performing a specific function. Resources may be allocated to thread boundaries based on queue depth.

Abstract: Techniques for dynamically updating a live object with personalized content for clients are provided. The techniques include receiving a first message from a source including a first identifier and a second identifier. The first identifier may be unique to a client. The second identifier may be generic across many clients. The first message includes information for updating a property of a live object associated with the second identifier. A client specific to the first identifier may be identified. A second message may then be routed through a network to the client. The second message may include the first identifier and the second identifier and also may contain information for updating a property of the live object associated with the second identifier. The client may receive the second message and may be capable of causing an update of the property of the live object associated with the second identifier.

Abstract: Each of a plurality of thread boundaries comprises functionality to be performed for a given event by a single thread. A plurality of queues through which events may be routed may be coupled to the thread boundaries. A plurality of tasks may be configured in a defined relationship, each task being associated with a thread boundary and comprising a unit of code for performing a specific function. Resources may be allocated to thread boundaries based on queue depth.

Abstract: Techniques for dynamically updating a live object with personalized content for clients are provided. The techniques include receiving a first message from a source including a first identifier and a second identifier. The first identifier may be unique to a client. The second identifier may be generic across many clients. The first message includes information for updating a property of a live object associated with the second identifier. A client specific to the first identifier may be identified. A second message may then be routed through a network to the client. The second message may include the first identifier and the second identifier and also may contain information for updating a property of the live object associated with the second identifier. The client may receive the second message and may be capable of causing an update of the property of the live object associated with the second identifier.

Abstract: A network routes update messages containing updates to properties of live objects from input sources to clients having the objects. When the clients receive live objects, the clients identify the object IDs associated with the objects and register the object IDs with the routing network. The routing network is adapted to selectively send update messages to nodes in the network and the nodes forward the messages to the clients. One implementation uses a hierarchy of registries to indicate which nodes and clients receive which update messages. Another implementation assigns update messages to one or more of N categories and nodes to one or more of M types, and the gateways maintain mapping between categories and types. To ensure that clients receive all of the update messages for which they register, the clients connect to client proxies that in turn connect to at least one node of each type.