Avatar Framework Thin-Server Architecture for Web Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing feature-rich HTML5 web applications for browsers and mobile devices poses challenges related to client-server architecture, including high start-up times and slow editing processes, especially when deciding which tasks to execute on the client versus the server, affecting cost, robustness, and flexibility.

Innovation Solution

A modular, end-to-end web development framework called 'Avatar' that uses a thin-server architecture with JavaScript, HTML5, and supports REST, WebSockets, and Server-Sent Events, allowing for rich, responsive, and mobile-enabled applications with a clear separation of client and server logic, enabling developers to create server-side services and bind HTML5 components to services written in any language.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a thick client architecture is used to execute complex tasks locally, then editing speed and responsiveness are improved, but start-up time and device cost increase

Engineering Contradiction:
Improveediting speedVSAvoidstart-up time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the application into a thin client component (HTML5 browser-based interface) and a server component (Java EE backend). The thin client handles only UI rendering and user interaction, while the server handles complex business logic and data processing. This segmentation allows the client to start quickly without downloading large application bundles, while still providing rich editing capabilities through server-side processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a servlet container and WebSocket infrastructure as intermediaries between the thin client and the Java EE server. These intermediaries enable real-time bidirectional communication, allowing the thin client to receive push notifications and send commands without maintaining a thick client installation, thus reducing start-up time while maintaining editing responsiveness.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If more functionality is implemented on the client side, then application responsiveness is improved, but device complexity and cost increase

Engineering Contradiction:
Improveapplication responsivenessVSAvoidclient device requirements
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The server-side Java EE application performs self-service by handling authentication, data validation, business logic execution, and session management. This eliminates the need for complex client-side implementations, allowing the use of simple HTML5 browsers on mobile devices while maintaining enterprise-grade functionality and responsiveness through server-side processing.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent creates a universal thin client implementation using HTML5, CSS3, and JavaScript that runs on any modern browser across different platforms (mobile devices, tablets, desktops). This universal client provides consistent responsive behavior across all devices without requiring device-specific optimizations or increased hardware complexity, while the server adapts to different client capabilities.

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

3Loss of time

If a thin-server architecture is used to reduce client burden, then start-up time is reduced, but communication overhead and network dependency increase

Engineering Contradiction:
Improvestart-up timeVSAvoidnetwork communication overhead
Core Design Contradiction:
Loss of timeVSLoss of information

Solution Approach 1:

The patent implements continuous bidirectional communication using WebSocket technology, which maintains persistent connections between the thin client and server. This allows for real-time data synchronization, push notifications, and collaborative editing without requiring repeated HTTP requests. The continuous connection minimizes communication overhead by establishing a single persistent channel rather than multiple discrete requests, reducing network latency and information loss.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS9992268B2Framework for thin-server web applications
Publication Date: 2018.06.05 ORACLE INT CORP
  • US9992268B2 patent drawing
  • US9992268B2 patent drawing
  • US9992268B2 patent drawing

AI summary

In various aspects, a framework is provided for building rich, responsive, and mobile-enabled HTML 5 web applications. In one embodiment, the framework is based on a thin server architecture (TSA) that uses REST, SSE, and WebSocket to communicate with the server side. This framework, sometimes referred to herein as ‘Avatar’ is a modular, end-to-end web development framework for building enterprise mobile and desktop applications using JavaScript, HTML5 and a thin-server architecture.