Caching Post-Query Web Form Responses via Signature Pseudo-Get Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional cache units cannot efficiently cache post-query web forms due to their URL structure, leading to increased network bandwidth usage and web server/database processing, as they cannot be easily converted to standard get-query forms due to HTTP URL length limitations.

Innovation Solution

A method that algorithmically treats post-query requests to create a signature, composing a pseudo-get web identifier, and sending the query through a network to a responding station to request results, allowing for caching and reducing duplicate requests by resubmitting queries in a cacheable format.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If post-query web forms are used to submit queries with parameters in the request body, then query functionality is maintained, but cacheability is lost and network bandwidth usage increases

Engineering Contradiction:
Improvequery functionalityVSAvoidnetwork bandwidth usage
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent introduces a signature as an intermediary element that bridges post-query functionality and cacheability. The signature is computed from the query parameters and appended to the URL, allowing cache units to identify and store responses without requiring the original post-query format. This intermediary mechanism enables both full query functionality and efficient caching.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms the query parameters from being exclusively in the request body to being represented in the URL through signature computation. By changing the parameter representation from raw form data to a hashed signature in the URL, the system enables cacheability while preserving the ability to retrieve and process the original query parameters when needed.

Inventive Principle:
Principle #35Parameter changes

2Loss of information

If post-query requests are sent with full parameters in the request body, then complete query information is transmitted, but web server and database processing activity increases

Engineering Contradiction:
Improvequery information completenessVSAvoidweb server processing efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent creates a simplified copy of the query information in the URL through the signature, which contains enough information for cache identification without requiring the full parameter set to be processed by the web server. The signature acts as a compact representation that preserves query identity while reducing processing overhead.

Inventive Principle:
Principle #26Copying

3Device complexity

If conventional cache units are used without modification, then cache structure simplicity is maintained, but post-query responses cannot be cached

Engineering Contradiction:
Improvecache structureVSAvoidcacheability of post-query responses
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments the query identification into two parts: the URL with signature for cache key generation, and the original request body for full parameter retrieval when needed. This segmentation allows conventional cache units to function with simple URL-based keys while maintaining the ability to handle post-query responses through the signature component.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8719216B2Caching of web form post-query requests
Publication Date: 2014.05.06 THE BOEING CO
  • US8719216B2 patent drawing
  • US8719216B2 patent drawing
  • US8719216B2 patent drawing

AI summary

A method for obtaining a result for a post-query may include: (a) Algorithmically treating the query to create a signature. (b) Composing a pseudo-get web identifier including a web address identifying a responding station and the signature. (c) Sending the query via a network to the responding station to request the result. (d) Determining whether the result is stored in a cache unit in the network. (e) If the result is stored in a cache unit, providing the result to the requesting station. (f) If the result is not stored in a cache unit, acquiring the result from the responding station. (g) Storing the result in a receiving cache unit. (h) Sending a resubmitted query via the network to the responding station in a format appropriate to retrieve the stored result from the receiving cache unit. The resubmitted query format includes the signature phrase.