Web Services Runtime Framework Stateless Protocol Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Web services message processing runtime frameworks face inefficiencies due to the use of state-full protocols, which limit scalability and do not effectively support features like WS-Reliable Messaging, and require a mapping registry that introduces performance delays.
Innovation Solution
The improved runtime framework eliminates the mapping registry, redesigns protocols to be state-less, and incorporates a built-in endpoint manager and implementation container, enabling direct protocol-to-runtime object communication and supporting hibernation for efficient message processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If state-full protocols are used in the runtime framework, then protocol functionality can be maintained, but scalability is limited and performance delays occur
Solution Approach 1:
The patent extracts and eliminates the mapping registry component from the runtime framework, removing the source of performance delays. It also removes stateful protocol instances, replacing them with stateless protocol handlers that process messages independently without maintaining internal state, thereby improving scalability and reducing complexity.
Solution Approach 2:
The patent implements a universal protocol handler architecture where a single protocol handler class can process multiple message types through polymorphic interfaces. The runtime framework uses a unified message processing mechanism that handles both incoming and outgoing messages, as well as both stateless and stateful protocol requirements, reducing overall system complexity.
2Reliability
If a mapping registry is used to manage protocol-to-endpoint mappings, then protocol functionality is maintained, but performance delays are introduced
Solution Approach 1:
The patent removes the mapping registry component entirely from the runtime framework. Instead of using a centralized registry that requires lookup operations, the system uses direct protocol-to-endpoint mappings configured at deployment time, eliminating the performance delay associated with runtime mapping lookups while maintaining reliable protocol functionality.
Solution Approach 2:
The patent performs protocol-to-endpoint mappings in advance during the deployment and configuration phase, rather than at runtime. Endpoint references are pre-resolved and bound to protocol handlers before message processing begins, so that during actual message processing, no time-consuming mapping lookups are required, thus eliminating performance delays.
3Reliability
If state-full protocols are used, then protocol state can be maintained, but multiple protocol instances are required for multiple message pairs
Solution Approach 1:
The patent extracts and removes the stateful protocol instance creation mechanism from the runtime framework. Instead of creating new protocol instances for each message pair, the system uses a single shared protocol handler that processes messages statelessly, significantly improving productivity and reducing resource consumption while maintaining protocol functionality through the message context.
Solution Approach 2:
The patent uses message context objects to copy and preserve protocol state information across different message processing operations. Instead of creating new protocol instances, the system serializes protocol state into message contexts that can be shared and restored, allowing a single protocol handler to serve multiple message pairs efficiently.
4Reliability
If the runtime framework processes all messages sequentially, then processing completeness is ensured, but processing time increases
Solution Approach 1:
The patent implements a dynamic message processing model where the runtime framework can process messages in parallel based on their type and priority. Critical messages requiring stateful processing are handled sequentially to ensure completeness, while stateless messages are processed concurrently using thread pools and asynchronous processing, thereby reducing overall processing time while maintaining reliability.
Data Source
AI summary
A method and system for processing Web service messages within an object oriented runtime environment is described. In one embodiment, the method includes steps for invoking a single instance of a state-less protocol for processing inbound and outbound flows of Web services messages. After determining Web services messages have been received out of order, processing of the outbound flow of any remaining messages is suspended until a complete set of messages is received. The messages are rearranged into proper order before completing processing of the outbound flows of the remaining messages.