Framework Socket for Real-Time Web Data Push

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web application frameworks require complex programming and incur computational expenses on both client-side web browsers and servers due to the need for frequent data requests and updates, often resulting in inefficient and non-cross-platform compatible applications.

Innovation Solution

A real-time web application framework that uses framework widgets with persistent connections (framework sockets) to receive data updates without proactive client requests, leveraging message brokers and plug-in architectures to distribute data efficiently across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If web applications use frequent data requests and updates to achieve real-time data exchange, then real-time data availability is improved, but computational expense and resource consumption increase

Engineering Contradiction:
Improvereal-time data availabilityVSAvoidcomputational expense
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent inverts the traditional request-response model by implementing a push-based architecture where the server proactively pushes data to clients through persistent connections (WebSockets, Server-Sent Events) rather than waiting for client requests. This reversal eliminates the need for continuous polling and reduces computational overhead significantly.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent establishes persistent connections and subscribes to data sources in advance before data becomes available. By pre-configuring the communication channels and data subscriptions, the system can immediately receive and deliver updates when data changes, eliminating the need for repeated connection establishment and data validation cycles.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If web applications implement complex programming frameworks to support real-time updates, then functionality and adaptability are improved, but programming complexity and development time increase

Engineering Contradiction:
Improvecross-platform compatibilityVSAvoidprogramming complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal communication layer that works across multiple platforms and browsers through standardized APIs (Fetch API, Event Source, WebSocket). The framework provides a single codebase that automatically adapts to different environments, eliminating the need for platform-specific implementations while maintaining cross-platform compatibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an intermediary communication framework that sits between the application logic and various transport protocols. This mediator layer handles protocol-specific details and provides a unified interface for data subscription and push operations, simplifying the programming model while supporting multiple communication technologies.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If web applications use traditional request-response models to exchange data, then simplicity of implementation is maintained, but efficiency and real-time performance deteriorate

Engineering Contradiction:
Improveimplementation simplicityVSAvoiddata exchange efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent maintains persistent connections that remain open and active throughout the application lifecycle, allowing continuous data flow without interruption. This eliminates the repeated connection establishment, authentication, and data validation overhead inherent in traditional request-response models, significantly improving data exchange efficiency.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8683357B2Providing real time web application framework socket
Publication Date: 2014.03.25 RED HAT INC
  • US8683357B2 patent drawing
  • US8683357B2 patent drawing
  • US8683357B2 patent drawing

AI summary

A method and apparatus for providing real-time web applications is described. In one embodiment, the method includes receiving a web page from a web application framework at a client computer system, the web page including at least one framework widget with a subscription to a topic. The method may also include opening a framework socket in a web browser run on the client computer system. In one embodiment, the method may further include rendering the framework socket along with the at least one framework widget in a web browser run by the client computer system.