Extensible Servlet Framework for URI Pattern Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current gateway servlet technologies in multi-tier client/server systems are not extensible, leading to constraints in processing URI requests and handling lifecycle events, which affects application performance and requires additional container design requirements.
Innovation Solution
An extensible URI-pattern-based servlet request-processing framework that includes an extension processor component and an improved web container, allowing for specific URI pattern handling and reducing the execution path of requests through an extension processor factory that instantiates processors for matching URI patterns.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If gateway servlet technologies are used in multi-tier client/server systems, then URI request processing capability is provided, but the system lacks extensibility and requires additional container design requirements
Solution Approach 1:
The gateway functionality is segmented into independent extension processor components that can be individually added or removed. Each extension processor handles specific URI patterns, allowing the system to be extended without redesigning the entire container architecture.
Solution Approach 2:
The extension processor interface provides universal functionality for handling different URI patterns through a standardized mechanism. This allows diverse gateway operations to be performed through a common extensible framework, reducing the need for specialized container design for each use case.
2Productivity
If traditional servlet processing is used, then request handling is provided, but the execution path is lengthy and performance is reduced
Solution Approach 1:
URI patterns are pre-compiled and registered in advance, allowing the container to perform direct pattern matching against incoming requests without undergoing the traditional lengthy servlet loading and initialization process. This preliminary preparation significantly reduces execution time.
Solution Approach 2:
The extension processor extracts and handles specific URI patterns directly at the container level, bypassing the traditional servlet processing chain for matched patterns. This extraction of specific functionality from the general servlet processing path reduces the overall execution path length.
Data Source
AI summary
Extensible URI-pattern-based servlet request processing frameworks process and respond to requests for resources sent over a network by client programs to application programs in multi-tiered data processing systems. An extension processor component, an improved web container; and an improved web application architecture form the framework. The extension processor component includes one or more extension processor factories, each of which generates a single type of extension processor to handle specific application components. Each extension processor is adapted to respond to a request having a declared pattern. The extension processor factory resides within the web container and provides a list of patterns for which it is responsible. The extension factory also instantiates an extension processor to respond to a request having a pattern that matches that extension processor's declared pattern. The improved web application includes a request mapper adapted to route a request having a particular pattern to the appropriate extension processor.