Abstract: Techniques for multiuser application platform are described. Generally, a multiuser application allow interaction by multiple different users with a single executing instance of the application. Implementations include a multiuser operating system and a multiuser application programming interface that enable interaction by multiple users with an executing instance of a multiuser application.

Abstract: Registration of an application in a per-user registration model includes the creation and storage of duplicate registration data for multiple user accounts present on a system. This duplication of registration data may be reduced by storing at least a portion of identical data in a per-machine location in the system memory where it is accessible to all user accounts. Instead of needing to separately re-compute and/or re-store duplicate registration data in multiple per-user locations in the memory, each user account may access and utilize the registration data stored in the per-machine location. Pre-computing and storing a portion of the application registration data in a per-machine location in the memory may also allow the system to defer the registration of the application.

Abstract: Techniques for multiuser application platform are described. Generally, a multiuser application allow interaction by multiple different users with a single executing instance of the application. Implementations include a multiuser operating system and a multiuser application programming interface that enable interaction by multiple users with an executing instance of a multiuser application.

Abstract: Registration of an application in a per-user registration model includes the creation and storage of duplicate registration data for multiple user accounts present on a system. This duplication of registration data may be reduced by storing at least a portion of identical data in a per-machine location in the system memory where it is accessible to all user accounts. Instead of needing to separately re-compute and/or re-store duplicate registration data in multiple per-user locations in the memory, each user account may access and utilize the registration data stored in the per-machine location. Pre-computing and storing a portion of the application registration data in a per-machine location in the memory may also allow the system to defer the registration of the application.

Abstract: A request is received from a software component of a software product to access a value of a public setting of the software component. A check is made as to whether the request conforms to an appropriate format for the public setting. If the request conforms to the appropriate format, then the requested access is performed. However, if the request does not conform to the appropriate format, then the requested access is denied. Multiple values for the public setting can be received and maintained concurrently.

Abstract: A request is received from a software component of a software product to access a value of a public setting of the software component. A check is made as to whether the request conforms to an appropriate format for the public setting. If the request conforms to the appropriate format, then the requested access is performed. However, if the request does not conform to the appropriate format, then the requested access is denied. Multiple values for the public setting can be received and maintained concurrently.

Abstract: One or more extension registrations are received for each of multiple software components installed on a computing device. The one or more extension registrations identify the software components as providers of functionality. A record of the one or more extension registrations for each of the multiple software components is maintained. Requests are received, from other software components installed on the computing device, that identify particular functionality. In response to such requests, the information regarding one or more of the multiple software components that provide the particular functionality is returned to the other software components.

Abstract: Multiple software component identifiers are maintained in a catalog of an operating system running on a device. Each of these software component identifiers corresponds to one of multiple software components installed on the device. The catalog is accessed in response to a request regarding one of the multiple software components, and the request is responded to based at least in part on information included in the catalog. Additionally, two or more versions of a software component that are installed on the computing device can be identified. Which one of the two or more versions of the software component is an active version of the software component to be run is determined. In response to requests for information regarding the software component, information regarding the active version of the software component is returned.

Abstract: Multiple software component identifiers are maintained in a catalog of an operating system running on a device. Each of these software component identifiers corresponds to one of multiple software components installed on the device. The catalog is accessed in response to a request regarding one of the multiple software components, and the request is responded to based at least in part on information included in the catalog. Additionally, two or more versions of a software component that are installed on the computing device can be identified. Which one of the two or more versions of the software component is an active version of the software component to be run is determined. In response to requests for information regarding the software component, information regarding the active version of the software component is returned.

Abstract: A request is received from a software component of a software product to access a value of a public setting of the software component. A check is made as to whether the request conforms to an appropriate format for the public setting. If the request conforms to the appropriate format, then the requested access is performed. However, if the request does not conform to the appropriate format, then the requested access is denied. Multiple values for the public setting can be received and maintained concurrently.

Abstract: One or more extension registrations are received for each of multiple software components installed on a computing device. The one or more extension registrations identify the software components as providers of functionality. A record of the one or more extension registrations for each of the multiple software components is maintained. Requests are received, from other software components installed on the computing device, that identify particular functionality. In response to such requests, the information regarding one or more of the multiple software components that provide the particular functionality is returned to the other software components.

Abstract: A request is received from a software component of a software product to access a value of a public setting of the software component. A check is made as to whether the request conforms to an appropriate format for the public setting. If the request conforms to the appropriate format, then the requested access is performed. However, if the request does not conform to the appropriate format, then the requested access is denied. Multiple values for the public setting can be received and maintained concurrently.

Abstract: Multiple software component identifiers are maintained in a catalog of an operating system running on a device. Each of these software component identifiers corresponds to one of multiple software components installed on the device. The catalog is accessed in response to a request regarding one of the multiple software components, and the request is responded to based at least in part on information included in the catalog. Additionally, two or more versions of a software component that are installed on the computing device can be identified. Which one of the two or more versions of the software component is an active version of the software component to be run is determined. In response to requests for information regarding the software component, information regarding the active version of the software component is returned.

Abstract: Monitoring interactions between application programs and data stores for analyzing stability of application programs. A method of the invention intercepts interactions from a plurality of application programs to a data store. The method also identifies pre-execution data relating to each of the intercepted interactions and the intercepted interaction is executed. The method identifies post-execution data relating to each of the executed interactions. The identified pre-execution data and the identified post-execution data from each of the interactions are normalized to create normalized interaction data for each of the interactions. The method combines the normalized interaction data for each of the interactions as a function of the application programs associated with each of the interactions. The method further stores the combined interaction data for analysis of the interactions between the application programs and the data store which is indicative of the stability of the application programs.