Virtualizing Access to Named System Objects via Isolated Scopes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Incompatible software application programs and versions often face compatibility and sociability issues when executed on the same computer system, leading to conflicts over shared native resources like the file system and registry database, especially in multi-user environments where multiple users access the same resources.
Innovation Solution
The solution involves virtualizing user and application access to native resources such as the file system, registry database, and system objects, allowing multiple applications to operate independently by creating isolated scopes for each application and user, without modifying the underlying operating system or applications, and storing virtualized resources in their native format for management using standard tools.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple incompatible application programs are executed on the same computer system, then the system can provide diverse functionality, but conflicts arise over shared native resources such as file system and registry database
Solution Approach 1:
The patent segments the shared native resources into application-specific isolated scopes. Each application program is assigned its own isolation scope that contains private copies of resources like file system directories and registry keys. This segmentation prevents conflicts between applications by ensuring that each application accesses only its own private resources, eliminating the resource access instability that would otherwise occur when multiple incompatible applications share the same system resources.
Solution Approach 2:
The patent introduces an intermediary layer (the isolation scope mechanism) between application programs and native resources. This intermediary automatically manages resource allocation and isolation, translating application resource requests into scoped access operations. The intermediary handles the complexity of resource management transparently, allowing applications to execute diverse functionality while maintaining reliable resource access through automatic isolation enforcement.
2Productivity
If multiple users concurrently access the same native resources, then system utilization is improved, but sociability problems occur when applications assume single-user environment
Solution Approach 1:
The patent segments resource access by creating user-specific isolation scopes that are further divided into application-specific sub-scopes. Each user session receives its own isolated scope containing private resource instances, while applications within those scopes receive additional isolation layers. This multi-level segmentation allows multiple users to concurrently access the system with high productivity while single-user applications maintain compatibility because their resource access patterns remain unchanged within their isolated scopes.
Solution Approach 2:
The patent creates copied instances of native resources for each user and application scope rather than sharing the same resource instances. When a user or application needs access to a resource, the system creates an isolated copy within the appropriate scope. This copying mechanism enables high system utilization through concurrent user access while maintaining compatibility with single-user applications, as each application receives its own private resource copies that behave exactly as if it were the only user accessing them.
3Reliability
If application programs are provided with isolated scopes for resource access, then compatibility between incompatible applications is improved, but system complexity increases due to resource virtualization
Solution Approach 1:
The patent implements segmentation at multiple hierarchical levels (user scope, application scope, resource scope) to manage complexity systematically. Rather than creating a monolithic virtualization system, the patent divides the isolation mechanism into manageable segments that can be independently configured and managed. Each scope level handles specific aspects of resource isolation, making the overall system more tractable while still achieving high application compatibility through the cumulative effect of multiple isolation layers.
4Ease of operation
If virtualized resources are stored in native format, then ease of management using standard tools is improved, but loss of information may occur during virtualization and de-virtualization
Solution Approach 1:
The patent creates precise copied instances of native resources within isolated scopes, maintaining the exact native format and structure of the original resources. These copies are stored in their original native formats (registry keys, file system structures, system objects) rather than being converted to abstract representations. This copying approach enables easy management using standard system tools while preserving data integrity, as the copies are exact replicas that can be manipulated independently without loss of information during virtualization or de-virtualization operations.
Data Source
AI summary
A method for virtualizing access to named system objects includes the step of receiving a request to access a system object from a process executing in the context of a user isolation scope, the request including a virtual name for the system object. A rule associated with the request is determined and a literal name for the system object is formed in response to the determined rule. A request to access the system object is issued to the operating system. The issued request including the literal name for the system object.