Shared Library Version Conflict Resolution via Storage Volume Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In computing environments where multiple applications with different versions of shared libraries are attached to a single virtual or physical computing system, ensuring the appropriate version of the shared library is used for each application can be challenging, leading to conflicts and execution issues.

Innovation Solution

A method is implemented to identify requests for shared files, determine the associated application, and retrieve the appropriate version of the file from the designated application storage volume, ensuring each application receives the required version without conflicts, by using a driver or software module that manages requests and maintains metadata to route requests to the correct version.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple application storage volumes with different versions of shared libraries are attached to a computing system, then application versatility and functionality are improved, but conflicts arise in ensuring the appropriate version of shared libraries is used for each application

Engineering Contradiction:

Improveapplication versatilityVSAvoidshared library version compatibility

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the shared library files by organizing them in a directory structure where different versions are stored in separate subdirectories (e.g., version-specific folders). This segmentation allows the system to maintain multiple versions without conflict, as each version resides in its own designated space within the shared library repository.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary component (such as a file system driver or library manager) that sits between the applications and the shared library files. This intermediary intercepts library loading requests, identifies the appropriate version based on application requirements, and retrieves the correct file, thereby mediating between conflicting version demands.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If application storage volumes are attached to provide virtual sessions for multiple users, then user-specific application access is improved, but system complexity increases due to managing multiple versions of shared files

Engineering Contradiction:

Improveuser-specific application accessVSAvoidshared file version management

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a self-service mechanism where the file system automatically manages versioned shared library files without requiring manual intervention. The system includes itself to track which versions are installed on which volumes and automatically serves the correct version to each application, eliminating the need for complex manual version management.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-organizing shared library files into versioned directories and pre-configuring the file system to recognize and manage these versions. This preliminary structuring allows the system to automatically handle versioning requests without complex runtime decision-making, reducing operational complexity.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If different versions of shared libraries are stored on separate application storage volumes, then application independence is improved, but difficulties arise in retrieving the correct version for each application

Engineering Contradiction:

Improveapplication independenceVSAvoidcorrect version identification

Core Design Contradiction:

Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent uses file naming conventions that act as visual identifiers (analogous to color changes), where shared library files include version information in their names or paths. This allows the system and users to easily distinguish between different versions through consistent naming patterns, making correct version identification straightforward.

Inventive Principle:

Principle #32Color changes

Solution Approach 2:

The patent implements a feedback mechanism where the system tracks and records which version of shared libraries is installed on each application storage volume. This feedback information is used to automatically determine the correct version to retrieve when an application requests a shared library, ensuring accurate version matching without manual intervention.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11792278B2Resolving conflicts of application runtime dependencies

Publication Date: 2023.10.17 OMNISSA LLC

AI summary

Described herein are systems, methods, and software to handle requests to an application file shared by a plurality of applications on a computing system. In one implementation, a method of handling request for an application file shared by a plurality of applications on a computing system includes identifying a request for the application file on the computing system, wherein each application in the plurality of applications is associated with an individualized version of the application file, and wherein the plurality of applications is stored on separate application storage volumes attached to the computing system. The method further provides identifying an application associated with the request, and identifying an application storage volume in the application storage volumes that stores the application. Once identified, the method also includes retrieving the application file from the identified storage volume to support the request.