Notification-Based Web Application Framework for Asynchronous Database Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database-backed web applications suffer from synchronous communication limitations, where the client and server are typically locked during request-response cycles, restricting flexibility and collaboration in data, user interface, and logic manipulation, and do not allow for seamless asynchronous updates or interchangeable client-server roles.
Innovation Solution
A notification-based web application framework that employs asynchronous communication techniques, allowing for dynamic content exposure from a database to browsers, enabling users to manipulate data, user interface, and logic through browsers, and push updates without specific client requests, using an architecture that facilitates two-way communication between web and database servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous request-response communication is used between client and server, then the communication protocol is simple and reliable, but the client and server are locked during request-response cycles, restricting flexibility and collaboration
Solution Approach 1:
The patent implements dynamic communication modes that can switch between synchronous and asynchronous operations. The server can dynamically change its behavior from waiting for requests to proactively pushing updates, allowing the system to adapt to different operational requirements while maintaining reliability through established connection management.
Solution Approach 2:
The communication protocol is segmented into distinct phases: connection establishment, data transmission, acknowledgment handling, and connection closure. This segmentation allows reliable synchronous communication for critical operations while enabling asynchronous updates through separate notification mechanisms, thus maintaining both reliability and flexibility.
2Ease of operation
If traditional server-client architecture is used, then the server controls the communication flow, but the client cannot initiate communication or receive updates without specific requests
Solution Approach 1:
The patent inverts the traditional communication paradigm by enabling server-initiated communication to clients. The server can push updates and notifications to clients without waiting for specific requests, allowing the client to receive real-time information proactively. This inversion maintains ease of operation for clients while significantly improving update delivery efficiency.
Solution Approach 2:
The system implements a feedback mechanism where the server monitors database changes and automatically sends notifications to clients when updates occur. This feedback loop eliminates the need for clients to continuously poll for updates, improving productivity while keeping the client interface simple and operationally easy.
3Adaptability or versatility
If multiple web application systems are introduced to facilitate communication, then asynchronous and two-way communication is enabled, but the system architecture becomes more complex
Solution Approach 1:
The patent introduces an intermediary communication layer that handles asynchronous messaging between the server and client. This intermediary layer abstracts the complexity of asynchronous communication from the main application logic, allowing multiple web application systems to work together seamlessly while managing architectural complexity through a dedicated communication infrastructure.
Solution Approach 2:
The communication system is designed with multi-functional capabilities that can handle both synchronous requests and asynchronous push notifications through a unified framework. This universality allows the same architectural components to serve multiple communication purposes, reducing the need for separate specialized systems and thereby managing overall architectural complexity.
4Adaptability or versatility
If users can manipulate data, user interface, and logic through browsers, then the browser becomes a powerful development tool, but the browser must handle complex processing tasks
Solution Approach 1:
The patent extracts complex processing tasks from the browser and relocates them to the server. The browser handles only high-level manipulation of data, user interface, and logic through simplified interfaces, while the server performs the heavy computational work. This extraction maintains the browser's versatility as a development tool while significantly reducing its processing complexity.
Solution Approach 2:
The system replaces complex mechanical processing operations in the browser with remote procedure calls and server-side computation. Instead of the browser performing complex data processing, the server executes these operations and returns results, substituting the mechanical burden with a more efficient distributed architecture that maintains browser versatility.
Data Source
AI summary
An interactive web application framework allows a user to define user interface and logic of a web application and publish the web application. A web application system can receive a database notification from a database server. The database notification can indicate that an update of a user interface item has occurred in a database. The database notification can be generated by the database server in response to a request from a user device. The request can be a request to receive information when any state change occurs at the database server. The web application system can initiate communication with the user device without responding to a specific request requesting the update. The web application system can generate instructions for refreshing the user interface item in a browser, and push the instructions to the user device.