Closure Document Offline Logic Embedding

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Implementing web-based applications is complex and costly, requiring specialized software and skilled programmers, and users may lose access to these applications when offline due to the need for continuous network connectivity.

Innovation Solution

The creation and use of a 'closure document' that abstracts network-based application functionalities into logic components, allowing off-the-shelf applications to access and modify data offline, enabling offline operation by embedding logic and data within a self-contained document that can be updated and synchronized with the server when connectivity is restored.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If web-based applications are implemented using specialized software and skilled programmers, then the application functionality and reliability are improved, but the implementation cost and complexity increase

Engineering Contradiction:

Improveapplication functionalityVSAvoidimplementation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a local copy of the web application functionality by embedding a snapshot of the application state, including data and logic components, directly into the client document. This allows the client to execute application logic locally without requiring continuous server connection or specialized web application software, thereby reducing implementation complexity while maintaining functionality.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent extracts essential application logic and data from the server environment and embeds it within the client document. By taking out the critical components needed for offline operation and incorporating them into the document structure, the system enables application functionality to run locally without requiring the full server infrastructure or specialized programming expertise.

Inventive Principle:

Principle #2Taking out (Extraction)

2Reliability

If continuous network connection is maintained for accessing web-based applications, then the application accessibility and data synchronization are improved, but the user convenience and flexibility deteriorate when network is unavailable

Engineering Contradiction:

Improvedata synchronizationVSAvoiduser convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent performs preliminary actions by capturing and embedding a snapshot of the application state, including data and logic components, into the client document before network disconnection occurs. This preliminary embedding of application state allows the user to continue accessing and manipulating data offline without immediate network connection, improving user convenience while maintaining the ability to synchronize later.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces a closure document as an intermediary that stores application state locally on the client side. This intermediary document acts as a bridge between the server and the user, allowing offline access to application functionality while maintaining the capability to synchronize with the server when network connectivity is restored, thus balancing data synchronization reliability with user convenience.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If offline access to web-based applications is enabled, then the user flexibility and convenience are improved, but the data consistency and synchronization with server may deteriorate

Engineering Contradiction:

Improveoffline access capabilityVSAvoiddata consistency

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the system tracks changes made to the embedded application state in the closure document and manages synchronization with the server when network connectivity is restored. This feedback loop ensures that offline modifications are properly communicated to the server, maintaining data consistency while preserving offline access capabilities.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The closure document serves as an intermediary that manages the transition between offline and online states. It stores application state locally for offline access while maintaining the capability to synchronize with the server, acting as a buffer that resolves the conflict between offline flexibility and data consistency by managing synchronization when network connectivity is available.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8656269B1Providing a functionality by loading logic into a document

Publication Date: 2014.02.18 MICRO FOCUS LLC

AI summary

To implement at least one functionality, a template having one or more logic components corresponding to the at least one functionality is provided. The template and a data collection are accessed to load the one or more logic components and data into a closure document. The closure document is provided to enable updating of data in the closure document using the one or more logic components.