Web Service Compositional Logic Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As Web service interfaces and choreographies become increasingly complex, existing technologies face challenges in rapidly and reliably developing interoperable services and clients, necessitating a flexible composition mechanism that structures Web service protocols into self-contained micro-protocols and imposes their inherent structure onto the specification and internal design of Web services and their clients.
Innovation Solution
The solution involves separating service logic from compositional logic, using protocol demultiplexers to implement protocol multiplexing and sequencing, allowing for the transmission of composite messages over the network instead of sending messages separately, and enabling modularization of Web service specifications and internal designs through protocol multiplexing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Web service interfaces and choreographies are designed to be highly interoperable using standards like SOAP and WSDL, then cross-platform and cross-language compatibility is improved, but the complexity of composing and managing composite Web services increases
Solution Approach 1:
The patent segments the Web service composition into distinct components: service logic (business operations) and compositional logic (protocol handling). This segmentation allows each component to be developed and tested independently, reducing overall complexity while maintaining interoperability through standardized interfaces.
Solution Approach 2:
The patent introduces protocol demultiplexers as intermediary components that handle protocol-level operations (multiplexing, sequencing, demultiplexing) separately from service logic. These intermediaries manage the complexity of protocol composition while keeping service logic clean and interoperable.
2Productivity
If protocol multiplexing is implemented to transmit composite messages over the network, then message transmission efficiency is improved, but the complexity of protocol demultiplexing and sequencing increases
Solution Approach 1:
The patent extracts protocol handling operations (multiplexing, sequencing, demultiplexing) from the service logic and places them in separate compositional logic components. This extraction simplifies the service logic while managing protocol complexity in dedicated components that can be automatically generated.
Solution Approach 2:
The patent uses automated code generation to create protocol demultiplexer components based on composite message definitions. This copying approach allows complex protocol handling code to be systematically generated from high-level specifications, reducing manual complexity while maintaining efficient message transmission.
3Ease of manufacture
If service logic is separated from compositional logic, then maintainability and testability are improved, but the complexity of implementing and coordinating the separation increases
Solution Approach 1:
The patent implements segmentation by separating service logic (business operations) from compositional logic (protocol handling). This creates distinct, maintainable modules where service logic remains business-focused and compositional logic handles infrastructure concerns, improving maintainability despite the added structural complexity.
Solution Approach 2:
The compositional logic components serve multiple functions: protocol multiplexing, sequencing, demultiplexing, and message routing. This multi-functionality consolidates several responsibilities into unified components, reducing the number of separate implementations needed while maintaining clear separation from service logic.
Data Source
AI summary
Methods and apparatus are disclosed for designing a Web service that processes one or more composite messages. The same techniques may be applied to the design of clients of the Web service. The Web service is comprised of service logic and compositional logic. The service logic is comprised of a plurality of message handlers that process micro-messages of one or more composite messages. The compositional logic is comprised of a plurality of protocol demultiplexers that implement Web service functionality for demultiplexing, sequencing, and multiplexing one or more composite messages. The compositional logic is separated from the service logic, such that the service logic does not include operations for demultiplexing, sequencing, or multiplexing the composite messages.