Server-Side Dynamic Page Execution with Intermediate Client Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional single-pass execution of server-side dynamic pages is cumbersome for voice applications, as it requires users to re-enter information if any field is invalid, leading to user frustration due to the inability to provide immediate feedback during the temporal input process.

Innovation Solution

A method and system for executing dynamic pages that allow intermediate requests for additional information from the client, enabling the dynamic page to enter a wait state until the necessary information is received, allowing seamless continuation of execution without requiring re-entry of data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional single-pass execution is used for server-side dynamic pages, then the server can process requests independently and maintain simple request-response cycles, but voice applications require users to re-enter information if any field is invalid, leading to user frustration

Engineering Contradiction:
Improveuser experience in voice applicationsVSAvoidrequest-response cycle complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies dynamics by enabling the server to transition between different execution states (wait state vs. completion state) during the request-response cycle. The server can pause execution, wait for additional client input, then resume execution within the same cycle, making the system adaptable to voice application needs without requiring complete re-entry of information

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements continuity of useful action by allowing the server to maintain an active execution context across multiple interactions. Instead of terminating and restarting execution for each validation failure, the server continues the same execution thread, preserving user input and application state, thereby providing seamless validation and correction within a single request-response cycle

Inventive Principle:
Principle #20Continuity of useful action

2Reliability

If the server waits for additional information from the client during dynamic page execution, then immediate validation feedback can be provided to the user, but the traditional request-response cycle must be extended to accommodate multiple interactions

Engineering Contradiction:
Improveinput validation accuracyVSAvoidrequest-response cycle duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by having the server prepare and send validation requests to the client before final processing. The server can request additional information or validation data in advance during the execution flow, allowing the client to provide feedback before the entire transaction completes, thereby improving validation accuracy without significant time penalty

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms by enabling the server to request and receive additional information from the client during execution. The server can validate input fields, check information accuracy, and provide immediate feedback to the user within the same request-response cycle, improving reliability without requiring complete re-entry of data

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8010595B2Execution of server-side dynamic pages
Publication Date: 2011.08.30 HULU LLC
  • US8010595B2 patent drawing
  • US8010595B2 patent drawing
  • US8010595B2 patent drawing

AI summary

A system (30) and method are provided for single-pass execution of dynamic pages across multiple request-response cycles. The system (30) comprises a client (32) and server (34) in communication with one another. A container (35) resides on the server and handles requests made for the result of a dynamic page (36). The container controls the processing of the dynamic page. If the dynamic page requires additional information to continue processing, an intermediate request (44) is transmitted to the client, which responds with an intermediate response (46) containing the additional information. A notifier servlet (38) receives the intermediate response and passes the information to the dynamic page so that execution can resume without interruption.