Scripting Resource Ordering via Server-Side Dependency Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional enterprise applications face inefficiencies in resolving dependencies for scripting language resources, leading to dependency-related errors and slow page load times due to multiple network requests, especially in high-latency networks.

Innovation Solution

A method for dynamically ordering scripting language resources during runtime, where a server-side application analyzes dependencies and merges resources into a single file, allowing for efficient loading of resources and their dependencies in a single HTTP request without rebuilding the application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If scripting language resources are loaded in order of appearance without dependency analysis, then the loading process is simple, but dependency-related errors occur and execution fails

Engineering Contradiction:
Improveexecution successVSAvoiddependency resolution complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary dependency analysis and resource ordering on the server side before transmitting resources to the client. The application server analyzes the dependency relationships among scripting language resources and determines the correct loading order in advance, then provides this ordered information to the web browser. This preliminary action ensures that resources are loaded in the correct sequence without requiring complex client-side dependency resolution.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If multiple network requests are used to load scripting language resources individually, then each resource can be loaded separately, but network latency increases and page load time slows down

Engineering Contradiction:
Improvepage load speedVSAvoidnetwork latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system merges multiple individual resource loading requests into a single batch request. Instead of loading each scripting language resource separately through individual HTTP requests, the web browser sends a single request that includes multiple resource identifiers. The application server processes this batch request and returns multiple resources in one response, significantly reducing network latency and improving page load speed.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If conventional enterprise applications use standard resource loading mechanisms, then implementation is straightforward, but they cannot efficiently resolve dependencies for custom components and functionalities

Engineering Contradiction:
Improvecustom component supportVSAvoiddependency resolution efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system introduces an intermediary application server that acts as a mediator between the web browser and scripting language resources. This intermediary server performs dependency analysis, determines the correct loading order, and manages resource distribution. This mediator enables efficient dependency resolution for custom components and functionalities while maintaining a simple client-side implementation, as the complex dependency management is handled by the intermediary server.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10146885B1Method and system for deciding on ordering of scripting language source code for dependency resolution
Publication Date: 2018.12.04 DELL EMC
  • US10146885B1 patent drawing
  • US10146885B1 patent drawing
  • US10146885B1 patent drawing

AI summary

Disclosed are systems and methods for ordering scripting language source code. A request for a first scripting language resource may be received. The first scripting language resource may provide one or more functionalities for a web application. A second scripting language resource may be identified based on dependency information. In some implementations, the dependency information identifies a dependency between the first scripting language resource and the second scripting language resource. A response including the first and second scripting language resources may be generated. In some implementations, the first and second scripting language resources may be ordered based on the dependency information. In various implementations, the response may be capable of being transmitted to a web browser.