Abstract: The present disclosure concerns methods and systems for registering dynamically created packaged applications with an operating system. A dynamically created packaged application may not include a way to authenticate the packaged application but may declare a dependency on a host package. The host package may include a verified signature and be registered with the operating system. The host package may include a host runtime that references an executable included in the host package. The packaged application may not include executable files but may reference the host runtime. The operating system may register the packaged application based in part on its dependency on the host package. When the packaged application is activated, the packaged application may invoke the host runtime and the executable but do so with an application identity of the packaged application. The application identity may be different from a host runtime identity of the host runtime.

Abstract: The present disclosure concerns methods and systems for registering dynamically created packaged applications with an operating system. A dynamically created packaged application may not include a way to authenticate the packaged application but may declare a dependency on a host package. The host package may include a verified signature and be registered with the operating system. The host package may include a host runtime that references an executable included in the host package. The packaged application may not include executable files but may reference the host runtime. The operating system may register the packaged application based in part on its dependency on the host package. When the packaged application is activated, the packaged application may invoke the host runtime and the executable but do so with an application identity of the packaged application. The application identity may be different from a host runtime identity of the host runtime.

Abstract: The present disclosure concerns methods and systems for registering dynamically created packaged applications with an operating system. A dynamically created packaged application may not include a way to authenticate the packaged application but may declare a dependency on a host package. The host package may include a verified signature and be registered with the operating system. The host package may include a host runtime that references an executable included in the host package. The packaged application may not include executable files but may reference the host runtime. The operating system may register the packaged application based in part on its dependency on the host package. When the packaged application is activated, the packaged application may invoke the host runtime and the executable but do so with an application identity of the packaged application. The application identity may be different from a host runtime identity of the host runtime.

Abstract: The present disclosure concerns methods and systems for registering dynamically created packaged applications with an operating system. A dynamically created packaged application may not include a way to authenticate the packaged application but may declare a dependency on a host package. The host package may include a verified signature and be registered with the operating system. The host package may include a host runtime that references an executable included in the host package. The packaged application may not include executable files but may reference the host runtime. The operating system may register the packaged application based in part on its dependency on the host package. When the packaged application is activated, the packaged application may invoke the host runtime and the executable but do so with an application identity of the packaged application. The application identity may be different from a host runtime identity of the host runtime.

Abstract: Mechanisms for synchronizing an object set with a remote data store are often performed at a particular frequency, e.g., once per hour or day. However, the objects of the object set may have different priorities, and it may be advantageous to synchronize higher-priority objects more often than regular-priority objects. The synchronization mechanisms may also differ (e.g., high-priority object synchronization may be direct and/or holistic, while regular-priority object synchronization may be differential, cached, and/or involving version and/or conflict resolution). Additionally, a resource-based threshold may be applied to the high-priority objects (e.g., a bandwidth cap) in order to reduce resource exhaustion, and high-priority objects that are not synchronized within the threshold may be synchronized with the regular-priority objects.

Abstract: Mechanisms for synchronizing an object set with a remote data store are often performed at a particular frequency, e.g., once per hour or day. However, the objects of the object set may have different priorities, and it may be advantageous to synchronize higher-priority objects more often than regular-priority objects. The synchronization mechanisms may also differ (e.g., high-priority object synchronization may be direct and/or holistic, while regular-priority object synchronization may be differential, cached, and/or involving version and/or conflict resolution). Additionally, a resource-based threshold may be applied to the high-priority objects (e.g., a bandwidth cap) in order to reduce resource exhaustion, and high-priority objects that are not synchronized within the threshold may be synchronized with the regular-priority objects.

Abstract: System and method for analyzing the impact of interactions of application programs with resources stored in a data store. A method of the invention receiving a selection of the application programs from a user. The interactions of the resources by the selected application programs are identified. The method also determines access types for each of the interactions of the resources by the selected application programs. The method further selects a set of the identified interactions and the determined access types that corresponds to a map, said map including a predefined set of interactions having access types associated therewith. The map with the selected set of the identified interactions and the determined access types is provided to the user. For example, the map identifies potential resource conflicts. Alternatively, the method generates a report including the map.

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.

Abstract: Managing the installation, execution, and removal of application programs by an operating system via an application identity associated with each application program. A method of the invention assigns the application identity to each application program and a resource identity to each resource associated with each application program. The method relates the assigned application identity and resource identity to enable manipulation of the application program and its resources.