Client-Side Dynamic Secondary Content Delivery via Asynchronous Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for delivering secondary content, such as advertising, are tied to top-level page transitions and fail to keep updates in sync with dynamically changing primary content, rendering them ineffective in providing timely and topical content to consumers.
Innovation Solution
A client-side initiated delivery system using a dynamic secondary content delivery application, running as a script on the host page, requests and renders updates independently of top-level page transitions, utilizing asynchronous techniques like AJAX to ensure timely and non-disruptive updates of secondary content.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional methods tie secondary content updates to top-level page transitions, then page load consistency is maintained, but secondary content becomes outdated when primary content updates dynamically without page reloads
Solution Approach 1:
The system pre-establishes an asynchronous communication channel (XMLHttpRequest) between the client and server during initial page load. This preliminary setup enables the client to proactively request secondary content updates without waiting for page transitions, ensuring timely content delivery while maintaining simple synchronization logic.
Solution Approach 2:
The server responds to client requests with feedback containing updated secondary content or metadata. This feedback mechanism allows the system to dynamically synchronize secondary content with primary content changes without requiring full page reloads, resolving the contradiction between timeliness and complexity.
2Reliability
If top-level page reloads are used to update secondary content, then content consistency is ensured, but user experience is disrupted and loading time increases
Solution Approach 1:
The system segments the content update process by separating secondary content updates from primary content loading. Instead of reloading the entire page, only the specific secondary content elements (e.g., advertisements, ancillary information) are updated through targeted asynchronous requests, maintaining consistency while minimizing time loss.
Solution Approach 2:
The asynchronous XMLHttpRequest mechanism enables continuous updating of secondary content without interrupting the user's interaction with the primary content. The useful action of content delivery continues seamlessly in the background, eliminating the disruptive page reloads and associated time losses.
3Speed
If secondary content is delivered concurrently with primary content during top-level page load, then initial content availability is improved, but updates to secondary content lag behind dynamic primary content changes
Solution Approach 1:
The system transitions from a static, one-time content delivery model to a dynamic, ongoing update model. The asynchronous XMLHttpRequest establishes a continuous communication channel that adapts to changing primary content, ensuring secondary content remains relevant and synchronized with current primary content state.
Solution Approach 2:
The system pre-configures the asynchronous request mechanism during initial page load, enabling rapid subsequent updates. This preliminary setup maintains fast initial content delivery while establishing the infrastructure for continuous synchronization, preventing relevance lag.
Data Source
AI summary
There is provided a method of enabling client-side initiated delivery of dynamic secondary content to a host page comprising running a dynamic secondary content delivery application, requesting a secondary content update to one or more items of existing secondary content rendered on the host page during page load, downloading the secondary content update to the client system, parsing the secondary content update by the dynamic secondary content delivery application, and rendering the secondary content update on the host page, resulting in the client-side initiated delivery of the dynamic secondary content to the host page. In one embodiment, the method is executed by a client system in response to instructions comprising the dynamic secondary content delivery application stored on a computer-readable medium.