Configurable File Placement for Web Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Web development tools, such as early versions of MACROMEDIA INC.'s CONTRIBUTE™, do not adequately address the efficient placement of files on a Web server, particularly for style sheet files like CSS, leading to duplication and requiring manual intervention when the server's file structure deviates from standard configurations.
Innovation Solution
A system and method that allows users to set customizable placement rules based on file extensions or types, automatically directing files to appropriate locations on the Web server during publication, eliminating the need for users to know the exact file structure and enabling administrators to design custom file placement policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If files are placed in standardized locations on the Web server, then Web pages can be accessed efficiently by browsers, but Web developers cannot place files in custom locations and must follow rigid file structures
Solution Approach 1:
The system dynamically determines file placement locations based on the type of file being published. Different file types (HTML, images, CSS, JavaScript) are automatically directed to appropriate locations on the Web server, allowing the system to adapt to various server structures while maintaining efficient file organization. This dynamic approach resolves the contradiction by making the file placement system flexible rather than rigid.
Solution Approach 2:
The publishing system acts as an intermediary between the Web developer and the Web server file structure. Instead of requiring developers to directly manage file locations, the system mediates the placement process by automatically determining where each file should be placed based on its type and the server's structure, thus providing both ease of operation and adaptability.
2Reliability
If style sheet files are placed alongside each HTML file, then each page can access its styles independently, but style sheet files are duplicated across multiple locations increasing storage usage
Solution Approach 1:
The system provides universal file placement capabilities that work for all file types including style sheets. By recognizing CSS files as a distinct category, the system can place them in centralized locations that are accessible to multiple HTML files, thus maintaining style sheet accessibility while avoiding duplication across every page.
Solution Approach 2:
The system merges the placement of style sheet files into shared locations rather than duplicating them alongside each HTML file. This consolidation reduces the total quantity of style sheet copies stored on the server while maintaining reliable access for all pages that need them.
3Manufacturing precision
If manual file placement is required on the Web server, then precise file locations can be controlled, but the publishing process becomes complex and requires professional knowledge
Solution Approach 1:
The publishing system performs self-service by automatically determining and executing file placement decisions based on file types. The system independently manages the complexity of file location management, allowing users to publish without needing professional knowledge of server file structures, thus maintaining precision while reducing operational complexity.
Solution Approach 2:
The system performs preliminary actions by pre-configuring placement rules for different file types before the actual publishing process. This preliminary setup of file placement logic allows the system to automatically direct files to precise locations during publishing without requiring users to manually configure complex file structure details.
Data Source
AI summary
In publishing to a Web server, a set of placement rules are entered by a user. These placement rules set a location on the Web server for storing the various files supporting a request to publish to the Web server. Type identifiers, such as file extensions, Multipurpose Internet Mail Extensions (MIME) types, and the like, are used in the rules to assign certain types of files to the desired locations. When a developer or designer requests to publish to the Web server, all of the files supporting this publication request are read to determine their file type identifiers. Using the type identifiers, a location is assigned to each of the files that corresponds to the location assigned in the placement rules.