Web Application Framework for Dynamic Script Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web application development technologies face challenges in managing associations between behaviors on web pages, leading to performance issues and inefficient resource management, particularly in cross-browser compatibility and interactive web applications, where scripts are randomly placed and lack centralized management, resulting in bottlenecks during user interactions and slow download processes.

Innovation Solution

A framework using standard object-oriented programming techniques is implemented, allowing developers to create web applications with a component-based pattern that separates document presentation from structure and behavior, enabling centralized management of resources and behaviors through a resource creation method, page interpreter, and lifecycle management components, which associate JavaScript classes with page elements and manage bindings dynamically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If scripts are placed throughout the page in a manner which is not managed centrally, then developers can add interaction and functionality, but resource management becomes problematic and performance issues occur

Engineering Contradiction:
ImproveinteractivityVSAvoidresource management
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments script management into distinct components: a behavior definition phase (where behaviors are declared with dependencies) and a behavior activation phase (where scripts are loaded on demand). This segmentation allows the system to manage resources efficiently while maintaining interactivity, as scripts are not loaded until needed rather than being embedded throughout the page.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by requiring developers to define behavior dependencies and script requirements in advance during the behavior definition phase. The system records these dependencies and activates scripts only when needed, preventing premature resource consumption while ensuring scripts are available when required.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If applications become more interactive, then user engagement increases, but the size of code and data increases, slowing the download process

Engineering Contradiction:
ImproveinteractivityVSAvoiddownload speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent extracts interactive functionality from the initial page load into separate, on-demand script modules. Only essential content is loaded initially, while interactive behaviors and their associated scripts are extracted and loaded only when triggered by user actions or dynamic content needs, significantly reducing initial download size while maintaining interactivity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements dynamic script loading where the set of loaded scripts changes based on user interactions and content requirements. Scripts are dynamically activated or deactivated based on current needs, allowing the application to adapt its resource footprint in real-time rather than loading all interactive components upfront.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If the set of components grow in an unbounded manner, then functionality increases, but the ability to download and render becomes expensive

Engineering Contradiction:
ImprovefunctionalityVSAvoidrendering cost
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by loading and rendering only the necessary components and scripts for the current view or interaction, rather than rendering all possible components. The system determines the minimal set of behaviors and scripts needed based on current context, avoiding unnecessary rendering costs while maintaining the ability to provide extensive functionality when needed.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7849437B2Object oriented web application framework
Publication Date: 2010.12.07 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7849437B2 patent drawing
  • US7849437B2 patent drawing
  • US7849437B2 patent drawing

AI summary

A framework for implementing web-based applications using standard object-oriented programming techniques. The framework may be implemented by computer-executable components executable by a Web browser is provided. The components include a resource creation method for creating resource objects, a page interpreter creating instances of objects based on bindings defined in a web-page, and a lifecycle management component for managing instances of the objects.