Abstract: A machine includes a number of slots. Each of the slots is configured to receive one or more components for implementing some functionality role of the slot in the machine. The machine further includes one or more replaceable components in each of the slots. The components are configured to communicate (or be communicated for) on behalf of a slot or the machine, to an external system(s). The external system(s) implement rules to perform authorization or other operations based on the role of the slot in the context of the machine. A different derived key is used to communicate by or for each component with the external system. Each derived key for a component is derived from a machine proof for the machine and information identifying the slot in which the component is installed.

Abstract: A machine includes a number of slots. Each of the slots is configured to receive one or more components for implementing some functionality role of the slot in the machine. The machine further includes one or more replaceable components in each of the slots. The components are configured to communicate (or be communicated for) on behalf of a slot or the machine, to an external system(s). The external system(s) implement rules to perform authorization or other operations based on the role of the slot in the context of the machine. A different derived key is used to communicate by or for each component with the external system. Each derived key for a component is derived from a machine proof for the machine and information identifying the slot in which the component is installed.

Abstract: The present invention extends to methods, systems, and computer program products for implementing a tenant provisioning system in a multi-tenancy architecture using a single provisioning master in the architecture, and a data center provisioner in each data center in the architecture. The provisioning master receives user requests to provision a tenant of a service and routes such requests to an appropriate data center provisioner. Each service in the multi-tenancy architecture implements a common interface by which the corresponding data center provisioner can obtain a common indication of load from each different service deployed in the data center thus facilitating the selection of a scale unit on which a tenant is provisioned. The common interface also enables a service to dynamically register (i.e. without redeploying the tenant provisioning system) with the provisioning master as a multi-tenancy service by registering an endpoint address with the provisioning master.

Abstract: Providing a badge counter from a server to a consumer. The badge counter indicates a number of notifications. A method includes receiving an event in a sequence of events. The event has an associated time stamp. The method further includes associating with the event a plurality of additional time stamps from events in the sequence of events occurring before the event. The method further includes creating a notification for an end user consumer device, the notification including an indication of a badge counter value based on the plurality of additional time stamps. The method further includes sending the notification, including badge counter value to the consumer device.

Abstract: Events can be emitted by a method that includes acquiring data from a plurality of different sources by communicating to the different sources using a plurality of different protocols specific to the different sources and, based on the acquired data, determining that an event should occur. The method can further include causing an event that is normalized for a consistent event evaluation by consumers irrespective of the specific shape of the data from the data source resulting in the event.

Abstract: Distributing an event to a plurality of end users. A method includes receiving a normalized event that a plurality of users have subscribed to receive. The event has data about the event in a normalized form. The method further includes evaluating user preferences of one or more of the plurality of users. The user preferences are expressed in a format matching the format of the normalized form. The method further includes, based on the evaluation, selecting a subset of the plurality of users. The method further includes packaging the event into a delivery bundle with a routing slip identifying the subset of the plurality of users. The method further includes using the delivery bundle, distributing the event to the subset of the plurality of users.

Abstract: The present invention extends to methods, systems, and computer program products for implementing a tenant provisioning system in a multi-tenancy architecture using a single provisioning master in the architecture, and a data center provisioner in each data center in the architecture. The provisioning master receives user requests to provision a tenant of a service and routes such requests to an appropriate data center provisioner. Each service in the multi-tenancy architecture implements a common interface by which the corresponding data center provisioner can obtain a common indication of load from each different service deployed in the data center thus facilitating the selection of a scale unit on which a tenant is provisioned. The common interface also enables a service to dynamically register (i.e. without redeploying the tenant provisioning system) with the provisioning master as a multi-tenancy service by registering an endpoint address with the provisioning master.

Abstract: Delivering data. A method includes determining a relative monetary value of data, with respect to time, at a particular point in time. The method further includes based on the determined monetary value providing the data to a set of one or more end user consumer devices for consumers correlated to the monetary value.

Abstract: Delivering events to consumers. A method includes accessing proprietary data. The method further includes normalizing the proprietary data to create a normalized event. A plurality of end consumers is determined, that based on a subscription should receive the event. Data from the normalized event is formatted into a plurality of different formats appropriate for all of the determined end consumers. Data from the normalized event is delivered to each of the plurality of end consumers in a format appropriate to the end consumers.

Abstract: Emitting events. A method includes acquiring data from a plurality of different sources by communicating to the different sources using a plurality of different protocols specific to the different sources. The method further includes, based on the acquired data, determining that an event should occur. The method further includes causing an event. The caused event is normalized for a consistent event evaluation by consumers irrespective of the specific shape of the data from the data source resulting in the event.

Abstract: Delivering a notification to a user device. One method includes receiving a generic event as part of a broadcast of the generic event to a plurality of consumers. The method further includes mapping the generic event to a specific notification for a specific end user consumer. The method further includes delivering the specific notification to the end user consumer.

Abstract: Distributing events to a large number of event consumers in a fashion that may minimize message copying and message latency. A method includes determining that an event should be sent to a set of specific consumers. The method further includes copying the event and providing individual copies to a plurality of distribution partitions. The method further includes, at each of the distribution partitions packaging a copy of the event with a plurality of routing slips to create a plurality of delivery bundles. The routing slips describing a plurality of individual consumers intended to receive the event. The method further includes using the delivery bundles, distributing the events to individual consumers as specified in the routing slips.

Abstract: Distributing an event to a plurality of end users. A method includes receiving a normalized event that a plurality of users have subscribed to receive. The event has data about the event in a normalized form. The method further includes evaluating user preferences of one or more of the plurality of users. The user preferences are expressed in a format matching the format of the normalized form. The method further includes, based on the evaluation, selecting a subset of the plurality of users. The method further includes packaging the event into a delivery bundle with a routing slip identifying the subset of the plurality of users. The method further includes using the delivery bundle, distributing the event to the subset of the plurality of users.

Abstract: Providing a badge counter from a server to a consumer. The badge counter indicates a number of notifications. A method includes receiving an event in a sequence of events. The event has an associated time stamp. The method further includes associating with the event a plurality of additional time stamps from events in the sequence of events occurring before the event. The method further includes creating a notification for an end user consumer device, the notification including an indication of a badge counter value based on the plurality of additional time stamps. The method further includes sending the notification, including badge counter value to the consumer device.

Abstract: The present invention extends to methods, systems, and computer program products for dispatching client requests to appropriate server-side methods. When a client request is received, a Web server refers to a service contract framework that maps URI paths and HTTP methods to corresponding server implemented methods. A server implemented method corresponding to a URI path and/or an HTTP method included in the client request is identified. The server implemented method is invoked to process the client request message. Accordingly, embodiments of the invention provide a uniform mechanism to dispatch HTTP requests to designated server implemented methods based solely on URI path and HTTP method. That is, an HTTP request can be dispatched to a designated server implemented method without having to include additional dispatch metadata within the HTTP request (e.g., in a SOAP envelope).

Abstract: The present invention extends to methods, systems, and computer program products for dispatching client requests to appropriate server-side methods. When a client request is received, a Web server refers to a service contract framework that maps URI paths and HTTP methods to corresponding server implemented methods. A server implemented method corresponding to a URI path and/or an HTTP method included in the client request is identified. The server implemented method is invoked to process the client request message. Accordingly, embodiments of the invention provide a uniform mechanism to dispatch HTTP requests to designated server implemented methods based solely on URI path and HTTP method. That is, an HTTP request can be dispatched to a designated server implemented method without having to include additional dispatch metadata within the HTTP request (e.g., in a SOAP envelope).