Web Browser Message Passing via HTTP Notification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current messaging systems for Web-based applications face complexity and insecurity when passing messages from a backend to a Web browser, particularly due to the challenges of addressing socket connections and the need for additional J2EE solutions or Java Runtime Environment.
Innovation Solution
A method where the backend controller notifies the Web browser of waiting messages, allowing the browser to open an HTTP connection to retrieve them, utilizing standard HTTP or HTTPS protocols for secure message delivery, thereby avoiding complex socket connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If socket connections are used to pass messages from backend to Web browser, then message delivery capability is improved, but system complexity and security increase
Solution Approach 1:
The patent introduces a notification mechanism as an intermediary that bridges the backend and Web browser. Instead of directly establishing complex socket connections, the backend sends a simple notification to the browser, which then initiates the connection. This intermediary notification system simplifies the overall architecture while maintaining reliable message delivery.
Solution Approach 2:
The patent inverts the traditional connection initiation approach. Rather than the backend initiating socket connections to the browser (which is complex and insecure), the browser is empowered to initiate connections to the backend after receiving a notification. This reversal simplifies the system architecture and improves security by allowing the browser to control connection establishment.
2Reliability
If socket connections are used for message passing, then message delivery is enabled, but security and reliability deteriorate
Solution Approach 1:
The patent reverses the connection initiation direction to improve security. Instead of the backend initiating potentially insecure socket connections to client browsers, the browser initiates connections to the backend after receiving a notification. This inversion allows the client to control the connection establishment process, reducing security vulnerabilities associated with server-initiated socket connections to browsers.
3Reliability
If JMS and socket connections are used, then message passing capability is improved, but ease of operation and deployment worsen
Solution Approach 1:
The patent extracts the heavy JMS messaging infrastructure from the solution and replaces it with a simplified notification-based approach using standard Web technologies. By removing the dependency on JMS and socket connections, the system becomes easier to deploy and operate while maintaining core message passing functionality through HTTP-based notifications and connections.
Data Source
AI summary
A method and system for passing messages to a Web browser. According to one embodiment, a controller receives one or more messages to be delivered to a Web browser session, provides notification to the Web browser session of the receipt of the one or more messages, receives a request by the Web browser session for the one or more messages in response to the notification, the request received via a connection opened by the Web browser session, and delivers the one or more messages to the Web browser session via the connection in response to the request.