Client-Side Content Transformation Offloading Gateway Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional technologies for accessing content outside an intranet are limited by the gateway's burden of transforming content, which consumes significant computer processing and memory resources, making them less scalable as content complexity increases.
Innovation Solution
A content accessing process that offloads transformation tasks from the gateway to client browsers, where transformation functions are installed and invoked to convert content into a form accessible to the client, reducing the gateway's workload and improving scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the gateway transforms content for viewing outside the intranet, then content accessibility is improved, but the gateway's processing load increases
Solution Approach 1:
The patent extracts the content transformation function from the gateway and relocates it to the client browser. The gateway no longer performs transformation but instead provides transformation functions to clients, which then execute the transformation locally. This extraction resolves the contradiction by removing the processing burden from the gateway while maintaining content accessibility.
Solution Approach 2:
The client browser performs self-service by executing transformation functions locally to transform content for its own display. Instead of relying on the gateway to transform content, the client uses provided transformation functions to independently transform content as needed, thereby reducing gateway processing load while maintaining accessibility.
2Adaptability or versatility
If the gateway performs content analysis, parsing, and manipulation, then content transformation is improved, but device scalability deteriorates
Solution Approach 1:
The patent extracts content transformation capabilities from the gateway and transfers them to client browsers through transformation functions. This extraction eliminates the scaling bottleneck at the gateway level, as each client can independently handle transformations without consuming gateway resources, thereby improving scalability while maintaining transformation versatility.
Solution Approach 2:
The patent introduces transformation functions as intermediary components that mediate between the gateway and client browsers. These functions are provided by the gateway but executed by clients, serving as a bridge that enables content transformation without requiring the gateway to directly process all content, thus improving both transformation capability and scalability.
Data Source
AI summary
In a client, a system receives a set of transformation functions for use in transforming a first content, requests the first content from a gateway, and receives the first content from the gateway, including an invocation of at least one transformation function maintained on the client. The system invokes the at least one transformation function to transform the first content to access a second content on the server.In a gateway communicating with a server, a system transmits a set of transformation functions to at least one client for use in transforming a first content, receives a request from at least one client for the first content residing on the server, rewrites the first content to include the invocation of at least one transformation function maintained on the client, and transmits the first content including the invocation of at the least one transformation function maintained on the client.