Custom String Resource Retrieval Optimization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing application development frameworks face performance issues due to the retrieval of large, shared resource bundles containing thousands of resource items, many of which are unused, leading to increased network traffic and computational burden, especially in cloud computing environments where bandwidth and latency are concerns.

Innovation Solution

The proposed solution involves analyzing document and metadata to identify only the custom key-value pairs actually used, coalescing these into a single server request, and caching them, thereby reducing the number of server requests and optimizing the retrieval of custom string resources, allowing for a 'smart' request that minimizes network traffic and computational load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If large, shared resource bundles containing thousands of resource items are retrieved, then completeness of resource availability is improved, but network traffic and computational burden increase

Engineering Contradiction:

Improveresource availabilityVSAvoidnetwork traffic

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the specific resource items that are actually needed by the user interface components from the large, shared resource bundles. Instead of retrieving entire bundles containing thousands of resources, the system identifies and retrieves only the subset of resources that are referenced by the UI components, thereby reducing network traffic while ensuring availability of necessary resources.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the large, shared resource bundles into smaller, component-specific resource sets. Each user interface component is associated with only the resource items it actually uses, creating segmented resource allocations that reduce unnecessary data transmission and improve retrieval efficiency.

Inventive Principle:

Principle #1Segmentation

2Reliability

If large, shared resource bundles containing thousands of resource items are retrieved, then completeness of resource availability is improved, but computational burden increases

Engineering Contradiction:

Improveresource availabilityVSAvoidcomputational burden

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts and retrieves only the specific resource items that are actually referenced by user interface components, rather than processing entire large resource bundles. This extraction approach reduces the computational burden on both client and server sides by minimizing the amount of data that needs to be processed, transmitted, and cached.

Inventive Principle:

Principle #2Taking out (Extraction)

3Reliability

If multiple server requests are made for resource bundles, then completeness of resource retrieval is improved, but network traffic increases

Engineering Contradiction:

Improveresource retrieval completenessVSAvoidnetwork traffic

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges multiple separate server requests for resource bundles into a single optimized request. By analyzing which resource items are actually needed and combining them into one request, the system reduces the number of network transactions while ensuring that all necessary resources are retrieved, thereby reducing network traffic without compromising retrieval completeness.

Inventive Principle:

Principle #5Merging (Combining)

4Reliability

If entire resource bundles are retrieved, then all possible resources are available, but unused resource retrieval increases

Engineering Contradiction:

Improveresource availabilityVSAvoidunused resource retrieval

Core Design Contradiction:

ReliabilityVSLoss of substance

Solution Approach 1:

The patent extracts and retrieves only the specific resource items that are actually used by user interface components, rather than retrieving entire resource bundles that contain many unused resources. This selective extraction eliminates the waste of bandwidth and processing power on unused resources while ensuring that all necessary resources are available.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of retrieving the complete resource bundles (excessive action), the system retrieves only the partial set of resources that are actually needed by the UI components. This partial retrieval approach avoids the inefficiency of fetching and processing resources that will not be used.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS10048948B2Optimized retrieval of custom string resources

Publication Date: 2018.08.14 ORACLE INT CORP

AI summary

In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow a desktop integration framework to optimize retrieval of custom string resources from resource bundles hosted by server computer systems. A client computer that uses a document as a user interface to a web-server application hosted by a server-computer system can determine which custom string resources are to be utilized in the document. The client computer system can request only the custom string resources that are determined to be utilized in the document from the server-computer system in a single request thereby optimizing retrieval without requesting entire resource bundles.