Asynchronous Postback Coordination for Web Page Regions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for providing Web pages to clients result in substantial delays due to the need for all components to be ready before any are provided, which can negatively impact user experience by not informing users of the server's status until the entire page is loaded.

Innovation Solution

Implementing asynchronous postbacks that allow regions of a Web page to be updated separately, enabling the server to provide updates and requestors for regions that need updating, reducing the need for a full page reload and improving user interaction by updating only changed regions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server waits for all components to be ready before providing any information to the client, then the completeness of the Web page is ensured, but the user experience deteriorates due to substantial delays and lack of status information

Engineering Contradiction:
Improvecompleteness of Web pageVSAvoidwait time for Web page
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the Web page into multiple independent regions, each with its own requestor that can be updated asynchronously. This allows the server to provide updates for individual regions as they become ready, rather than waiting for all components to be complete, thereby reducing overall wait time while maintaining page reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The server performs preliminary actions by preparing and providing updates for regions that are ready before the entire Web page is complete. The framework and indicator are provided in advance to inform users of the server's status, allowing partial content to be displayed while remaining components are being prepared.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If the server provides an indicator specifying that the Web page will be provided when all components are ready, then user satisfaction improves due to status information, but the wait time remains substantial

Engineering Contradiction:
Improveuser satisfactionVSAvoidwait time for Web page
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent divides the Web page into multiple regions with individual requestors, allowing the server to update regions asynchronously as they become ready. This segmentation enables the server to provide status information more frequently through regional updates rather than waiting for complete page readiness, reducing perceived wait time while maintaining user satisfaction.

Inventive Principle:
Principle #1Segmentation

3Productivity

If the server provides updates for all regions simultaneously, then the Web page is complete faster, but the complexity of coordinating multiple asynchronous postbacks increases

Engineering Contradiction:
ImproveWeb page provisioning speedVSAvoidcoordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a feedback mechanism where each region has an associated requestor that tracks its update status. When a region receives an update, the requestor is removed from further consideration, providing automatic feedback that prevents redundant updates and simplifies coordination of multiple asynchronous postbacks.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8631095B2Coordinating multiple asynchronous postbacks
Publication Date: 2014.01.14 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8631095B2 patent drawing
  • US8631095B2 patent drawing
  • US8631095B2 patent drawing

AI summary

Techniques are described herein for coordinating multiple asynchronous postbacks. Each postback specifies a requestor that initiates the postback. A requestor is a request to update a corresponding region of a Web page. Each time a server receives a postback from a client, the server provides a response to the client that includes an update regarding a region of the Web page that corresponds to a requestor that initiates the postback. The response further includes a requestor for each region of the Web page that is to be updated once the response is processed by the client. Upon receipt of each response from the server, the client provides a postback to the server. The client and server may continue to communicate in this manner until all regions of the Web page that are to be updated have been updated.