Client-Side UI Customization via Local Action Scripts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud storage systems require significant server resources to maintain and apply user customization, leading to increased network usage, memory usage, and processing time, as well as reduced server response times due to the need for frequent client-server communication for UI component changes.
Innovation Solution
A method where a client browser requests and runs a .swf file that identifies and loads user preferences as action scripts, enabling client-side customization of UI components, such as adding, renaming, or sorting views and columns, and managing filter panels, with the ability to check for updates and save preferences in XML format, reducing server load and improving response times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If servers maintain user customization information and process preferences at server end, then user preferences can be preserved and applied, but network resource usage increases and server response time decreases
Solution Approach 1:
The patent extracts the user preference processing functionality from the server and relocates it to the client machine. The customization information is saved locally in the browser's shared object file rather than being maintained on the server, thereby eliminating the need for continuous server-client communication for preference management while preserving reliability.
Solution Approach 2:
The client machine is empowered to independently manage, store, and apply user preferences without requiring server intervention. The browser's shared object file serves itself as the storage medium, and the client application automatically applies these preferences when rendering web pages, making the system self-sufficient for customization tasks.
2Reliability
If servers maintain user customization information, then user preferences can be applied, but server processing time increases
Solution Approach 1:
User preferences are pre-loaded and stored in the browser's shared object file before the web page rendering process begins. When the client application executes, it immediately accesses these pre-stored preferences without requiring server processing, thereby eliminating server processing time delays while ensuring reliable preference application.
Solution Approach 2:
The client application independently retrieves and applies user preferences from the locally stored shared object file without requiring server-side processing. This self-service mechanism eliminates the time-consuming server processing step while maintaining the reliability of preference application through local storage and automatic retrieval.
3Adaptability or versatility
If client customizes UI components and changes are sent to server, then user interface can be customized, but device complexity increases
Solution Approach 1:
The patent extracts the UI customization logic from the complex server-client communication framework and embeds it directly in the client application. The shared object file stores customization parameters locally, and the client application directly applies these parameters to UI components without requiring server mediation, thereby reducing system complexity while maintaining full UI customization capability.
Solution Approach 2:
The browser's shared object file serves as an intermediary storage mechanism between user actions and UI rendering. Instead of complex direct communication between client and server for each customization change, the shared object file acts as a local mediator that stores and manages customization data, simplifying the overall system architecture while preserving adaptability.
Data Source
AI summary
Methods and apparatus to provide client application customization including requesting and receiving, by a client browser on a client machine, a first file from a server, running the first file as a client application, which looks to identify user preferences on the client machine, reading, parsing and loading into memory, by a computer processor on the client application, the identified user preferences as action scripts, and rendering the application using the action scripts. This arrangement saves server resources by customization being performed locally.