Web Server Document Versioning via Mapping Data

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Web servers face challenges in efficiently providing access to multiple versions of documents, as existing systems often require users to manually specify version identifiers or rely on administrators to manage versioning, leading to complexity and potential errors in version retrieval.

Innovation Solution

A web server system that maintains mapping data to identify and serve different versions of documents based on embedded document and version identifiers, allowing users to request specific or the latest versions, and providing a web page with links to all available versions for user selection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the web server stores multiple versions of documents with version identifiers, then users can access specific document versions, but the system complexity increases due to version management requirements

Engineering Contradiction:

Improveversion access capabilityVSAvoidversion management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The web server pre-generates and stores mapping data that associates document identifiers with their respective versions and URL patterns. This preliminary action allows the server to quickly resolve version requests without performing complex analysis at request time, thus reducing operational complexity while maintaining version access capability

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces mapping data as an intermediary layer between the document storage system and the request processing system. This mapping data structure serves as a mediator that simplifies the interaction between users and multiple document versions by providing a standardized access interface, thereby reducing system complexity

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If administrators manually manage document versioning, then version control is maintained, but the administrative burden and potential for errors increase

Engineering Contradiction:

Improveversion control accuracyVSAvoidadministrative burden

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The web server automatically generates and maintains mapping data that tracks document versions and their corresponding URL patterns. This self-service mechanism eliminates the need for administrators to manually manage versioning information, reducing administrative burden while maintaining reliable version control through automated tracking

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements automatic feedback loops where the web server continuously updates mapping data based on document version changes. This automated feedback mechanism ensures version control accuracy without requiring manual intervention, as the system self-corrects and updates its own version tracking information

Inventive Principle:

Principle #23Feedback

3Measurement precision

If users request specific document versions by identifier, then precise version retrieval is achieved, but the ease of use decreases due to the need for users to know version identifiers

Engineering Contradiction:

Improveversion identification accuracyVSAvoiduser accessibility

Core Design Contradiction:

Measurement precisionVSEase of operation

Solution Approach 1:

The web server implements multiple URL patterns that can universally access document versions. Users can access documents through various URL formats including version-specific patterns and generic patterns that automatically resolve to the latest version. This multi-functional URL system maintains precise version identification while improving user accessibility by allowing users to request documents without knowing specific version identifiers

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Instead of requiring users to specify version identifiers in their requests, the system inverts the approach by having the URL pattern itself encode the version selection logic. The server interprets URL patterns and automatically resolves them to the appropriate document versions, thereby maintaining precision while eliminating the need for users to know version identifiers

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS8655943B2Web server providing access to documents having multiple versions

Publication Date: 2014.02.18 ORACLE INT CORP

AI summary

A web server provided according to an aspect of the present invention provides access to different versions of a document. In an embodiment, the web server sends the last version in response to a first request, and a specific requested version in response to a second request (identifying the specific requested version). According to another aspect, the specific requested version is sent when the request includes a corresponding version identifier along with a document identifier, and the last version is sent when the request includes only the document identifier. According to one more aspect, the web server sends a web page indicating all the versions of a document in response to a request for all the versions.