Web App Native DLL Access via Browser Extension and Named Pipe

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Web-based applications struggle to access and utilize computationally intensive local executables, such as binary DLL files, due to security restrictions and performance limitations of JavaScript.

Innovation Solution

A system and method that enable web applications to access native binary DLLs through a long-running computational process on the host computing device, using a browser extension and native messaging application to communicate via standard input/output and a named pipe.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If web applications use JavaScript to process data, then security is maintained, but processing speed and capability are insufficient for high-volume image data

Engineering Contradiction:

ImprovesecurityVSAvoidprocessing speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent introduces a native messaging application as an intermediary between the web application and the local executable. The web application communicates with the native messaging application via standard web APIs, which then connects to the local executable through a named pipe. This mediator architecture allows the web application to maintain security constraints while accessing powerful local processing capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If web applications access local binary DLL files directly, then processing capability is improved, but security risks increase

Engineering Contradiction:

Improveprocessing capabilityVSAvoidsecurity risks

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The native messaging application serves as a controlled intermediary that bridges the web application and the local binary DLL. It manages the communication through a named pipe, providing a secure interface that limits direct access while enabling necessary processing capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is divided into distinct segments: the web application layer, the native messaging application layer, and the local executable layer. Each segment has defined interfaces and responsibilities, with the named pipe providing a controlled communication boundary between segments.

Inventive Principle:

Principle #1Segmentation

3Productivity

If client devices host local executables for high-volume data processing, then processing capability is improved, but accessibility by web applications becomes unreliable

Engineering Contradiction:

Improveprocessing capabilityVSAvoidaccessibility

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The native messaging application acts as a reliable intermediary that ensures consistent communication between web applications and local executables. It handles the complexity of process creation, communication channel establishment, and data transmission, providing stable access to local processing capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces direct binary communication mechanisms with a standardized named pipe interface. This substitution provides a more reliable and controllable communication mechanism that works consistently across different systems and contexts.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Productivity

If web applications transfer large amounts of data to the server, then processing capability is improved, but network bandwidth requirements and latency increase

Engineering Contradiction:

Improveprocessing capabilityVSAvoidnetwork bandwidth

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The patent extracts computationally intensive processing tasks from the network-based server model and places them on local devices. By running processing-capable executables locally and only transferring necessary data through the named pipe, the system reduces network bandwidth requirements while maintaining processing capability.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS12288083B2System and method for communication between a web-based application and a computation intensive executable

Publication Date: 2025.04.29 DASSAULT SYSTEMS AMERICAS CORP

AI summary

A system and method provide access by a web application running on a host computing device in communication with a remote server to a native binary DLL. A browser extension to the web application and a native messaging application communicate with the browser extension via standard input/output. A long-running computational process on the host computing device configured as a wrapper for the binary DLL is executable by the host computing device. The native messaging application and the long-running computational process communicate with one another via a named pipe, and the long-running computational process duration is independent of the native messaging application duration.