Declarative Resource Scripts for Centralized Trigger Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computing scenarios, decentralizing additional processing for accessing secured data sets across various client applications can lead to security control diminishment and complexity, as clients may need to handle authorization, logging, and supplemental data retrieval, which complicates network transport and maintenance.
Innovation Solution
Centralizing supplemental processing by associating resource scripts with specific data sets and protocol verbs, allowing the host to execute pre- and post-triggers for operations like HTTP GET, HTTP POST, and HTTP DELETE, ensuring reliable and centralized data access without complicating client applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If additional processing (authorization, logging, supplemental data retrieval) is decentralized to client applications, then clients can perform these operations independently, but security control is diminished and system complexity increases
Solution Approach 1:
The patent introduces a host system as an intermediary between client applications and data sets. The host centralizes supplemental processing functions (authorization, logging, data supplementation) and executes them on behalf of clients when they access data sets. This mediator approach maintains client independence while consolidating complex processing logic in a centralized location, thereby reducing overall system complexity and improving security control.
2Ease of operation
If additional processing is decentralized to client applications, then clients can handle their own authorization and logging, but security control is diminished
Solution Approach 1:
The host acts as a trusted intermediary that enforces security policies centrally. When clients access data sets, the host executes pre-trigger scripts for authorization checks and post-trigger scripts for logging, ensuring that security control mechanisms are consistently applied. This maintains client autonomy in initiating operations while ensuring reliable security control through centralized enforcement.
3Reliability
If resource scripts are executed centrally by the host, then security and control are maintained, but network transport and maintenance complexity increase
Solution Approach 1:
The patent segments the resource script execution process into distinct components: pre-trigger scripts that execute before data access operations and post-trigger scripts that execute after. This segmentation allows for independent development, testing, and maintenance of different script types. The host manages these segmented script components separately, reducing maintenance complexity while maintaining centralized control over resource access.
4Loss of information
If multiple additional requests are issued for supplemental processing, then complete data retrieval is achieved, but network interactions increase
Solution Approach 1:
The patent merges supplemental processing operations with the primary data access operation by executing resource scripts during the same network interaction. Pre-trigger scripts prepare data before retrieval, and post-trigger scripts supplement retrieved data, all within a single request-response cycle. This combining approach achieves complete data retrieval without requiring multiple separate network interactions, thereby reducing network latency and improving efficiency.
Data Source
AI summary
Data sets of various types may be accessible through a host according to a protocol, such as a RESTful HTTP interface. Various domains may involve domain-specific processes to be executed as pre-triggers or post-triggers of various protocol requests (e.g., an HTTP GET request specifying a Read operation on an access-restricted data set may involve an authorization operations set that verifies the access privileges of the requester.) A host of the data set may be configured to receive a resource script expressing the operations set in a script language, to store the resource script, and to associated it with at least one data set and at least one verb of the protocol. Upon later receiving a protocol request specifying the verb and the resource, the host may then execute the resource script (as a pre-trigger and/or as a post-trigger) in accordance with the business logic of the domain.