Email Webclient Notification Queuing via HTTP Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Webclients do not maintain persistent connections with HTTP servers, leading to potential loss of attachment data during email composition if connectivity is lost, and notifications may be missed due to the lack of persistent connections, resulting in incomplete user communication.
Innovation Solution
Implementing an HTTP server that maintains a persistent connection with the mail server and stores attachment data and notifications, allowing for retrieval and delivery even after connectivity is re-established, ensuring data integrity and notification delivery without altering existing connection types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If webclient does not maintain persistent connection to HTTP server, then connection complexity is reduced and ease of operation is improved, but notification delivery reliability deteriorates and information loss increases
Solution Approach 1:
The patent introduces a notification queue as an intermediary component between the HTTP server and webclient. The queue stores notifications that are generated when the webclient is disconnected, allowing them to be delivered later when the connection is restored. This mediator resolves the contradiction by enabling reliable notification delivery without requiring persistent connections.
Solution Approach 2:
The system performs preliminary actions by storing notifications in the queue before the webclient reconnects. When a notification event occurs during disconnection, the system proactively saves the notification data in the queue, ensuring it is ready for delivery. This preliminary storage action prevents information loss and ensures reliable delivery without requiring the client to be continuously connected.
2Device complexity
If webclient does not maintain persistent connection, then device complexity is reduced, but data loss increases during connectivity failures
Solution Approach 1:
The notification queue acts as an intermediary storage mechanism that temporarily holds attachment data and notification information. When the webclient disconnects, the queue preserves the data instead of losing it. This intermediary storage layer prevents information loss while maintaining the simplicity of non-persistent connections.
Solution Approach 2:
The system provides beforehand cushioning by creating a buffer (notification queue) that protects against data loss during connectivity failures. The queue serves as a cushion that absorbs the impact of disconnections, storing critical data safely until the connection is restored, thereby preventing information loss without requiring complex persistent connection management.
3Speed
If server sends notification immediately upon event, then notification speed is improved, but notification delivery reliability deteriorates when client is disconnected
Solution Approach 1:
The notification queue serves as a mediator between immediate notification generation and actual client delivery. When an event occurs, the notification is immediately created and stored in the queue (maintaining speed), then delivered when the client reconnects (ensuring reliability). This intermediary storage resolves the contradiction between fast notification generation and reliable delivery.
Solution Approach 2:
The system performs preliminary notification creation and queue storage immediately when an event occurs, maintaining fast notification speed. The notification data is prepared and stored in advance in the queue, ready for delivery. This preliminary action ensures both speed of generation and reliability of eventual delivery, even if the client is temporarily disconnected.
Data Source
AI summary
Notifications received from an email server can be stored and provided to a webclient upon subsequent communications from the webclient received at an HTTP server. Notifications stored in a database or a storage are retrieved and transmitted to the webclient by backup or alternate HTTP servers when the webclient requests service. An attachment received from a webclient for a message in composition can be saved by an HTTP server in a storage system so that a backup HTTP server can locate the attachment and provide the attachment to a messaging server when the user is ready to send the message.