Abstract: Methods and apparatuses that generate a subtopic identifier identifying a client application within a client device that can support multiple users are described. The client application may be associated with a server application hosted in one or more application servers. Notification services may be registered with the application servers from the client application to forward identifiers associated with the client application for one of the multiple users to the server application to enable the server application to push notification messages to the client device selectively for the client application for that user. When receiving a notification message from the application server, the notification message may be examined to forward the notification message directly to the client application for that user without invoking other applications in the client device if the notification message carries a subtopic identifier of the client application.

Abstract: Methods and apparatuses that generate a subtopic identifier identifying a client application within a client device that can support multiple users are described. The client application may be associated with a server application hosted in one or more application servers. Notification services may be registered with the application servers from the client application to forward identifiers associated with the client application for one of the multiple users to the server application to enable the server application to push notification messages to the client device selectively for the client application for that user. When receiving a notification message from the application server, the notification message may be examined to forward the notification message directly to the client application for that user without invoking other applications in the client device if the notification message carries a subtopic identifier of the client application.

Abstract: Methods and apparatuses that generate a subtopic identifier identifying a client application within a client device that can support multiple users are described. The client application may be associated with a server application hosted in one or more application servers. Notification services may be registered with the application servers from the client application to forward identifiers associated with the client application for one of the multiple users to the server application to enable the server application to push notification messages to the client device selectively for the client application for that user. When receiving a notification message from the application server, the notification message may be examined to forward the notification message directly to the client application for that user without invoking other applications in the client device if the notification message carries a subtopic identifier of the client application.

Abstract: User preferences and configuration information are determined automatically when a user account is created. The configuration information is derived from service configuration files. The user account and configuration information is stored in a directory such that it is accessible by a client and applied to applications executing on the client.

Abstract: A server device sends a list of account holders together with an invitation to bind to the server. A client device can decide to present the invitation to a user for decision only if the client device finds a match between the list and the user.

Abstract: A server device sends a list of account holders together with an invitation to bind to the server. A client device can decide to present the invitation to a user for decision only if the client device finds a match between the list and the user.

Abstract: A server device sends a list of account holders together with an invitation to bind to the server. A client device can decide to present the invitation to a user for decision only if the client device finds a match between the list and the user.

Abstract: Methods and apparatuses that generate a subtopic identifier identifying a client application within a client device that can support multiple users are described. The client application may be associated with a server application hosted in one or more application servers. Notification services may be registered with the application servers from the client application to forward identifiers associated with the client application for one of the multiple users to the server application to enable the server application to push notification messages to the client device selectively for the client application for that user. When receiving a notification message from the application server, the notification message may be examined to forward the notification message directly to the client application for that user without invoking other applications in the client device if the notification message carries a subtopic identifier of the client application.

Abstract: A server device sends a list of account holders together with an invitation to bind to the server. A client device can decide to present the invitation to a user for decision only if the client device finds a match between the list and the user.

Abstract: A server device sends a list of account holders together with an invitation to bind to the server. A client device can decide to present the invitation to a user for decision only if the client device finds a match between the list and the user.

Abstract: A server device sends a list of account holders together with an invitation to bind to the server. A client device can decide to present the invitation to a user for decision only if the client device finds a match between the list and the user.

Abstract: User preferences and configuration information are determined automatically when a user account is created. The configuration information is derived from service configuration files. The user account and configuration information is stored in a directory such that it is accessible by a client and applied to applications executing on the client.

Abstract: Multiple devices are automatically configured within a cluster through the use of exclusive file locks in a shared file system. The devices execute a process to determine the health of the enabled services and check for failed services. Actions are tailored based upon which services and roles are enabled for a specific device to maintain a relationship and sharing of information and data between the devices.