Website Access Method Using URL Version Parameters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing website upgrading processes often require manual updates of file paths and names, leading to extensive file upgrades and increased risks, as well as higher development costs and risks of affecting dependent files.
Innovation Solution
A website access method that generates a current URL for content files by adding a version parameter to the search part of the URL, allowing clients to retrieve the latest content files without changing file paths or names, thereby reducing the need for full upgrades and minimizing risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If file content hash mechanism is used to ensure dynamic updating of web pages, then file updates can be tracked, but all dependent files must be updated accordingly, resulting in massive file updates and increased upgrading risks
Solution Approach 1:
The patent segments the file identification mechanism by separating the file path (which remains constant) from the version identification (achieved through query parameters). This allows individual file updates without requiring updates to all dependent files, as the version is identified through URL parameters rather than filename changes that would trigger cascading updates.
Solution Approach 2:
The patent introduces a version parameter as an intermediary element between the file content and its identification. Instead of directly embedding version information in filenames (which triggers dependent file updates), the version parameter is added to the URL query string, acting as a mediator that identifies file versions without affecting the file's reference structure in dependent files.
2Loss of time
If filename is changed to include hashcode to track file updates, then latest file can be obtained, but file path and name must be manually updated, increasing development costs and time
Solution Approach 1:
The patent makes the URL dynamic by adding version parameters to the query string instead of statically changing filenames. This allows the same file path to serve multiple versions, with the version identified through dynamic URL parameters. This eliminates manual filename updates while maintaining the ability to track and serve specific versions.
Solution Approach 2:
The patent changes the identification parameter from filename to URL query parameter. By moving version information from the filename (static identifier) to the URL query parameter (dynamic identifier), the system allows version tracking without requiring changes to file paths or names, significantly reducing manual update efforts.
3Productivity
If one file is updated with filename change, then that file can be updated, but all files referencing it must also be updated, increasing upgrading risks
Solution Approach 1:
The patent segments the file reference mechanism by separating the stable file path from the version identifier. This allows independent updating of individual files without requiring coordinated updates across the entire file dependency graph, as version identification is decoupled from the filename structure that dependent files reference.
Solution Approach 2:
The patent establishes a version parameter mechanism in advance that allows files to be updated independently. By pre-defining the URL structure to include version parameters, the system enables straightforward single-file updates without requiring preliminary updates to all dependent files, reducing upgrading risks.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
This application relates to the field of IT technologies, and in particular, to a website access method, an apparatus, and a website system. In the website system, when a client accesses a page of a website, a web server obtains an initial URL of a content file included in the to-be-accessed page and a version parameter of a current version of the website, generates a current URL of the content file, and adds the version parameter to a search part of the current URL of the content file, so that the client can obtain the content file from the web server according to the current URL. During version upgrade of the website, a developer does not need to change a path to a content file, does not need to manually change a URL of the content file, and does not need to update a name of the content file either. This improves website upgrading efficiency.