Dynamic Plugin Framework for Web Service Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web service aggregation technologies face challenges in integrating UI code from multiple providers, leading to complex maintenance issues and difficulties with single sign-on (SSO) compatibility, requiring developers to overhaul entire modules or force users to authenticate separately.
Innovation Solution
A technique involving a framework page that dynamically downloads plugins from service providers, allowing for decoupling of the framework page from plugin content, enabling static updates and seamless SSO authentication through a framework token exchange, without requiring extensive developer involvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If UI code from multiple providers is integrated into compacted modules, then the website can aggregate diverse web services, but the modules become difficult to maintain due to many interlocking parts and dependencies
Solution Approach 1:
The system segments the UI code architecture into independent plugins, each provider maintaining their own code separately. The framework page loads plugins dynamically, allowing each plugin to be developed, updated, and maintained independently without affecting others, thus resolving the maintainability issue while preserving aggregation capability.
Solution Approach 2:
The framework page acts as an intermediary that dynamically loads and coordinates multiple provider plugins. This mediator approach allows diverse web services to be aggregated through a standardized interface while keeping each provider's code isolated and maintainable.
2Stability of the object's composition
If the framework page includes all plugin contents, then the page is self-contained, but any change requires complete overhaul of the entire module
Solution Approach 1:
The framework page dynamically loads plugin contents via JavaScript rather than being statically compiled. This allows the page structure to adapt at runtime, enabling individual plugin updates without requiring complete module overhauls, thus reducing update complexity while maintaining structural integrity.
3Reliability
If the aggregating website provides its own authentication methodology, then it can control access, but service providers must rework their authentication schemes to be compatible
Solution Approach 1:
The system implements a universal authentication framework where the aggregating website's authentication methodology serves as a common interface that multiple service providers can adopt. Providers rework their schemes once to be compatible with the framework, after which the same authentication mechanism serves multiple purposes across different providers, easing future integration.
4Adaptability or versatility
If service providers force users to authenticate separately, then they maintain their own authentication schemes, but users must log on to each application separately, losing SSO benefits
Solution Approach 1:
The system merges multiple service provider authentication schemes into a unified Single Sign-On framework. Users authenticate once to the aggregating website, and this authentication is then recognized across all integrated service providers, combining the independence of individual schemes with the convenience of centralized authentication.
Data Source
AI summary
A technique for rendering web content includes downloading a framework page from a framework server, the framework page including framework code which, when executed by a browser of a client machine, dynamically downloads a set of plugins from respective service providers. Each plugin includes its own plugin code configured to communicate with the respective service provider and with the framework code, to dynamically render web content specific to the service provider in the framework page running in the browser.