CN116089099A

CN116089099A - Communication method, device, electronic equipment and storage medium

Info

Publication number: CN116089099A
Application number: CN202310003604.0A
Authority: CN
Inventors: 周鸿轩
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2023-01-03
Filing date: 2023-01-03
Publication date: 2023-05-09

Abstract

The disclosure relates to a communication method, a device, an electronic apparatus and a storage medium, including: and sending a message to be processed to the target thread by the main thread, calling the sequence waiting component to enable the source thread to be in an information waiting state, receiving preset wake-up information, wherein the preset wake-up information is used for ending the information waiting state of the source thread currently, and acquiring feedback information, obtained by the target thread based on the message to be processed, from the data sharing area. According to the method and the device, communication between the source thread and the target thread is guaranteed through the main thread, after the source thread sends the message to be processed, the subsequent operation is not executed through the sequence waiting component, and the reply of the target thread is waited for, so that synchronous communication is realized.

Description

Communication method, device, electronic equipment and storage medium

Technical Field

The disclosure relates to the technical field of internet, and in particular relates to a communication method, a device, electronic equipment and a storage medium.

Background

Communication between threads can generally be divided into two steps: for example, the a-thread sends a message to the B-thread, and the B-thread then feeds back a reply message to the a-thread. In the prior art, two communication modes may be included, including: synchronous communication and asynchronous communication. In the synchronous communication mode, after the A thread sends a message to the B thread, the A thread waits for the message replied by the B thread and then executes subsequent operation; in the asynchronous communication mode, the thread a does not wait for the message replied by the thread B after sending the message to the thread B, but performs the subsequent operation first, and then performs the corresponding operation after waiting for the reply of the thread B.

For example, in a complex browser application scenario involving the use of a multi-working thread architecture, the communication between threads is performed using a browser-provided messaging interface (Post Message Interface, PMI) that can only provide an asynchronous communication mode, but cannot meet the requirements of synchronous communication.

Disclosure of Invention

The disclosure provides a communication method, a device, an electronic device and a storage medium, and the technical scheme of the disclosure is as follows:

according to a first aspect of embodiments of the present disclosure, there is provided a communication method, including:

sending a message to be processed to a target thread through a main thread;

calling a sequence waiting component to enable a source thread to be in an information waiting state;

receiving preset wake-up information; the method comprises the steps that preset wake-up information is used for ending an information waiting state of a source thread at present;

and acquiring feedback information obtained by the target thread based on the processing of the message to be processed from the data sharing area.

In some possible embodiments, the preset wake-up information is generated by triggering after the target thread stores feedback information in the data sharing area and resets a signal sharing flag corresponding to the source thread from a first flag to a second flag; the first mark characterizes that the source thread is in an information waiting state; the second identifier characterizes that the source thread is not in an information waiting state;

Before sending the message to be processed to the target thread through the main thread, the method further comprises the following steps:

the signal share flag is reset to the first flag.

In some possible embodiments, obtaining feedback information of the target thread based on the processing of the message to be processed from the data sharing area includes:

determining an area identifier of a data sharing area corresponding to a source thread;

sending an information acquisition request to a data sharing module; the information acquisition request comprises a region identifier;

receiving feedback information returned by the data sharing module; the feedback information is information read by the data sharing module from the data sharing area corresponding to the area identifier.

In some possible embodiments, after obtaining feedback information obtained by the target thread based on the processing of the pending message from the data sharing area, the method further includes:

invoking a codec to convert feedback information in a first format in the data sharing area to feedback information in a second format; the second format is the data format corresponding to the target thread.

In some possible embodiments, the source thread, the main thread, and the target thread are threads in a browser.

According to a second aspect of embodiments of the present disclosure, there is provided a communication method, including:

Receiving a message to be processed sent by a source thread through a main thread;

processing the message to be processed to obtain feedback information;

storing feedback information into a data sharing area corresponding to a source thread, and resetting a signal sharing mark corresponding to the source thread from a first mark to a second mark;

generating a sharing notification; the sharing notification is used for triggering generation of preset wake-up information; the preset wake-up information is used for ending the information waiting state of the source thread caused by calling the sequence waiting component.

In some possible embodiments, storing the feedback information in the data sharing area corresponding to the source thread includes:

calling a coder-decoder to convert feedback information in a second format corresponding to the thread into feedback information in a first format corresponding to the data sharing area;

and storing the feedback information in the first format to a data sharing area corresponding to the source thread.

According to a third aspect of embodiments of the present disclosure, there is provided a communication apparatus comprising:

the first sending module is configured to send a message to be processed to the target thread through the main thread;

the calling module is configured to execute the calling sequence waiting component so that the source thread is in an information waiting state;

the first receiving module is configured to execute receiving preset wake-up information; the method comprises the steps that preset wake-up information is used for ending an information waiting state of a source thread at present;

And the acquisition module is configured to acquire feedback information, which is obtained by the target thread based on the processing of the message to be processed, from the data sharing area.

the apparatus further comprises:

the first reset module is configured to perform resetting of the signal sharing flag to a first flag.

In some possible embodiments, the acquisition module is configured to perform:

In some possible embodiments, the apparatus further comprises:

a decoding module configured to perform calling of the codec to convert feedback information of a first format to feedback information of a second format in the data sharing area; the second format is the data format corresponding to the target thread.

According to a fourth aspect of embodiments of the present disclosure, there is provided a communication apparatus comprising:

the second receiving module is configured to execute the message to be processed, which is sent by the source thread through the main thread;

the processing module is configured to execute processing of the message to be processed to obtain feedback information;

the storage module is configured to store feedback information to a data sharing area corresponding to the source thread;

a flag resetting module configured to perform resetting of a signal sharing flag corresponding to the source thread from a first flag to a second flag;

a generation module configured to perform generating a sharing notification; the sharing notification is used for triggering generation of preset wake-up information; the preset wake-up information is used for ending the information waiting state of the source thread caused by calling the sequence waiting component.

In some possible embodiments, the storage module is configured to perform:

According to a fifth aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute instructions to implement the method as in any of the first or second aspects above.

According to a sixth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the method of any one of the first or second aspects of embodiments of the present disclosure.

According to a seventh aspect of the embodiments of the present disclosure, there is provided a computer program product comprising a computer program stored in a readable storage medium, the computer program being read from the readable storage medium by at least one processor of the computer device and executed such that the computer device performs the method of any one of the first or second aspects of the embodiments of the present disclosure.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

and sending a message to be processed to the target thread by the main thread, calling the sequence waiting component to enable the source thread to be in an information waiting state, receiving preset wake-up information, wherein the preset wake-up information is used for ending the information waiting state of the source thread currently, and acquiring feedback information, obtained by the target thread based on the message to be processed, from the data sharing area. According to the method and the device, communication between the source thread and the target thread is guaranteed through the main thread, after the source thread sends the message to be processed, the subsequent operation is not executed through the sequence waiting component, and the reply of the target thread is waited for, so that synchronous communication is realized.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of an application environment shown in accordance with an exemplary embodiment;

FIG. 2 is a flow chart illustrating a method of communication according to an exemplary embodiment;

FIG. 3 is a flow chart illustrating a method of communication according to an exemplary embodiment;

FIG. 4 is a flowchart illustrating a method of communication for a browser, according to an example embodiment;

FIG. 5 is a block diagram of a communication device, according to an example embodiment;

FIG. 6 is a block diagram of a communication device, according to an example embodiment;

fig. 7 is a block diagram of an electronic device for communication, according to an example embodiment.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar first objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

It should be noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for presentation, analyzed data, etc.) related to the present disclosure are information and data authorized by the user or sufficiently authorized by each party.

Referring to fig. 1, fig. 1 is a schematic diagram illustrating an application environment of a communication method according to an exemplary embodiment, and as shown in fig. 1, the application environment is an application environment in a browser, where the browser includes a source thread 01, a main thread 02, a target thread 03, and a data sharing module 04.

In some possible embodiments, the browser may be a browser in a server. The server may include a stand-alone physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), basic cloud computing services such as big data and artificial intelligent platforms, and the like. Operating systems running on the server may include, but are not limited to, android systems, IOS systems, linux, windows, unix, and the like.

In some possible embodiments, the browser may be a browser in a client. Clients may include, but are not limited to, smart phones, desktop computers, tablet computers, notebook computers, smart speakers, digital assistants, augmented Reality (AR)/Virtual Reality (VR) devices, smart wearable devices, and the like. Or may be software running on the client, such as an application, applet, etc. Alternatively, the operating system running on the client may include, but is not limited to, an android system, an IOS system, linux, windows, unix, and the like.

In some possible embodiments, the source thread sends a message to be processed to the target thread through the main thread, calls the sequence waiting component to enable the source thread to be in an information waiting state, receives preset wake-up information, and the preset wake-up information is used for ending the information waiting state in which the source thread is currently in, and obtains feedback information, obtained by the target thread based on the message to be processed, from the data sharing area.

Fig. 2 is a flowchart of a communication method according to an exemplary embodiment, and as shown in fig. 2, the communication method may be applied to a client, or may be applied to other node devices, and execute a subject as a source thread, including the following steps:

In step S201, a message to be processed is sent to a target thread by a main thread.

In some possible embodiments, the source thread may send a pending message to the target thread via the main thread.

In this embodiment of the present application, the source thread, the main thread, and the target thread may be threads in a browser, and the source thread and the target thread may be referred to as working sub-threads, and may include other working sub-threads in addition to the source thread and the target thread referred to above. .

That is, the scenarios in which the source thread, the main thread, and the target thread are located may be complex browser application scenarios involving the use of a multi-work thread architecture. Generally, a multi-task thread architecture is typically used to implement split tasks for a high-level central processing unit (central processing unit, CPU), isolation of scripting language JavaScript execution environments, simulation of an operating system multi-process architecture, and so forth. In such a scenario, since the source thread and the target thread are different threads in the browser, there is no direct interaction (such as data interaction or calling methods) between the source thread and the target thread. Based on this, the source thread can perform data interaction through the main thread and the target thread when communication is performed between the source thread and the target thread.

Alternatively, in addition to the browser, the scenes where the source thread, the main thread and the target thread are located may be scenes related to other application programs, such as application programs of a communication application, an audio-video application, an office application and the like, which use a multi-working thread architecture.

Communication between threads can generally be divided into two steps: for example, the a-thread sends a message to the B-thread, and the B-thread then feeds back a reply message to the a-thread. In the embodiment of the application, two communication modes can be included, including: synchronous communication and asynchronous communication. In the synchronous communication mode, after the A thread sends a message to the B thread, the A thread waits for the message replied by the B thread and then executes subsequent operation; in the asynchronous communication mode, the a thread does not wait for the message replied by the B thread after sending the message to the B thread, but performs the subsequent operation first, and then performs the corresponding operation after waiting for the reply of the B thread.

In a complex browser application scenario involving the use of a multi-working thread architecture, the inter-thread communication uses a browser-provided messaging interface (Post Message Interface, PMI) that can only provide an asynchronous communication mode, but cannot meet the requirements of synchronous communication. Based on this, embodiments of the present application provide an implementation of synchronous communication between a source thread and a target thread.

In some possible embodiments, when the source thread needs to send a pending message to the target thread, the pending message and the identification information of the target thread may be sent to the main thread. Correspondingly, when the main thread receives the message to be processed and the identification information of the target thread, the thread to be forwarded can be determined to be the target thread through the identification information of the target thread, so that the main thread can send the message to be processed to the target thread.

In step S203, the call order wait component places the source thread in an information wait state.

As has been set forth above, embodiments of the present application provide an implementation of synchronous communication between a source thread and a target thread. Thus, in order for the source thread to perform subsequent operations after sending the pending message to the target thread through the main thread and waiting for the reply of the target thread, the source thread may invoke the order waiting component to place the source thread in an information waiting state.

In the embodiment of the application, the calling sequence waiting component can be implemented in the browser by calling atom. Atom is an application program interface (Application Interface, API) of an atomic operation provided by a browser, and the atomic operation ensures that the value of data being read or written is expected, i.e. the next atomic operation must be started after the last atomic operation is finished, and the operation process is not interrupted. In this way, it can be explained that the source thread is in the information waiting state through the application program interface of the atomic operation.

In an alternative embodiment, the embodiment of the present application further provides a signal sharing flag in the browser, where the signal sharing flag may be represented by a binary bit.

In some possible embodiments, the signal sharing flag may be used to represent two states: an information waiting state represented by a binary 1 and an information preparing state represented by a binary 0, or a state represented by a binary 0 which is not in the information waiting state.

Alternatively, before step S201, the source thread may reset the signal sharing flag to the first flag, that is, the information waiting state represented by binary 1. The source thread may invoke the order wait component such that the source thread is in an information wait state may be specifically represented as the source thread may invoke the order wait component to wait for the information wait state represented by the signal sharing flag being updated to an information ready state represented by a binary 0. At this point, the signal share flag also identifies the information wait state represented by a binary 1, and the source thread will enter the pending wait state.

Correspondingly, the target thread can receive the message to be processed sent from the source thread through the main thread. After the target thread receives the message to be processed, the message to be processed can be processed to obtain feedback information.

In some possible embodiments, when the main thread receives the pending message and the identification information of the target thread, a corresponding data sharing area may be allocated to the source thread, i.e. the main thread may send the area identification of the data sharing area allocated to the source thread. When the main thread sends a message to be processed to the target thread, the region identifier of the data sharing region corresponding to the source thread can be sent to the target thread.

In other possible embodiments, the source thread is created by the main thread. When the main thread creates the source thread, a corresponding data sharing area can be allocated for the source thread, that is, the main thread can send the area identification of the data sharing area allocated for the source thread to the source thread. Based on the above, when the source thread sends the message to be processed to the target thread through the main thread, the area identifier of the data sharing area can also be sent to the target thread through the main thread.

Thus, after the target thread obtains the feedback information, the data sharing area corresponding to the source thread can be determined based on the area identifier of the data sharing area corresponding to the source thread sent by the main thread, and then the feedback information is stored in the data sharing area corresponding to the source thread.

In this embodiment of the present application, the data sharing area may be a whole area or a partial area in the data sharing module. Alternatively, the data sharing module in the browser may be a module in a memory sharing mode provided by the browser, that is, a shared array buffer (SharedArrayBuffer, SAB), which may read or modify a piece of memory data for a plurality of threads in the browser, where the data stored in the memory is binary format data.

Based on the SAB data sharing area, in an alternative embodiment, since the feedback information is generally data in the format of Json, text, etc., in order to enable the target thread to store the feedback information in the data sharing area corresponding to the source thread, the target thread may invoke the codec to convert the feedback information in the second format corresponding to the target thread into the feedback information in the first format corresponding to the data sharing area, that is, may invoke the codec to convert the feedback information in the format of Json, text, etc. corresponding to the thread into the feedback information in the binary format corresponding to the data sharing area. And then, storing the feedback information in the binary format into a data sharing area corresponding to the source thread.

Since it is mentioned that after the source thread sends the message to be processed to the target thread through the main thread, the sequence waiting component is invoked to make the source thread be in the information waiting state, that is, the sequence waiting component is invoked to wait for the information waiting state represented by the signal sharing flag with binary 1 to update to the information preparation state represented by binary 0. Therefore, after the target thread stores the feedback information in the binary format in the data sharing area corresponding to the source thread, the signal sharing flag corresponding to the source thread may be reset from the first flag to the second flag, that is, the information waiting state of the signal sharing flag corresponding to the source thread represented by binary 1 is reset to the information preparing state represented by binary 0. At this time, the signal share flag has identified an information preparation state represented by binary 0.

In this embodiment of the present application, after the target thread resets the information waiting state represented by binary 1 for the signal sharing flag corresponding to the source thread to the information preparation state represented by binary 0, the target thread may generate a sharing notification, where the sharing notification is used to trigger the target thread or the main thread to generate preset wake-up information, where the preset wake-up information is used to end the information waiting state that the source thread is currently in due to the calling sequence waiting component.

In step S205, receiving preset wake-up information; the preset wake-up information is used for ending the information waiting state of the source thread.

In this embodiment of the present application, after the target thread may generate the sharing notification, the sharing notification may trigger generation of preset wake-up information, and send the preset wake-up information to the source thread. Correspondingly, after the source thread receives the preset wake-up information, the source thread can be used for ending the information waiting state of the source thread.

In step S207, feedback information obtained by the target thread based on the processing of the message to be processed is acquired from the data sharing area.

Because of the above, when the main thread receives the message to be processed and the identification information of the target thread, a corresponding data sharing area may be allocated to the source thread, that is, the main thread may send the area identification of the data sharing area allocated to the source thread. Alternatively, the main thread may allocate a corresponding data sharing area for the source thread when the source thread is created. Therefore, after the source thread finishes the information waiting state in which the source thread is currently in, the area identification of the data sharing area corresponding to the source thread can be determined. And sending an information acquisition request to the data sharing module, wherein the information acquisition request comprises the area identifier.

Alternatively, the source thread may read the feedback information in the data sharing module. Specifically, after the data sharing module receives the information obtaining request, the area identifier can be obtained through analysis, feedback information stored by the target thread is obtained from the data sharing area corresponding to the area identifier, and then the data sharing module can send the feedback information to the source thread.

Optionally, since the feedback information fed back by the data sharing module is feedback information in a binary format, and the target thread (may also be a source thread or a main thread) applies data in a format of Json, text, etc., after the source thread obtains the feedback information in the binary format, the codec may be invoked to convert the feedback information in the first format corresponding to the data sharing area into the feedback information in the second format corresponding to the target thread, that is, the codec may be invoked to convert the feedback information in the binary format corresponding to the data sharing area into the feedback information in the format of Json, text, etc. corresponding to the thread.

Fig. 3 is a flowchart illustrating a communication method according to an exemplary embodiment, and as shown in fig. 3, the communication method may be applied to a client, or may be applied to other node devices, and execute a subject as a target thread, including the following steps:

In step S301, a message to be processed sent by a source thread is received through a main thread.

In some possible embodiments, the signal share flag may be reset to a first flag, i.e., a binary 1 representing an information wait state, before the source thread sends the pending message. When the source thread needs to send a message to be processed to the target thread, the message to be processed and the identification information of the target thread may be sent to the main thread. Correspondingly, when the main thread receives the message to be processed and the identification information of the target thread, the thread to be forwarded can be determined to be the target thread through the identification information of the target thread, so that the main thread can send the message to be processed to the target thread.

In this way, the target thread can receive the information to be processed sent by the source thread through the main thread, so that the source thread can execute subsequent operations after sending the information to be processed to the target thread through the main thread and waiting for the reply of the target thread, and the source thread can call the sequence waiting component to enable the source thread to be in an information waiting state. That is, the source thread may invoke the order wait component to wait for the information wait state represented by a binary 1 to update to an information ready state represented by a binary 0 for the signal sharing flag. At this point, the signal share flag also identifies the information wait state represented by a binary 1, and the source thread will enter the pending wait state.

In step S303, the message to be processed is processed to obtain feedback information.

In this embodiment of the present application, after receiving the message to be processed, the target thread may process the message to be processed to obtain feedback information.

In step S305, feedback information is stored in the data sharing area corresponding to the source thread.

In this embodiment of the present application, after the target thread obtains the feedback information, the data sharing area corresponding to the source thread may be determined based on the area identifier of the data sharing area corresponding to the source thread sent by the main thread, and then the feedback information is stored in the data sharing area corresponding to the source thread.

Because feedback information generated by the threads in the browser is generally data in Json, text and other formats, in order to enable the target thread to store the feedback information in the data sharing area corresponding to the source thread, the target thread can call the codec to convert the feedback information in the second format corresponding to the target thread into the feedback information in the first format corresponding to the data sharing area, i.e. can call the codec to convert the feedback information in Json, text and other formats corresponding to the threads into the feedback information in the binary format corresponding to the data sharing area. And then, storing the feedback information in the binary format into a data sharing area corresponding to the source thread.

In step S307, the signal sharing flag corresponding to the source thread is reset from the first flag to the second flag.

In this embodiment of the present application, after the source thread sends the message to be processed to the target thread through the main thread, the order waiting component is called to make the source thread be in the information waiting state, that is, the order waiting component is called to wait for the information waiting state of the signal sharing flag represented by binary 1 to update to the information preparation state represented by binary 0. Therefore, after the target thread stores the feedback information in the binary format in the data sharing area corresponding to the source thread, the signal sharing flag corresponding to the source thread may be reset from the first flag to the second flag, that is, the information waiting state of the signal sharing flag corresponding to the source thread represented by binary 1 is reset to the information preparing state represented by binary 0. At this time, the signal share flag has identified an information preparation state represented by binary 0.

In step S309, a sharing notification is generated, where the sharing notification is used to trigger generation of preset wake-up information, and the preset wake-up information is used to end the information waiting state of the source thread caused by calling the order waiting component.

In this embodiment of the present application, after the target thread resets the information waiting state represented by binary 1 for the signal sharing flag corresponding to the source thread to the information preparing state represented by binary 0, the target thread may generate a sharing notification, where the sharing notification is used to trigger generation of preset wake-up information, where the preset wake-up information is used to end the information waiting state currently in by the source thread due to the calling of the sequential waiting component.

Correspondingly, after the source thread receives the preset wake-up information, the source thread can be used for ending the information waiting state of the source thread.

When the main thread receives the message to be processed and the identification information of the target thread, a corresponding data sharing area can be allocated for the source thread, namely, the main thread can send the area identification of the data sharing area allocated for the source thread to the source thread. Alternatively, the main thread may allocate a corresponding data sharing area for the source thread when the source thread is created. Therefore, after the source thread finishes the information waiting state in which the source thread is currently in, the area identification of the data sharing area corresponding to the source thread can be determined. And sending an information acquisition request to the data sharing module, wherein the information acquisition request comprises the area identifier.

Optionally, since the feedback information fed back by the data sharing module is feedback information in a binary format, and the thread application is generally Json, text and other data, after the source thread obtains the feedback information in the binary format, the codec may be invoked to convert the feedback information in the first format corresponding to the data sharing area into feedback information in a second format corresponding to the target thread, that is, invoke the codec to convert the feedback information in the binary format corresponding to the data sharing area into feedback information in the Json, text and other formats corresponding to the thread.

In the embodiment of the present application, the binary format specification of the data stored in the data sharing area is:

the 1 st byte represents the original data format type, currently supporting JSON objects, text objects and Binary objects. 0 denotes JSON,1 denotes Text, and 2 denotes Binary.

The 2 nd to 5 th bytes represent the total length of the data. Since the data sharing area corresponding to the shared array buffer (SharedArrayBuffer, SAB) needs to be specified with a storage length at the time of creation, the size cannot be dynamically adjusted with an actual message. A larger data sharing area is applied in the initial stage for storing the message data with different possible lengths. A total of 4 bytes may represent 0-2-32-1, which itself is also close to the maximum size of 2-32 bytes that can be stored by the current SAB.

Starting at byte 6 and going to the location identified by the length is the actual data payload area.

How the content encoding of the data payload is performed is described below:

binary format: no encoding is required, as the data sharing area is also stored in binary format, and thus is filled directly into the data sharing area. Text format: the text encoder is used for converting the character strings into Unit8Array and filling the Unit8Array into the data sharing area. JSON object format: firstly, converting an object in the JavaScript of the scripting language into a JSON character string by using JSON.string, then converting the JSON character string into a Unit8Array by using the same mode as the Text format, and finally filling the JSON character string into a data sharing area.

Only one set of threads requiring synchronous communication, including the source thread and the target thread, is set forth above. If the browser has a plurality of groups of threads requiring synchronous communication within the same time period, the browser comprises a first source thread and a first target thread, and a second source thread and a second target thread.

Before the first source thread sends the message to be processed through the main thread, or before the second source thread sends the message to be processed through the main thread, the browser may assign a respective signal sharing flag to the first source thread or the second source thread, respectively, such as assigning a first signal sharing flag to the first source thread and assigning a second signal sharing flag to the second source thread.

Similarly, when the main thread allocates a data sharing area for the first source thread, the main thread may divide the entire area in the data sharing module into a plurality of data sharing sub-areas, allocate the first data sharing sub-area for the first source thread, and allocate the second data sharing sub-area for the second source thread.

Therefore, each group of synchronous communication thread groups has the corresponding signal sharing mark and data sharing area, and when the synchronous communication of the thread groups is realized, the information among the thread groups can be ensured not to be disturbed.

Fig. 4 is a flowchart illustrating a communication method of a browser according to an exemplary embodiment, and as shown in fig. 4, the communication method may be applied to a client, and may also be applied to other node devices, including the following steps:

in step S401, the source thread resets the signal sharing flag to the first flag;

in step S402, the source thread sends a message to be processed and identification information of the target thread to the main thread;

in step S403, the main thread allocates a corresponding data sharing area for the source thread, and sends an area identifier of the data sharing area to the source thread;

in step S404, the main thread determines a target thread based on the identification information of the target thread;

in step S405, the main thread sends the region identifier and the message to be processed to the target thread;

in step S406, the target thread processes the message to be processed to obtain feedback information in the second format;

in step S407, the target thread invokes the codec to convert the feedback information in the second format to the feedback information in the first format;

in step S408, the target thread sends feedback information in the first format and the region identifier to the data sharing module;

in step S409, the data sharing module stores the feedback information in the first format to the data sharing area corresponding to the area identifier;

In step S410, the target thread resets the signal sharing flag corresponding to the source thread from the first flag to the second flag;

in step S411, the target thread generates a sharing notification, where the sharing notification is used to trigger generation of preset wake-up information;

in step S412, the source thread receives preset wake-up information; the method comprises the steps that preset wake-up information is used for ending an information waiting state of a source thread at present;

in step S413, the source thread sends an information acquisition request to the data sharing module, where the information acquisition request includes a region identifier;

in step S414, the data sharing module obtains feedback information in the first format stored in the target thread from the data sharing area corresponding to the area identifier;

in step S415, the data sharing module sends feedback information in a first format to the source thread;

in step S416, the source thread invokes the codec to convert the feedback information in the first format to feedback information in the second format.

The specific embodiments related to the steps S4001 to S4016 refer to the specific examples of executing the subject as the source thread and the target thread, and are not repeated here.

Thus, the application sets forth a synchronous communication mode between the source thread and the target thread from both sides of the source thread and the target thread. First, the problem that the source thread and the target thread cannot directly interact is solved through the main thread, and an additionally created service thread is not needed, so that maintenance cost is reduced. Second, the source thread does not execute subsequent operations after sending the message to be processed by the sequential waiting component atom, waits for the reply of the target thread, and when waiting, whether feedback information exists in the data sharing area or not is determined by polling actively initiated by the main thread, but waits for being awakened, so that the resource consumption of the central processor caused by polling can be completely ignored.

Fig. 5 is a block diagram of a communication device, according to an example embodiment. The device has the function of realizing the data processing method in the method embodiment, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. Referring to fig. 5, the apparatus includes a first transmitting module 501, a calling module 502, a first receiving module 503, and an obtaining module 504.

A first sending module 501 configured to perform sending a message to be processed to a target thread through a main thread;

a calling module 502 configured to execute a call order waiting component such that the source thread is in an information waiting state;

a first receiving module 503 configured to perform receiving preset wake-up information; the method comprises the steps that preset wake-up information is used for ending an information waiting state of a source thread at present;

an acquisition module 504 configured to perform acquisition of feedback information of the target thread based on the processing of the pending message from the data sharing area.

The apparatus further comprises:

In some possible embodiments, the acquisition module is configured to perform:

In some possible embodiments, the apparatus further comprises:

It should be noted that, in the apparatus provided in the foregoing embodiment, when implementing the functions thereof, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional allocation may be implemented by different functional modules, that is, the internal structure of the device is divided into different functional modules, so as to implement all or part of the functions described above. In addition, the apparatus and the method embodiments provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the apparatus and the method embodiments are detailed in the method embodiments and are not repeated herein.

Fig. 6 is a block diagram of a communication device, according to an example embodiment. The device has the function of realizing the data processing method in the method embodiment, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. Referring to fig. 6, the apparatus includes a second receiving module 601, a processing module 602, a storage module 603, a flag resetting module 604, and a generating module 605.

A second receiving module 601 configured to execute receiving, by the main thread, a message to be processed sent by the source thread;

the processing module 602 is configured to perform processing on the message to be processed to obtain feedback information;

a storage module 603 configured to perform storing of feedback information into a data sharing area corresponding to the source thread;

a flag reset module 604 configured to perform resetting of a signal sharing flag corresponding to the source thread from a first flag to a second flag;

a generation module 605 configured to perform generation of a sharing notification; the sharing notification is used for triggering generation of preset wake-up information; the preset wake-up information is used for ending the information waiting state of the source thread caused by calling the sequence waiting component.

In some possible embodiments, the storage module is configured to perform:

Fig. 7 is a block diagram illustrating an apparatus 3000 for communication according to an exemplary embodiment. For example, apparatus 3000 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, or the like.

Referring to fig. 7, the apparatus 3000 may include one or more of the following components: a processing component 3002, a memory 3004, a power component 3006, a multimedia component 3008, an audio component 3010, an input/output (I/O) interface 3012, a sensor component 3014, and a communications component 3016.

The processing component 3002 generally controls overall operations of the device 3000, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing assembly 3002 may include one or more processors 3020 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 3002 may include one or more modules to facilitate interactions between the processing component 3002 and other components. For example, the processing component 3002 may include a multimedia module to facilitate interaction between the multimedia component 3008 and the processing component 3002.

The memory 3004 is configured to store various types of data to support operations at the device 3000. Examples of such data include instructions for any application or method operating on device 3000, contact data, phonebook data, messages, pictures, videos, and the like. The memory 3004 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power supply assembly 3006 provides power to the various components of the device 3000. The power supply components 3006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 3000.

The multimedia component 3008 includes a screen between the device 3000 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia assembly 3008 includes a front camera and/or a rear camera. The front camera and/or the rear camera may receive external multimedia data when the device 3000 is in an operational mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 3010 is configured to output and/or input audio signals. For example, audio component 3010 includes a Microphone (MIC) configured to receive external audio signals when device 3000 is in an operational mode, such as a call mode, a recording mode, and a speech recognition mode. The received audio signals may be further stored in the memory 3004 or transmitted via the communication component 3016. In some embodiments, the audio component 3010 further comprises a speaker for outputting audio signals.

The I/O interface 3012 provides an interface between the processing component 3002 and a peripheral interface module, which may be a keyboard, click wheel, button, or the like. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 3014 includes one or more sensors for providing status assessment of various aspects of the device 3000. For example, sensor assembly 3014 may detect the on/off state of device 3000, the relative positioning of the components, such as the display and keypad of device 3000, sensor assembly 3014 may also detect the change in position of device 3000 or a component of device 3000, the presence or absence of user contact with device 3000, the orientation or acceleration/deceleration of device 3000, and the change in temperature of device 3000. The sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 3014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 3014 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 3016 is configured to facilitate wired or wireless communication between the apparatus 3000 and other devices. The device 3000 may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 3016 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 3016 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 3000 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

Embodiments of the present invention also provide a computer readable storage medium that can be disposed in an electronic device to hold at least one instruction or at least one program related to implementing a communication method, the at least one instruction or the at least one program being loaded and executed by the processor to implement the communication method provided by the above-mentioned method embodiments.

In an exemplary embodiment, a storage medium is also provided, such as a memory 3004, comprising instructions executable by the processor 3020 of the apparatus 3000 to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

Embodiments of the present invention also provide a computer-readable storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the method of any one of the first or second aspects of the embodiments of the present disclosure.

Embodiments of the present invention also provide a computer program product comprising a computer program stored in a readable storage medium, from which at least one processor of the computer device reads and executes the computer program, causing the computer device to perform the method of any one of the first or second aspects of the embodiments of the present disclosure.

It should be noted that: the sequence of the embodiments of the present invention is only for description, and does not represent the advantages and disadvantages of the embodiments. And the foregoing description has been directed to specific embodiments of this specification. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments in part.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing description of the preferred embodiments of the invention is not intended to limit the invention to the precise form disclosed, and any such modifications, equivalents, and alternatives falling within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

1. A method of communication, comprising:

sending a message to be processed to a target thread through a main thread;

receiving preset wake-up information; the preset wake-up information is used for ending the information waiting state of the source thread;

2. The communication method according to claim 1, wherein the preset wake-up information is generated by triggering after the target thread stores the feedback information in the data sharing area and resets a signal sharing flag corresponding to the source thread from a first flag to a second flag; wherein the first flag characterizes that the source thread is in an information waiting state; the second identifier characterizes that the source thread is not in an information waiting state;

Before the message to be processed is sent to the target thread through the main thread, the method further comprises the following steps:

the signal sharing flag is reset to the first flag.

3. The communication method according to claim 1, wherein the obtaining feedback information obtained by the target thread based on the processing of the pending message from the data sharing area includes:

determining an area identifier of a data sharing area corresponding to the source thread;

sending an information acquisition request to a data sharing module; the information acquisition request comprises the area identifier;

receiving the feedback information returned by the data sharing module; and the feedback information is information read by the data sharing module from the data sharing area corresponding to the area identifier.

4. The communication method according to claim 1, wherein after the obtaining feedback information obtained by the target thread based on the processing of the pending message from the data sharing area, further comprises:

invoking a codec to convert the feedback information in the first format in the data sharing area to the feedback information in the second format; and the second format is a data format corresponding to the target thread.

5. The communication method according to any one of claims 1 to 4, wherein the source thread, the main thread, and the target thread are threads in a browser.

6. A communication method, comprising:

processing the message to be processed to obtain feedback information;

storing the feedback information into a data sharing area corresponding to the source thread, and resetting a signal sharing mark corresponding to the source thread from a first mark to a second mark;

7. The communication method according to claim 6, wherein storing the feedback information in the data sharing area corresponding to the source thread includes:

8. A communication device, comprising:

the first receiving module is configured to execute receiving preset wake-up information; the preset wake-up information is used for ending the information waiting state of the source thread;

and the acquisition module is configured to acquire feedback information corresponding to the message to be processed from the data sharing area.

9. A communication device, comprising:

the processing module is configured to execute processing on the message to be processed to obtain feedback information;

the storage module is configured to store the feedback information to a data sharing area corresponding to the source thread;

10. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the communication method of any one of claims 1 to 5 or 6 to 7.

11. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the communication method of any one of claims 1 to 5 or 6 to 7.