Web Application Interoperability via Event Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Web applications hosted in the same Web page cannot dynamically communicate or interoperate with each other, limiting their ability to react to services or data generated by other applications, which restricts the functionality and user experience.
Innovation Solution
A method that allows dynamic communication and interoperability between Web applications by using an application management entity to facilitate the subscription of services and the transmission of parameter types and values between applications, enabling real-time interaction and automation of operations based on generated data or events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple Web applications are hosted in the same Web page using portlets, then the page can display multiple application components in a customizable way, but the applications cannot communicate or interoperate with each other
Solution Approach 1:
The patent introduces an event routing mechanism that acts as an intermediary between portlets. Events generated by one portlet are routed through this mechanism to appropriate subscriber portlets, enabling communication without direct application-to-application interaction. The routing mechanism matches event types with subscriber interests to establish indirect communication channels.
Solution Approach 2:
The patent segments the communication system into independent event publishers, event subscribers, and event routing mechanisms. Each portlet operates independently, publishing events based on its own logic and subscribing to events of interest, while the routing mechanism coordinates communication. This segmentation maintains portlet independence while enabling interoperability.
2Ease of manufacture
If Web applications are developed independently and hosted separately, then each application maintains its independence and modularity, but they cannot dynamically react to services or data generated by other applications
Solution Approach 1:
The patent implements a feedback mechanism where portlets can subscribe to events generated by other portlets. When an event occurs in one portlet, the routing mechanism delivers it to subscribed portlets, creating a feedback loop that enables dynamic reaction. Subscribers receive events asynchronously and can respond based on their own logic, maintaining independence while achieving adaptability.
Solution Approach 2:
The patent makes the system dynamic by allowing portlets to subscribe to and unsubscribe from event types at runtime. The event routing mechanism dynamically matches events with subscribers based on event type compatibility. This dynamic subscription model allows applications to adapt their behavior based on the presence and state of other applications without requiring static configuration.
3Device complexity
If portlets are used to host Web applications in the same page, then applications can cohabit in a customizable layout, but connection and interoperability between applications is not possible
Solution Approach 1:
The patent creates a universal event routing mechanism that works across all portlet types and technologies. The system defines standard event types and subscription interfaces that any portlet can implement, making the communication mechanism universally applicable. This allows heterogeneous applications to interoperate through a common protocol, enhancing reliability across diverse components.
Data Source
Figure 1
Figure 2A~2B
Figure 2C~2D
AI summary
The invention relates to a method of communication between a first application and at least one second application accessible within a web browser page. According to the invention, such a method comprises: ■ a step of dynamically subscribing said first application to at least one service of said at least one second application; ■ a step of executing, by said first application, at least one operation taking into account a value of at least one parameter generated by the execution of said at least one service and transmitted by said second application to said first application.