Abstract: Extensible architecture for template-baser user setting management by creating logical groupings of per-user settings using different template types. A manageable way to assign templates to sets of users based on different criteria is provided. Templates can be defined in a declarative format (e.g., XML), which declarative format is developed such that various user interface (UI) pieces, third-party applications, and different client types can easily understand the templates. Extensibility of the architecture is supported for defining the templates such that external third-party application writers can make use of the provided infrastructure to add to existing templates or create new template types, and to seamlessly integrate into the existing infrastructure. Additionally, the per-user settings within the templates can be enforced on the server side, including the enforcement of future settings and template types.

Abstract: A conference room endpoint facility enables a user to schedule conferences directly with the conference room endpoint facility without the need for a central data store to save the conference-specific information. For each scheduled conference, the conference room endpoint facility may store the conference data in a blob, and the lob is stored locally with each invited conference attendee. At the time of joining a scheduled conference, each attendee presents its copy of the blob containing the meeting data to the conference room endpoint facility. The conference room endpoint facility validates the conference data and, upon validating the conference data, admits the submitting conference attendee into the conference.

Abstract: A task infrastructure that allows for the decoupling of the task launch code from the task client code and from the task execution code is provided. The task infrastructure allows the relationship between the task display and launch logic and the task client logic to be defined in a declarative manner, allowing for the segregation of the task display and launch logic from the task client logic. The task infrastructure comprises a manifest that contains a specification of the relationship between the task display and launch logic and the task client logic. The manifest may also define which task clients expose which tasks, the context under which each task is displayed, the arguments that the task needs in order to start execution, the task description to display, and the method in which the task can be launched. At run-time, a task client can read the manifest and decide which task or tasks to expose to an end user under a current context.

Abstract: A framework for declarative expression of data processing is provided. The framework allows for data to be represented by its metadata in a declarative manner, allowing for the generation of code at, for example, build time. The declarative representation of the metadata facilitates the separation of the data (e.g., the raw data that is stored in a data store and that is available using, for example, a data store adapter) from the code (e.g., the code that is executed for the manipulation and validation of data) and the view (e.g., the form that the data is shown to a user, for example, through a UI).

Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: A novel patient-convenient, cost effective pharmaceutical composition, comprising of thiazolidinediones and biguanide for controlling hyperglycemia manufactured as multilayer tablet and its process of manufacturing, for immediate release of thiazolidinediones or thiazolidinediones and biguanide and prolonged release of the biguanide only, the tablet comprising of minimum two layers wherein one outer layer comprises of a mixture of excipients and thiazolidinediones or thiazolidinediones and biguanide allowing immediate release of thiazolidinediones or thiazolidinediones and biguanide respectively and the other layer arranged in contact with the immediate release layer which comprises of a novel composition of excipients and a minimum one or more non-biodegradable, inert polymer(s) and the biguanide allowing pH independent prolonged release of the biguanide up to a period of 8-12 hours. The tablets are for once a day dosing.