Co-Browsing StyleID Caching for Adopted Stylesheets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The transmission of adopted stylesheets during co-browsing sessions consumes significant resources due to the large amount of data transfer, particularly when dealing with shadow DOM regions, leading to performance issues for both the visitor and agent.
Innovation Solution
A method where the visitor transmits a StyleID instead of the actual CSS of adopted stylesheets, which is then cached and reused across sessions by a Universal Co-browse Asset Management (UCAM) system, allowing agents to retrieve stylesheets from local or server caches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the visitor transmits the actual CSS of adopted stylesheets during co-browsing, then the agent can accurately reproduce the webpage content, but the bandwidth consumption and transmission time increase significantly
Solution Approach 1:
The patent extracts only the essential identifying information (StyleID) from the full CSS stylesheet and transmits it to the agent. The StyleID serves as a reference key that allows the agent to retrieve or reconstruct the complete stylesheet without receiving the entire CSS content over the network, thereby reducing bandwidth consumption while maintaining reproduction accuracy.
Solution Approach 2:
The system performs preliminary processing by generating StyleIDs from the CSS content before transmission. The UCAM service pre-processes and caches stylesheets locally, so when the agent receives a StyleID, it can quickly retrieve or reconstruct the corresponding CSS without waiting for full stylesheet transmission, reducing latency and improving response time.
2Reliability
If the visitor transmits the actual CSS of adopted stylesheets, then the agent can apply the correct styling, but the transmission latency increases
Solution Approach 1:
The agent creates a local copy or reference to the CSS stylesheet through the StyleID mechanism. Instead of transmitting the full CSS each time, the system uses the StyleID as a pointer that allows the agent to access the stylesheet content from local cache or reconstruct it on-demand, significantly reducing transmission latency while ensuring the correct styling is applied.
Solution Approach 2:
The UCAM service performs preliminary caching of stylesheets locally. When the agent needs a stylesheet, it can retrieve it from the local cache using the StyleID without waiting for network transmission, thereby reducing latency. The system also pre-processes the CSS to generate StyleIDs that can be quickly resolved to the actual stylesheet content.
3Loss of energy
If the system caches and reuses stylesheets across sessions, then bandwidth is saved, but the system complexity increases
Solution Approach 1:
The UCAM (Universal Co-browse Asset Management) service acts as an intermediary between the visitor and agent. It manages the caching, storage, and retrieval of stylesheets locally, handling the complexity of cross-session reuse. The visitor and agent only interact through simple StyleID references, while the UCAM service manages the sophisticated caching logic, thereby isolating system complexity to a dedicated component.
Solution Approach 2:
The system transforms the stylesheet representation from full CSS content to compact StyleID references. This parameter change enables efficient caching and comparison - instead of storing and comparing large CSS texts, the system stores and compares small StyleID strings, reducing memory usage and simplifying the caching mechanism while enabling cross-session reuse.
Data Source
AI summary
Co-browsing webpages containing regions with adopted stylesheets is enabled between a visitor and agent, while minimizing transmission of CSS associated with adopted stylesheets on the co-browsing session. When the visitor encounters an adopted stylesheet, the visitor creates a StyleID from the CSS of the adopted stylesheet, and transmits the StyleID on the co-browse session instead of the CSS. When the agent receives the StyleID, the agent determines if it has a locally stored copy of the CSS corresponding to the StyleID. In instances where the agent has the locally stored copy, the agent applies the corresponding CSS to the region. In instances where the agent doesn't have a locally stored copy, the agent requests a copy of the CSS from a UCAM facilitating the co-browse session. The UCAM stores CSS corresponding to StyleIDs for use between multiple co-browse sessions and requests unknown StyleID CSS from the visitor.