Web Services Layer Synchrony Translation Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web services layers struggle to integrate applications with different types of synchrony, such as synchronous and asynchronous, and cannot provide multiple interfaces with varying synchrony types, limiting compatibility and efficiency in data processing and retrieval.
Innovation Solution
A web services system that translates client requests between interfaces with different types of synchrony by using a translation layer to match web services requests with corresponding application functions, employing a naming convention to identify namespaces and handle tokens efficiently, allowing for synchronous and asynchronous interfaces to be created or modified for either type of underlying application programming interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a web services layer mirrors the underlying application API, then compatibility with the application is maintained, but the ability to change synchrony type and integrate applications with different synchrony types is lost
Solution Approach 1:
The patent introduces a translation layer as an intermediary between the web services interface and the underlying application API. This translation layer receives requests in one synchrony type, translates them to the appropriate synchrony type for the application, and returns responses in the required format. This mediator enables the web services layer to provide synchronous or asynchronous interfaces regardless of the application's native synchrony type, resolving the contradiction between maintaining compatibility and providing flexibility.
Solution Approach 2:
The patent changes the synchrony parameter of the web services interface independently from the application's synchrony parameter. By allowing the web services layer to accept and return different synchrony types (synchronous or asynchronous) while the application maintains its native synchrony type, the system achieves both compatibility with the application and flexibility in the web services interface. This parameter decoupling resolves the contradiction.
2Productivity
If a web services layer integrates with synchronous applications, then simple data processing is achieved, but integration with asynchronous applications and multiple synchrony types is limited
Solution Approach 1:
The patent makes the web services layer universal by enabling it to work with both synchronous and asynchronous applications through the translation layer. The translation layer can handle requests for synchronous applications (maintaining simple data processing) and asynchronous applications (enabling integration with multiple synchrony types). This multi-functionality resolves the contradiction between processing efficiency and adaptability.
3Adaptability or versatility
If multiple interfaces with different synchrony types are provided, then flexibility and compatibility are improved, but system complexity increases
Solution Approach 1:
The patent segments the web services layer into distinct components: the web services interface layer and the translation layer. This segmentation allows each layer to have a specific responsibility - the interface layer handles client requests with appropriate synchrony types, while the translation layer handles the complexity of converting between different synchrony types and application-specific formats. This segmentation reduces overall system complexity while maintaining interface flexibility.
4Speed
If synchronous processing is used, then immediate data retrieval is achieved, but client blocking and wait states occur
Solution Approach 1:
The patent introduces dynamic synchrony selection, allowing the web services interface to adapt its processing mode based on client requirements and application capabilities. Clients can choose synchronous processing for immediate retrieval or asynchronous processing for non-blocking operations. The translation layer dynamically translates between these modes and the application's native synchrony type, resolving the contradiction between retrieval speed and operational continuity.
Data Source
AI summary
A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.