Context Services Provider for Module Interaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mashup systems require significant expertise and resources to create and maintain interactions between modules, especially in enterprise environments, where the demand for application development resources exceeds supply and internal wiring must be consistently updated due to changes in source applications.
Innovation Solution
A system that utilizes context-consuming and context-producing logic within functional modules, facilitated by a context services provider, allows modules to interact through context items, enabling efficient creation and operation of composite functionalities by using a publish/subscribe protocol and data serialization services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional wiring approaches are used to create interactions between modules, then module interaction functionality is achieved, but development complexity and resource requirements increase significantly
Solution Approach 1:
The patent introduces a context services provider as an intermediary component that mediates interactions between functional modules. Instead of modules directly wiring to each other, they all interact through the context services provider which manages context items and publishes/subscribes to changes, thereby reducing wiring complexity while maintaining interaction capability
Solution Approach 2:
The context services provider serves as a universal interaction mechanism that handles all types of module communications. It provides standardized context item management, change propagation, and subscription mechanisms that work across different module types, eliminating the need for custom wiring for each interaction scenario
2Adaptability or versatility
If extensive wiring is used to connect modules, then interaction functionality is achieved, but maintenance difficulty increases due to changes in source applications
Solution Approach 1:
The context services provider acts as a stable intermediary layer that isolates modules from direct wiring dependencies. When source applications change, only the context services provider needs to be updated to reflect new context items or relationships, while individual module wiring remains unchanged, significantly easing maintenance
Solution Approach 2:
The system pre-establishes context items and their relationships through the context services provider before modules need to interact. This preliminary configuration allows modules to connect through standardized interfaces without requiring extensive wiring, and future changes can be accommodated by updating the pre-established context model rather than rewiring
3Adaptability or versatility
If manual wiring is performed for each module interaction, then custom functionality is achieved, but development time and resource allocation increase
Solution Approach 1:
The context services provider enables modules to self-configure their interactions by automatically subscribing to relevant context items and receiving change notifications. Modules don't need manual wiring for each interaction; they simply declare their context dependencies and the system automatically establishes connections, dramatically improving development efficiency while maintaining custom functionality
Solution Approach 2:
The context services provider pre-configures the interaction framework by defining context items, their types, and subscription mechanisms before modules are developed. This preliminary setup allows developers to focus only on business logic rather than wiring, increasing productivity while still enabling custom interactions through the standardized context framework
Data Source
AI summary
A computer-implemented system to receive user input at a first functional module, to issue an instruction from the first functional module to change a value of a first context item in response to the user input, to receive the instruction at a context services provider, and to issue, via the context data services provider, a notification of the changed value of the first context item. The notification is received at a second functional module based on an association of the second functional module with the first context item, and first functionality of the second functional module is generated based on the notification of the changed value of the first context item.