A local procedure calling method, apparatus, device and medium

Abstract

The present application discloses a local procedure calling method, device, device and medium, including: creating a process connection object between an interface process and a target process; creating a first session object corresponding to the interface process and a second session object corresponding to the target process; The first process function calling interface responds to the object function calling interface and passes in the target parameters; the interface response object asynchronously calls the first session object; the first session object asynchronously notifies the second session object to call the second process function; Obtain the asynchronous notification corresponding to the function call result sent by the second session object, and obtain the function call result; the first session object asynchronously notifies the function call result to the interface response object; the interface response object returns the function call result to the first process function, During the procedure call process between the interface process and the target process, the interface corresponding to the interface response object control interface process continues to provide services. It can ensure the timeliness of interface response.

Description

technical field [0001] The present application relates to the field of communication technologies, and in particular, to a local procedure calling method, apparatus, device and medium. Background technique [0002] Traditional inter-process communication usually exchanges data through pipes, messages, signals, sockets, etc., but these technologies only provide the interaction of basic data or information and cannot satisfy inter-process procedure calls. [0003] At present, in order to meet the requirement of inter-process procedure calls, open source remote procedure call frameworks such as gRPC and Thrift and Microsoft RPC (that is, remote procedure call remote procedure call) have appeared, but these frameworks are based on the concepts of Client and Server. Although it basically satisfies inter-process procedure calls, some remote procedure call libraries only support synchronous calls and cannot meet interface responsive procedure calls. Although other remote procedure ...

AI Technical Summary

Problems solved by technology

[0002] Traditional inter-process communication usually exchanges data through pipes, messages, signals, sockets, etc., but these technologies only provide basic data or information interaction and cannot satisfy inter-process procedure calls.

[0003] At present, in order to meet the needs of inter-process procedure calls, open source remote procedure call frameworks such as gRPC and Thrift and Microsoft RPC (remote procedure call) have emerged, but these frameworks are based on the concepts of Client and Server. Although it basically satisfies inter-process procedure calls, some remote procedure call libraries only support synchronous calls and cannot satisfy interface-responsive procedure calls. Although other remote procedure call libraries support asynchronous calls, users need to deal with interface response issues by themselves, which increases user development. complexity and efficiency

In addition, these concepts applicable to remote procedure call libraries are relatively complicated, inconvenient for development and debugging, troublesome to deploy, and poor in scalability, so they are not suitable for local procedure calls.

Images