Unified Action Handler for Cross-Platform App Interaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of applications built on different user interface (UI) technologies is inefficient due to the need for multiple tools and ad-hoc deployment, leading to a disorganized system that complicates navigation and interaction between applications.
Innovation Solution
The implementation of action handlers organized in a hierarchical structure allows for the registration and dispatching of access requests between applications, enabling interoperability and navigation across different UI technologies by associating each application with at least one action handler and using target identifiers to launch the target application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple integration tools are employed for different UI technologies, then application interoperability is achieved, but system complexity and difficulty of maintenance increase
Solution Approach 1:
The patent implements a universal integration layer that provides a common interface and standardized protocols for interacting with applications built on different UI technologies (HTML, Flex, Java applets, etc.). This single unified integration mechanism replaces the need for multiple technology-specific integration tools, allowing one integration layer to handle diverse application types through standardized communication patterns and a common event model.
2Adaptability or versatility
If ad-hoc deployment is used for integrating applications, then flexibility in adding new applications is achieved, but organization and navigation between applications deteriorate
Solution Approach 1:
The patent establishes a pre-configured integration framework with standardized interfaces, event handlers, and communication protocols before applications are integrated. This preliminary structure includes predefined integration patterns and a organized architecture that guides how applications connect and interact, eliminating the need for ad-hoc deployment while maintaining flexibility for adding new applications through the established framework.
3Reliability
If technology-specific integration tools are used, then communication between specific application types is enabled, but the number of tools required grows and maintenance difficulty increases
Solution Approach 1:
The patent merges multiple technology-specific integration functions into a single unified integration layer. This consolidated architecture combines the roles of various specialized tools (Flash-HTML bridges, ActiveX controls, etc.) into one standardized integration framework that handles all application types through common mechanisms, reducing the total number of tools from many technology-specific solutions to a single maintenanceable system.
Data Source
AI summary
Various embodiments of systems and methods for interaction between applications built on different technologies are described herein. In one aspect, at least one action handler of a number of action handlers is associated with at least one application from a number of applications participating in the integrated scenario. In another aspect, at a first action handler that is associated with a source application, a request to access a target application is received. An identifier of the target application is retrieved and based on that identifier a second action handler associated with the target application is invoked, where the identifier of the target application is registered with the second action handler. The target application is launched by the second action handler in response to the received request.