File Type Association via Isolation Scopes and Chooser Tools

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Incompatible software application programs often conflict when accessing shared native resources, leading to installation and execution issues on single-user and multi-user computers, resulting in compatibility and sociability problems.

Innovation Solution

The solution involves virtualizing user and application access to native resources like the file system, registry database, and system objects, allowing multiple applications to coexist without modification, using isolation scopes to provide unique views of resources and manage conflicts, enabling the association of file types with chooser tools for seamless execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple incompatible applications are installed on a single computer, then application compatibility is improved, but resource conflicts and system stability deteriorate

Engineering Contradiction:
Improveapplication compatibilityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the shared native resources into application-specific isolated views. Each application receives a dedicated scope of resources that prevents conflicts with other applications. The file system, registry database, and system objects are divided into separate namespaces for each application, allowing incompatible applications to coexist without interfering with each other's resource access.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (isolation environment) between applications and native resources. This intermediary manages resource allocation and access control, translating application requests into isolated resource operations. The chooser tool acts as an intermediary for file type associations, routing file operations to the appropriate application without direct conflicts.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If file type associations are restricted to single applications, then resource access control is simplified, but application versatility and user choice deteriorate

Engineering Contradiction:
Improveresource access controlVSAvoidapplication versatility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent makes the file type association mechanism universal by allowing multiple applications to be associated with the same file type. Instead of a one-to-one mapping, the system supports many-to-many associations where a file type can be linked to multiple applications, and applications can handle multiple file types. The chooser tool provides a unified interface for managing these associations across all applications.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces dynamic selection in file type associations through the chooser tool. When a file is opened, the system dynamically presents available applications to the user, allowing runtime selection based on current needs. This dynamic approach replaces static single-application associations with flexible multi-application support, enabling users to choose the most appropriate application for each specific file operation.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7752600B2Method and apparatus for providing file-type associations to multiple applications
Publication Date: 2010.07.06 CITRIX SYSTEMS INC
  • US7752600B2 patent drawing
  • US7752600B2 patent drawing
  • US7752600B2 patent drawing

AI summary

A method for associating a file type of a file with one or more programs includes the step of receiving a request to store in a configuration store file type association information. From the request, an application program is determined that is to be associated with a file type in the configuration store. An association of the file type with a chooser tool is written to the configuration store