CN115129469B - Cross-process communication method, device, equipment and storage medium - Google Patents

Abstract

The present disclosure relates to a cross-process communication method, apparatus, device, and storage medium. The method comprises the following steps: receiving a sub-process dependency request sent by a first sub-process by using a main process in an inter-process communication mode; then, the main process is utilized to control at least one second sub-process to execute a target task corresponding to the sub-process dependency request based on the sub-process dependency request, and an execution result corresponding to the target task is obtained; and further, the main process feeds back an execution result corresponding to the target task to the first subprocess through the inter-process communication mode. Therefore, the cross-process communication among the plurality of sub-processes can be managed through the main process, so that the cross-process communication among the sub-processes and the main process can be ensured, and the cross-process communication among the sub-processes can be ensured, namely, the effective cross-process communication among the processes can be ensured.

Description

Cross-process communication method, device, equipment and storage medium

technical field

The present disclosure relates to the technical field of communication, and in particular to a cross-process communication method, device, device and storage medium.

Background technique

A process can be a running activity of a program with independent functions on a certain data set. In order to propagate or exchange information between different application programs, different application programs need to communicate through their corresponding processes, thereby realizing cross-process communication.

However, as user requirements are continuously updated, the number of application programs running on terminal devices is also increasing. Therefore, providing a cross-process communication method for multiple processes corresponding to multiple application programs is an urgent technical problem to be solved at present.

Contents of the invention

In order to solve the above technical problems, the present disclosure provides a cross-process communication method, device, device and storage medium.

In a first aspect, the present disclosure provides a cross-process communication method, the method comprising:

Using the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication;

Using the main process to control at least one second sub-process to execute a target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task;

Using the main process to feed back the execution result corresponding to the target task to the first sub-process through the inter-process communication manner.

In a second aspect, the present disclosure provides a device for cross-process communication, which includes:

The sub-process dependency request receiving module is used for receiving the sub-process dependency request sent by the first sub-process through the inter-process communication mode by the main process;

A control module, configured to use the main process to control at least one second sub-process to execute a target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task;

The execution result feedback module is configured to use the main process to feed back the execution result corresponding to the target task to the first sub-process through the inter-process communication method.

In a third aspect, an embodiment of the present disclosure further provides a cross-process communication device, the device including:

processor;

memory for storing executable instructions;

Wherein, the processor is configured to read executable instructions from the memory, and execute the executable instructions to implement the cross-process communication method provided by the first aspect above.

In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the processor is enabled to implement the above-mentioned first On the one hand, the cross-process communication method provided.

Compared with the prior art, the technical solutions provided by the embodiments of the present disclosure have the following advantages:

A cross-process communication method, device, device, and storage medium in the embodiments of the present disclosure can use the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication; then use the main process to base the sub-process dependency request , controlling at least one second sub-process to execute the target task corresponding to the sub-process dependency request, to obtain the execution result corresponding to the target task; and then using the main process to feed back the execution result corresponding to the target task to the second sub-process through the inter-process communication method a child process. Therefore, the cross-process communication between multiple sub-processes can be managed through the main process, so that the cross-process communication between the sub-process and the main process can be guaranteed, and the cross-process communication between the sub-processes can also be guaranteed , that is, to ensure effective cross-process communication between processes.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, In other words, other drawings can also be obtained from these drawings without paying creative labor.

FIG. 1 is a schematic flowchart of a cross-process communication method provided by an embodiment of the present disclosure;

FIG. 2 is a schematic flowchart of another cross-process communication method provided by an embodiment of the present disclosure;

FIG. 3 is a schematic flowchart of another cross-process communication method provided by an embodiment of the present disclosure;

FIG. 4 is a logical schematic diagram of a cross-process communication method provided by an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a cross-process communication device provided by an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a cross-process communication device provided by an embodiment of the present disclosure.

Detailed ways

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the drawings, it should be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein; A more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for exemplary purposes only, and are not intended to limit the protection scope of the present disclosure.

It should be understood that the various steps described in the method implementations of the present disclosure may be executed in different orders, and/or executed in parallel. Additionally, method embodiments may include additional steps and/or omit performing illustrated steps. The scope of the present disclosure is not limited in this respect.

As used herein, the term "comprise" and its variations are open-ended, ie "including but not limited to". The term "based on" is "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one further embodiment"; the term "some embodiments" means "at least some embodiments." Relevant definitions of other terms will be given in the description below. It should be noted that concepts such as "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the sequence of functions performed by these devices, modules or units or interdependence.

It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative and not restrictive, and those skilled in the art should understand that unless the context clearly indicates otherwise, it should be understood as "one or more" multiple".

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are used for illustrative purposes only, and are not used to limit the scope of these messages or information.

At present, cross-process communication is generally implemented based on the socket (socket) communication mode of the Hyper Text Transfer Protocol (HTTP). However, the performance of this cross-process communication method is low, and it can only realize the communication between two applications, and cannot realize the communication between multiple applications; in addition, this cross-process communication method is limited to communication, and cannot perform underlying native operations.

It should be noted that since different processes may be written in different languages, it is necessary to provide a cross-process communication method that can adapt to different languages for processes written in different languages.

In order to solve the above problem, the cross-process communication method provided by the embodiment of the present disclosure will be described below with reference to FIG. 1 to FIG. 4 . In the embodiment of the present disclosure, the cross-process communication method may be executed by an electronic device or a server. Wherein, the electronic devices may include devices with communication functions such as mobile phones, tablet computers, desktop computers, and notebook computers. The server may be a cloud server or a server cluster or other device with storage and computing functions. It should be noted that, the following embodiments take an electronic device as an execution subject for exemplary explanation.

Fig. 1 shows a schematic flowchart of a cross-process communication method provided by an embodiment of the present disclosure.

As shown in FIG. 1, the cross-process communication method may include the following steps.

S110. Using the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication.

In the embodiment of the present disclosure, when multiple processes in the electronic device need to perform cross-process communication, if the first sub-process in the multi-process needs to use the functions of other sub-processes, the first sub-process can generate a sub-process dependency request, and The sub-process dependency request is sent to the main process through inter-process communication, then the main process can obtain the sub-process dependency request, and the main process can implement communication between the first sub-process and other sub-processes based on the request.

In the embodiments of the present disclosure, a main process refers to a process in the system for executing a main task, generating and managing other sub-tasks, and a sub-process refers to a process created by a parent process.

In the embodiments of the present disclosure, interprocess communication (interprocess communication, IPC) is a communication method for sharing messages between one process and another process.

In the embodiments of the present disclosure, the sub-process dependency request refers to request information that the first sub-process depends on other sub-processes to perform corresponding tasks.

Optionally, the number of the first subprocess may be at least one.

S120. Using the main process to control at least one second sub-process to execute the target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task.

In the embodiment of the present disclosure, after receiving the sub-process dependency request by the main process, the electronic device can extract the process ID from the sub-process dependency request, and if the process ID is the process ID of at least one second sub-process, control at least one The second sub-process executes the corresponding task, and after the at least one second sub-process executes the corresponding task, the execution result fed back by the at least one second sub-process is acquired.

In the embodiments of the present disclosure, the target task refers to a task to be executed to realize the feature function.

Wherein, the process identifier can represent the identifier of the subprocess. Optionally, the process identification may include any one of subprocess identification numbers (Identity Document, ID), package identifiers (Packet Identifier, PID) and other identifications.

In some embodiments, the main process first sends the subprocess dependency request to at least one second subprocess, and then at least one second subprocess executes the target task to obtain the execution result of the target task, and then the main process obtains the execution of the target task result.

In some other embodiments, the main process first sends the sub-process dependency request to at least one second sub-process, and then the at least one second sub-process and the main process jointly execute the target task, and the main process obtains the execution result of the target task.

S130, using the main process to feed back the execution result corresponding to the target task to the first sub-process through inter-process communication.

In the embodiment of the present disclosure, after the main process in the electronic device obtains the execution result of the target task, it can feed back the execution result of the target task to the first sub-process through the path corresponding to the sub-process dependency request, that is, continue to use inter-process communication. process, so as to realize cross-process communication between multiple processes.

It can be understood that the execution result of the target task can carry the process ID of the first sub-process and the process ID of at least one second sub-process, therefore, the path corresponding to the sub-process dependency request can be obtained according to the process ID of the first sub-process , and feed back the execution result to the first sub-process based on the path, so that the first sub-process can perceive that at least one second sub-process has completed task processing.

It should be noted that since IPC is a communication method with high performance, cross-process communication between multiple processes can also have good performance. In this way, compared with the cross-process communication method of http, the cross-process communication method based on IPC can effectively guarantee the performance of cross-process communication.

The embodiment of the present disclosure provides a cross-process communication method, which can use the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication; then use the main process to control at least one second sub-process based on the sub-process dependency request. The sub-process executes the target task corresponding to the sub-process dependency request, and obtains the execution result corresponding to the target task; and then uses the main process to feed back the execution result corresponding to the target task to the first sub-process through the inter-process communication mode. Therefore, the cross-process communication between multiple sub-processes can be managed through the main process, so that the cross-process communication between the sub-process and the main process can be guaranteed, and the cross-process communication between the sub-processes can also be guaranteed , that is, to ensure effective cross-process communication between processes.

In this embodiment of the present disclosure, optionally, the main process is written based on a first language, the first sub-process and at least one second sub-process are written based on a second language, and the first language and the second language are different; the first The child process is the main Electron process, and at least one second child process is a U3D child process.

Optionally, the first language may be Electron, and the second language may be U3D (Unity). Among them, Electron uses JavaScript, HTML and CSS to build a cross-platform desktop application framework, and U3D is a real-time 3D interactive content creation and operation platform developed based on C# language.

It should be noted that since IPC can realize cross-language communication, even though the main process and sub-processes in the multi-process are written in different languages, the IPC communication method can also ensure effective cross-process communication between processes, thus providing A specification for interlingual communication.

In another implementation manner of the present disclosure, at least one second subprocess and the main process may jointly execute the target task, or at least one second subprocess may execute the target task.

Fig. 2 shows a schematic flowchart of another cross-process communication method provided by an embodiment of the present disclosure.

As shown in FIG. 2, the cross-process communication method may include the following steps.

S210. Extract the sub-process identifier of the first sub-process from the sub-process dependency request.

In the embodiment of the present disclosure, when the main process in the electronic device detects a sub-process dependency request, in order to improve the security of cross-process communication, it can extract the sub-process identifier of the first sub-process from the request, and determine the first sub-process Whether the child process ID of the process is a stored ID.

In the embodiment of the present disclosure, the sub-process identifier of the first sub-process can represent the identity information of the first sub-process.

Optionally, the process identification may include any one of subprocess identification numbers (Identity Document, ID), package identifiers (Packet Identifier, PID) and other identifications.

S220. If the sub-process ID of the first sub-process is found from the pre-stored sub-process IDs, receive a sub-process dependency request sent by the first sub-process through inter-process communication.

In the embodiment of the present disclosure, after the main process in the electronic device obtains the sub-process ID of the first sub-process, it can compare the sub-process ID of the first sub-process with the pre-stored sub-process ID one by one. If the sub-process identification of the first sub-process is found in the sub-process identification of the sub-process, it means that the sub-process identification of the first sub-process is an already stored identification, and the sub-process dependency request can be directly received.

Specifically, after each sub-process is started, each sub-process can send its corresponding identifier to the main process, so that the main process can store the sub-process identifier corresponding to each sub-process.

It can be understood that if the sub-process ID of the first sub-process is not found from the pre-stored sub-process IDs, it means that the sub-process ID of the first sub-process is an unstored ID, and the sub-process dependency request can be rejected .

Therefore, in the embodiment of the present disclosure, by comparing the sub-process ID of the first sub-process in the sub-process dependency request with the pre-stored sub-process ID, selectively accepting or rejecting the sub-process dependency request can improve cross- Security of process communication.

S230. Send the sub-process dependency request to at least one second sub-process through inter-process communication, wherein the at least one second sub-process is used to generate the main process dependency request based on the sub-process dependency request.

In the embodiment of the present disclosure, after the main process in the electronic device sends the sub-process dependency request to at least one second sub-process, if at least one second sub-process needs to rely on the main process to perform some functions, at least one second sub-process A main process dependency request may be generated from a subprocess dependency request.

In the embodiments of the present disclosure, the main process dependency request refers to request information that at least one second sub-process relies on the main process to perform a corresponding task. Specifically, the main process dependency request may carry the dependent task module of the main process.

S240. In response to the main process dependency request fed back by the at least one second sub-process, determine an execution result of the main process corresponding to the target task.

In the embodiment of the present disclosure, the main process in the electronic device receives the main process dependency request, and may call the corresponding function module process task processing, and obtain the main process execution result corresponding to the target task.

In this embodiment of the present disclosure, the execution result of the main process may be an intermediate result obtained by the main process.

S250. Feedback the execution result of the main process corresponding to the target task to at least one second sub-process through inter-process communication, wherein at least one second sub-process is used to continue executing the target task based on the execution result of the main process, and obtain the corresponding execution result.

In the embodiment of the present disclosure, after the main process in the electronic device feeds back the execution result of the main process to at least one second sub-process, at least one second sub-process can take the execution result of the main process as the trigger condition of the target task, so that based on the The trigger condition continues task processing, and the execution result corresponding to the target task is obtained, that is, the final execution result is obtained.

S260. Receive an execution result corresponding to the target task fed back by at least one second sub-process through inter-process communication.

In the embodiment of the present disclosure, the main process in the electronic device may receive the execution result through the feedback channel of the execution result of the main process and by using inter-process communication.

S270. Receive an execution result corresponding to the target task fed back by at least one second sub-process through inter-process communication, wherein the at least one second sub-process is used to execute the sub-process dependency request corresponding to the target task.

In the embodiment of the present disclosure, after the main process in the electronic device sends the sub-process dependency request to at least one second sub-process, if at least one second sub-process does not need to rely on the main process to perform some functions, then at least one second sub-process The process can directly process the task to obtain the processing result of the target task, and then the main process can feed back the execution result of the target task to the main process.

Therefore, in the embodiments of the present disclosure, at least one second sub-process can perform task processing independently according to its own task execution situation, or the main process can assist in task processing, so that it can be applied to task processing in various application scenarios The process improves the flexibility of the task processing process.

S280. Use the main process to feed back the execution result corresponding to the target task to the first sub-process through inter-process communication.

Wherein, the specific implementation manners of S280 and S130 are similar, and details are not described here.

In yet another embodiment of the present disclosure, before the main process receives the sub-process dependency request, it needs to start each sub-process, and obtain and store the sub-process identification corresponding to each sub-process; after the main process obtains the execution result corresponding to the target task , at least one second child process can be closed.

Fig. 3 shows a schematic flowchart of another cross-process communication method provided by an embodiment of the present disclosure.

As shown in FIG. 3, the cross-process communication method may include the following steps.

S310. Based on the installation path of the first sub-process, start the first sub-process, and obtain and store a sub-process identifier corresponding to the first sub-process.

In the embodiment of the present disclosure, before performing cross-process communication, the main process can obtain the installation path of the first sub-process through IPC, and start the first sub-process based on the installation path; after the first sub-process is started, the main process The sub-process identifier corresponding to the first sub-process may be obtained through IPC, and the sub-process identifier corresponding to the first sub-process is stored.

In order to facilitate understanding of the process of obtaining the sub-process identifier corresponding to the first sub-process, FIG. 4 shows a schematic diagram of a cross-process communication method provided by an embodiment of the present disclosure.

As shown in Figure 4, after the first sub-process A is installed, first, the main process can obtain the installation path of the first sub-process A through IPC, and then, the main process can obtain the sub-process identifier corresponding to the first sub-process A through IPC , and store the subprocess identifier corresponding to the first subprocess A.

S320. Receive the process assistance request sent by the first sub-process through inter-process communication.

S330. In response to the process assistance request, start at least one second sub-process, and acquire and store a sub-process identifier corresponding to the at least one second sub-process.

Specifically, when the first sub-process needs to use the function of at least one second sub-process, a process assistance request can be generated, then the main process in the electronic device can receive the process assistance request through IPC, and then, in response to the request, pass IPC obtains the installation path of at least one second subprocess, and starts at least one second subprocess based on the installation path; after at least one second subprocess is started, the main process can obtain the subprocess corresponding to the second subprocess through IPC ID, and store at least one sub-process ID corresponding to the second sub-process.

Continue to refer to Figure 4, after the second sub-process B and the second sub-process C are installed, first, the main process can obtain the installation paths corresponding to the second sub-process B and the second sub-process C through IPC, and then, the main process obtains A process assistance request, and in response to the process assistance request, obtain the sub-process identifiers corresponding to the second sub-process B and the second sub-process C through IPC, and store the sub-process identifiers corresponding to the second sub-process B and the second sub-process C respectively Process ID.

S340. Use the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication.

S350. Using the main process to control at least one second sub-process to execute the target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task.

Wherein, the specific implementation manners of S340-S350 are similar to those of S110-S120, and will not be repeated here.

S360. Receive a sub-process shutdown request sent by at least one second sub-process through inter-process communication.

In the embodiment of the present disclosure, after at least one second sub-process executes the target task, at least one second sub-process in the electronic device needs to generate a sub-process shutdown request, and the main process can receive at least one second sub-process through IPC. A child process shutdown request sent by a process.

In the embodiment of the present disclosure, the sub-process closing request refers to information requesting the main process to close the sub-process.

Specifically, the subprocess shutdown request may carry at least one process identifier of the second subprocess.

S370. In response to the request to close the sub-process, close at least one second sub-process that has been started.

In an embodiment of the present disclosure, the main process in the electronic device may extract the process identifier of at least one second sub-process from the sub-process closing request, and close the at least one started second sub-process.

S380. When at least one second sub-process is closed, send the execution result corresponding to the target task to the first sub-process through inter-process communication.

In an embodiment of the present disclosure, after closing at least one second sub-process, the main process in the electronic device may notify the first sub-process of the closing result of the at least one second sub-process, so that the first sub-process determines that the target task has After the execution is completed, at the same time, the execution result of the target task is fed back to the first sub-process.

Further, after closing at least one second sub-process, the sub-process identifier of at least one second sub-process can be deleted, so that at least one second sub-process enters a dormant state after executing the target task, and uses at least one second sub-process next time process, the process identification corresponding to at least one second sub-process may be acquired again.

Therefore, in the embodiment of the present disclosure, the main process can control the opening and closing of the first sub-process and at least one second sub-process, so as to achieve the effect of the underlying native operation during the process of cross-process communication.

An embodiment of the present disclosure also provides a cross-process communication device for implementing the above-mentioned cross-process communication method, which will be described below with reference to FIG. 5 . In the embodiment of the present disclosure, the cross-process communication device may be an electronic device or a server. Wherein, the electronic devices may include devices with communication functions such as mobile phones, tablet computers, desktop computers, and notebook computers. The server may be a cloud server or a server cluster or other device with storage and computing functions.

Fig. 5 shows a schematic structural diagram of a cross-process communication device provided by an embodiment of the present disclosure.

As shown in FIG. 5, the cross-process communication device 500 may include:

The sub-process dependency request receiving module 510 is configured to use the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication;

The control module 520 is configured to use the main process to control at least one second sub-process to execute the target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task;

The execution result feedback module 530 is configured to use the main process to feed back the execution result corresponding to the target task to the first sub-process through inter-process communication.

The embodiment of the present disclosure provides a cross-process communication device, which can use the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication; then use the main process to control at least one second sub-process based on the sub-process dependency request. The sub-process executes the target task corresponding to the sub-process dependency request, and obtains the execution result corresponding to the target task; and then uses the main process to feed back the execution result corresponding to the target task to the first sub-process through inter-process communication. Therefore, the cross-process communication between multiple sub-processes can be managed through the main process, so that the cross-process communication between the sub-process and the main process can be guaranteed, and the cross-process communication between the sub-processes can also be guaranteed , that is, to ensure effective cross-process communication between processes.

In some optional embodiments, the main process is written based on the first language, the first sub-process and the second sub-process are written based on the second language, and the first language and the second language are different;

The first child process is the Electron main process, and at least one second child process is a U3D child process.

In some optional embodiments, the child process depends on the request receiving module 510, which may include:

a sub-process identification extraction unit, configured to extract the sub-process identification of the first sub-process from the sub-process dependency request;

The sub-process dependency request receiving unit is configured to receive the sub-process dependency request sent by the first sub-process through inter-process communication if the sub-process ID of the first sub-process is found from the pre-stored sub-process IDs.

In some optional embodiments, the control module 520 may include:

The sub-process dependency request sending unit is configured to send the sub-process dependency request to at least one second sub-process through inter-process communication, wherein at least one second sub-process is used to generate the main process dependency request based on the sub-process dependency request;

The main process execution result determination unit is configured to determine the main process execution result corresponding to the target task in response to the main process dependency request fed back by at least one second sub-process;

The main process execution result feedback unit is used to feed back the main process execution result corresponding to the target task to at least one second sub-process through inter-process communication, wherein at least one second sub-process is used to continue execution based on the main process execution result Target task, get the execution result corresponding to the target task;

The first receiving unit is configured to receive the execution result corresponding to the target task fed back by the second sub-process through inter-process communication.

In some optional embodiments, the control module 520 includes:

The sub-process dependency request sending unit sends the sub-process dependency request to at least one second sub-process, wherein at least one second sub-process is used to execute the target task corresponding to the sub-process dependency request;

The second receiving unit is configured to receive the execution result corresponding to the target task fed back by at least one second sub-process through inter-process communication, wherein the second sub-process is configured to request the corresponding target task based on the execution sub-process dependency.

In some optional embodiments, the device also includes:

The first sub-process starting module is configured to start the first sub-process based on the installation path of the first sub-process, and obtain and store a sub-process identifier corresponding to the first sub-process.

In some optional embodiments, the device also includes:

The second sub-process startup module is configured to receive the process assistance request sent by the first sub-process through inter-process communication;

In response to the process assistance request, start at least one second sub-process, and obtain and store a sub-process identifier corresponding to the at least one second sub-process.

In some optional embodiments, the device also includes:

A sub-process closing request receiving module, configured to receive a sub-process closing request sent by at least one second sub-process through inter-process communication;

The second sub-process closing module is configured to close at least one second sub-process that has been opened in response to the sub-process closing request;

Correspondingly, the execution result feedback module 530 is specifically configured to, when at least one second sub-process is closed, send the execution result corresponding to the target task to at least one first sub-process through inter-process communication.

It should be noted that the cross-process communication device 500 shown in FIG. 5 can execute each step in the method embodiment shown in FIG. 1 to FIG. 4 , and realize each process in the method embodiment shown in FIG. 1 to FIG. 4 and effects, which will not be described here.

Exemplary embodiments of the present disclosure also provide an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by at least one processor, and when executed by the at least one processor, the computer program is used to cause the electronic device to perform the method according to the embodiments of the present disclosure.

Exemplary embodiments of the present disclosure also provide a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute the method according to the embodiments of the present disclosure.

Exemplary embodiments of the present disclosure also provide a computer program product, including a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute the method according to the embodiments of the present disclosure.

Referring to FIG. 6, a structural block diagram of a cross-process communication device 600 that can be used as a server or a client of the present disclosure will now be described, which is an example of a hardware device that can be applied to various aspects of the present disclosure. The cross-process communication device 600 can be the above-mentioned Electronic equipment. Electronic device is intended to mean various forms of digital electronic computing equipment, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are by way of example only, and are not intended to limit implementations of the disclosure described and/or claimed herein.

As shown in FIG. 6 , the cross-process communication device 600 includes a computing unit 601, which can be configured according to a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603 , to perform various appropriate actions and processing. In the RAM 603, various programs and data required for the operation of the inter-process communication device 600 can also be stored. The computing unit 601 , ROM 602 and RAM 603 are connected to each other through a bus 604 . An input/output (I/O) interface 605 is also connected to the bus 604 .

Multiple components in the cross-process communication device 600 are connected to the I/O interface 605 , including: an input unit 606 , an output unit 607 , a storage unit 608 and a communication unit 609 . The input unit 606 can be any type of device capable of inputting information to the cross-process communication device 600, the input unit 606 can receive input digital or character information, and generate key signal input related to user settings and/or function control of the electronic device . The output unit 607 may be any type of device capable of presenting information, and may include, but is not limited to, a display, a speaker, a video/audio output terminal, a vibrator, and/or a printer. The storage unit 604 may include, but is not limited to, a magnetic disk and an optical disk. The communication unit 609 allows the cross-process communication device 600 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks, and may include, but not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and/or Or a chipset, such as a Bluetooth™ device, WiFi device, WiMax device, cellular communication device, and/or the like.

The computing unit 601 may be various general-purpose and/or special-purpose processing components having processing and computing capabilities. Some examples of computing units 601 include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processing processor (DSP), and any suitable processor, controller, microcontroller, etc. The calculation unit 601 executes the various methods and processes described above. For example, in some embodiments, the inter-process communication method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608 . In some embodiments, part or all of the computer program can be loaded and/or installed on the inter-process communication device 600 via the ROM 602 and/or the communication unit 609 . In some embodiments, the computing unit 601 may be configured in any other suitable way (for example, by means of firmware) to execute the cross-process communication method.

Program codes for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special purpose computer, or other programmable data processing devices, so that the program codes, when executed by the processor or controller, make the functions/functions specified in the flow diagrams and/or block diagrams Action is implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer discs, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

As used in this disclosure, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or means for providing machine instructions and/or data to a programmable processor (eg, magnetic disk, optical disk, memory, programmable logic device (PLD)), including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with the user, the systems and techniques described herein can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user. ); and a keyboard and pointing device (eg, a mouse or a trackball) through which a user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and can be in any form (including Acoustic input, speech input or, tactile input) to receive input from the user.

The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., as a a user computer having a graphical user interface or web browser through which a user can interact with embodiments of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system can be interconnected by any form or medium of digital data communication, eg, a communication network. Examples of communication networks include: Local Area Network (LAN), Wide Area Network (WAN) and the Internet.

A computer system may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other.

It should be noted that in this article, relative terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these No such actual relationship or order exists between entities or operations. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

The above are only specific implementation manners of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to these embodiments herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A cross-process communication method, characterized in that, comprising: Using the main process to receive the sub-process dependency request sent by the first sub-process through inter-process communication; Using the main process to control at least one second sub-process to execute a target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task, including: Send the sub-process dependency request to the at least one second sub-process through the inter-process communication method, wherein the at least one second sub-process is used to generate a main process dependency request based on the sub-process dependency request ; In response to the main process dependency request fed back by the at least one second sub-process, determine an execution result of the main process corresponding to the target task; Feedback the execution result of the main process corresponding to the target task to the at least one second sub-process through the inter-process communication, wherein the at least one second sub-process is used to continue based on the execution result of the main process Executing the target task to obtain an execution result corresponding to the target task; receiving an execution result corresponding to the target task fed back by the at least one second sub-process by means of the inter-process communication; Using the main process to control at least one second sub-process to execute a target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task; Using the main process to feed back the execution result corresponding to the target task to the first sub-process through the inter-process communication manner. 2. The method according to claim 1, wherein the main process is written based on a first language, the first sub-process and the at least one second sub-process are written based on a second language, and the the first language and said second language are not the same; The first sub-process is an Electron main process, and the at least one second sub-process is a U3D sub-process. 3. The method according to claim 1, wherein said utilizing the main process to receive the sub-process dependency request sent by the first sub-process through an inter-process communication method comprises: extracting the subprocess identifier of the first subprocess from the subprocess dependency request; If the sub-process identifier of the first sub-process is found from the pre-stored sub-process identifiers, the sub-process dependency request sent by the first sub-process is received through the inter-process communication manner. 4. The method according to claim 1, wherein said utilizing said main process to control at least one second sub-process to execute the target task corresponding to said sub-process dependency request based on said sub-process dependency request, to obtain The execution results corresponding to the target tasks include: Send the sub-process dependency request to the at least one second sub-process through the inter-process communication method, wherein the at least one second sub-process is used to execute the target task corresponding to the sub-process dependency request ; The execution result corresponding to the target task fed back by the at least one second sub-process is received through the inter-process communication manner. 5. The method according to claim 1, wherein, before the main process is used to receive the sub-process dependency request sent by the first sub-process through inter-process communication, the method further comprises: Based on the installation path of the first sub-process, start the first sub-process, and obtain and store a sub-process identifier corresponding to the first sub-process. 6. The method according to claim 5, wherein, in the installation path based on the first sub-process, start the first sub-process, and obtain and store the sub-process corresponding to the first sub-process After the process identification, the method also includes: receiving the process assistance request sent by the first sub-process by means of the inter-process communication; In response to the process assistance request, start the at least one second sub-process, and obtain and store a sub-process identifier corresponding to the at least one second sub-process. 7. The method according to claim 5, wherein, before using the main process to feed back the execution result corresponding to the target task to the first sub-process through the inter-process communication method, The method also includes: Receive a sub-process shutdown request sent by the at least one second sub-process by means of the inter-process communication; closing the at least one second sub-process that has been started in response to the sub-process closing request; Correspondingly, using the main process to feed back the execution result corresponding to the target task to the first sub-process through the inter-process communication method includes: In the case that the at least one second sub-process is closed, the execution result corresponding to the target task is sent to the first sub-process through the inter-process communication manner. 8. A cross-process communication device, characterized in that it comprises: The sub-process dependency request receiving module is used for receiving the sub-process dependency request sent by the first sub-process through the inter-process communication mode by the main process; A control module, configured to use the main process to control at least one second sub-process to execute a target task corresponding to the sub-process dependency request based on the sub-process dependency request, and obtain an execution result corresponding to the target task; An execution result feedback module, configured to use the main process to feed back the execution result corresponding to the target task to the first sub-process through the inter-process communication method; The control module includes: A sub-process dependency request sending unit, configured to send the sub-process dependency request to the at least one second sub-process through the inter-process communication method, wherein the at least one second sub-process is used to send the sub-process dependency request based on the The child process dependency request generates the main process dependency request; a main process execution result determining unit, configured to determine the main process execution result corresponding to the target task in response to the main process dependency request fed back by the at least one second sub-process; The main process execution result feedback unit is configured to feed back the execution result of the main process corresponding to the target task to the at least one second sub-process through the inter-process communication method, wherein the at least one second sub-process uses continue to execute the target task based on the execution result of the main process, and obtain an execution result corresponding to the target task; The first receiving unit is configured to receive the execution result corresponding to the target task fed back by the at least one second sub-process through the inter-process communication manner. 9. A cross-process communication device, characterized in that, comprising: processor; memory for storing executable instructions; Wherein, the processor is configured to read the executable instruction from the memory, and execute the executable instruction to implement the cross-process communication method according to any one of claims 1-7. 10. A computer-readable storage medium on which a computer program is stored, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the processor is enabled to implement the above-mentioned claim 1- The cross-process communication method described in any one of 7.

Images