Remote API Access Point Instances for Direct Process Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional methods do not support remote process-to-process direct function calls or pointer delivery between remote processes, limiting the ability for efficient remote communication and programming between server and client devices using Application Programming Interfaces (API).
Innovation Solution
The system implements a method for remote communication and programming through API interfaces by creating access point instances on both server and client devices, using compiled headers to establish relayer and callback access points that enable direct function calls without a central inter-process service manager, allowing for remote process-to-process communication and pointer delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional API methods are used for local process communication, then direct function calls are simple and efficient, but remote process-to-process direct function calls are not supported
Solution Approach 1:
The patent introduces access point instances as intermediary components that enable remote process-to-process communication. These access points act as mediators between remote processes, allowing direct function calls without requiring complex centralized service management. The access point instances handle the complexity of remote communication internally while presenting a simple interface to applications.
2Productivity
If centralized inter-process service manager is used for remote communication, then service registration and management are simplified, but communication efficiency and performance are reduced
Solution Approach 1:
The patent segments the centralized service management function into distributed access point instances that operate autonomously. Instead of a single centralized service manager, multiple access point instances are distributed across different processes and devices, each handling its own communication needs independently. This segmentation eliminates the performance bottleneck of centralized management while maintaining organized service discovery and communication.
3Ease of operation
If remote communication is implemented without access point instances, then system structure is simpler, but direct function calls and pointer delivery between remote processes are not enabled
Solution Approach 1:
The patent uses access point instances as copyable templates that can be instantiated multiple times across different processes. Each access point instance is a lightweight copy that contains the necessary communication logic and state, allowing direct function calls between remote processes without requiring complex point-to-point configuration. The copying mechanism enables scalable remote communication while keeping individual instance complexity low.
Data Source
AI summary
Methods and systems are provided for Remote Application Programming Interface (RAPI) communications between server and client devices. In an embodiment, server and client devices comprise memories and hardware processors coupled to the memories. The hardware processors execute instructions to perform operations that instantiate access point instances on both server side and client side. The instructions are generated from compiling API interface classes with remote communication classes, wherein the compiling includes a procedure of creating new classes through double inheritance. By receiving an API connection message from a client device, the server device clones a default relayer access point instance and assigns the cloned relayer access point instance to process API requests received thereafter from the client device.