CN102279774A - Method and device for realizing multi-thread message interaction by using synchronous function calling mechanism - Google Patents
Method and device for realizing multi-thread message interaction by using synchronous function calling mechanism Download PDFInfo
- Publication number
- CN102279774A CN102279774A CN 201110241269 CN201110241269A CN102279774A CN 102279774 A CN102279774 A CN 102279774A CN 201110241269 CN201110241269 CN 201110241269 CN 201110241269 A CN201110241269 A CN 201110241269A CN 102279774 A CN102279774 A CN 102279774A
- Authority
- CN
- China
- Prior art keywords
- task
- response data
- function interface
- caller
- nonproductive
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and a device for realizing multi-thread message interaction by using a synchronous function calling mechanism. The method comprises the following steps that: a caller task calls a function interface and writes request parameters; the function interface locks an interface use right and sets the state of the caller task as a waiting state; the function interface sends the request parameters to a request processing task through an auxiliary task and reads response data which is fed back to the auxiliary task by the request processing task; and the function interface sets the state of the caller task as an idle state, releases the interface use right and returns the length of the read response data to the caller task. By the method and the device, a logic processing flow in a program development process is greatly simplified, and the problem of complicated logic processing flow of an asynchronous message interaction mechanism is solved.
Description
Technical field
The present invention relates to field of computer technology, relate in particular to a kind of method and apparatus that utilizes synchronization function call mechanism to realize the multithreading interacting message.
Background technology
Multithreading exploitation widely-used makes the powerful, flexible of computing machine, the concurrent many-sided ability of system and the efficient of also can improving of multithreading.Wherein the most general mode of communication between the multithreading is exactly an interacting message.
When interacting message offers convenience for the developer, also cause the logic flow of program complicated unusually.A processing procedure may need repeatedly interacting message, because the uncontinuity of message, processing procedure is easy to be interrupted, so just must write down a large amount of states handles various possible interference to the developer.When the interacting message of a thread and another one thread was man-to-man request and response, the thread of request service was the processing sequence of one " processing "-" wait "-" processing ".The process of " wait " may be interrupted, so the developer must be concerned about current treatment state.So there is the drawback of logical process flow process complexity in existing asynchronous message interaction mechanism.
Summary of the invention
The invention provides a kind of method and apparatus that utilizes synchronization function call mechanism to realize the multithreading interacting message, in order to solve asynchronous message interaction mechanism logical process flow process complicated problems in the prior art.
In order to solve the problems of the technologies described above, the technical solution used in the present invention is as follows:
On the one hand, the invention provides a kind of method of utilizing synchronization function call mechanism to realize the multithreading interacting message, described method comprises:
Caller task call function interface writes required parameter;
The described function interface lock port right to use, and the state that described caller task is set is a waiting status;
Described function interface is sent to the Request Processing task by nonproductive task with the described request parameter, and reads the response data that the described request Processing tasks feeds back to described nonproductive task;
The state that described function interface is provided with described caller task is an idle condition, discharges the described interface right to use, and returns the length of the described response data that reads to described caller task.
Preferably, described function interface adopts the mode of obtaining the mutex amount that is pre-created to realize the lock port right to use, adopts the mode that discharges described mutex amount to realize the realizing interface right to use.
Further, described function interface is sent to the Request Processing task by described nonproductive task with the described request parameter, and reads the response data that the described request Processing tasks feeds back to described nonproductive task, specifically comprises:
Described function interface is sent to described nonproductive task with the described request parameter, and sets the stand-by period, enters waiting status;
Described nonproductive task is sent to the Request Processing task of appointment in the described request parameter with the described request parameter, and the state that nonproductive task is set is a waiting status;
Described nonproductive task receives the response data of described request Processing tasks feedback, deposits described response data in default buffer zone, and the state that described nonproductive task is set is an idle condition, and notifies described function interface;
Described function interface receives described notice, reads the response data in the described buffer zone.
Wherein, described function interface is set the stand-by period, and the preferred implementation that enters waiting status comprises: described function interface obtains the semaphore that is pre-created, and the stand-by period of the described semaphore that obtains is set; The initial value of the described semaphore that is pre-created is 0;
Described nonproductive task notifies the preferred implementation of described function interface to comprise: described nonproductive task discharges described semaphore;
The preferred implementation that described function interface receives described notice comprises: described function interface successfully obtains described semaphore.
On the other hand, the present invention also provides a kind of device that utilizes synchronization function call mechanism to realize the multithreading interacting message, and described device comprises: caller TU task unit, function interface, nonproductive task unit and Request Processing TU task unit;
Described caller TU task unit is used to call described function interface, writes required parameter; And receive the length of the response data that described function interface returns;
Described function interface is used for based on the calling of described caller TU task unit, the lock port right to use, and the state that described caller TU task unit is set is a waiting status; And the described request parameter is sent to the Request Processing TU task unit, and read the response data that described request Processing tasks unit feeds back to described nonproductive task unit by described nonproductive task unit; Then, the state that described caller TU task unit is set is an idle condition, the realizing interface right to use, and return the length of the described response data that reads to described caller TU task unit.
Compared with prior art, beneficial effect of the present invention is as follows:
Adopt the method for the invention and device, reach the purpose that the asynchronous message communication mechanism is converted to function call mechanism, logical process flow process in the performance history of can simplifying procedures has widely solved asynchronous message interaction mechanism logical process flow process complicated problems.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do one to the accompanying drawing of required use in embodiment or the description of the Prior Art below introduces simply, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is a kind of process flow diagram that utilizes synchronization function call mechanism to realize the method for multithreading interacting message provided by the invention;
Fig. 2 realizes the synoptic diagram of multithreading interacting message for the synchronization function call mechanism of utilizing that the embodiment of the invention provides;
Fig. 3 is a kind of structural representation that utilizes synchronization function call mechanism to realize the device of multithreading interacting message provided by the invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
The flow process complicated situation that the present invention causes in order to limit asynchronous message mechanism to greatest extent, on the basis of message mechanism, a kind of method and apparatus that utilizes synchronization function call mechanism to realize the multithreading interacting message is proposed, described method is a synchronization function call mechanism with the asynchronous message mechanism transformation, has simplified the logical process flow process in the program development process widely.
As shown in Figure 1, the invention provides a kind of method of utilizing synchronization function call mechanism to realize the multithreading interacting message, described method comprises:
Step S101, caller task call function interface write required parameter;
Step S102, the described function interface lock port right to use, and the state that the caller task is set is a waiting status;
Wherein, function interface is realized that the usufructuary mode of lock port is preferred but is not limited to: adopt the mutex amount mode that is pre-created of obtaining.
Step S103, described function interface are sent to the Request Processing task by nonproductive task with the described request parameter, and read the response data that the described request Processing tasks feeds back to described nonproductive task;
This step specifically comprises:
(1) described function interface is sent to described nonproductive task with the described request parameter, and sets the stand-by period, enters waiting status;
(2) described nonproductive task is sent to the Request Processing task of appointment in the described request parameter with the described request parameter, and the state that nonproductive task is set is a waiting status;
(3) described nonproductive task receives the response data of described request Processing tasks feedback, deposits described response data in default buffer zone, and the state that described nonproductive task is set is an idle condition, and notifies described function interface;
Wherein, described nonproductive task preferably, judges whether the state of described caller task is waiting status, if then deposit described response data in default buffer zone after receiving the response data of described request Processing tasks feedback; Otherwise, directly abandon described response data.
(4) described function interface receives described notice, reads the response data in the described buffer zone.
Wherein, the mode of nonproductive task notification function interface is preferred but be not limited to: the nonproductive task release semaphore; It is preferred but be not limited to that function interface receives the mode of described notice: function interface successfully obtains described semaphore.
Continue step S103, have:
The state that step S104, described function interface are provided with described caller task is an idle condition, discharges the described interface right to use, and returns the length of the described response data that reads to described caller task.
Preferably, described function interface adopts the mode that discharges the mutex amount to realize the realizing interface right to use.
Provide preferred embodiment of the present invention according to Fig. 2 below, and, further provide ins and outs of the present invention in conjunction with description to embodiment.
The embodiment of the invention provides a kind of method of utilizing synchronization function call mechanism to realize the multithreading interacting message, described method relates to following a few part: nonproductive task, semaphore, mutex amount, caller task status, nonproductive task state, data buffer, function interface, wherein:
Nonproductive task as the media of caller task and Request Processing task, is responsible for giving the Request Processing task with the forwards of caller task, receives the response data of Request Processing task, and deposits response data in data buffer;
Semaphore is used for controlling the wait and the execution of caller task;
The mutex amount is used for controlling the exclusive reference to synchronization function call mechanism;
The caller task status is used for writing down the caller task and whether is in waiting status;
Whether the nonproductive task state is used for writing down nonproductive task in the response of waiting for the Request Processing task, and the ID of Request Processing task;
The data buffer is used for keeping in the response data that the Request Processing task is returned, and the caller task is visited the response data that this buffer zone obtains the Request Processing task by function interface.
Function interface uses for the caller task, and the caller task is passed to nonproductive task by this interface with request message ID, message data and Request Processing task ID, and obtains response data by this interface.
Based on the functional description of each part mentioned above, provide the embodiment of the invention in conjunction with Fig. 2 and utilize synchronization function call mechanism to realize the concrete operations flow process of the method for multithreading interacting message, comprising:
Initialization procedure, this initialization procedure mainly comprises:
(1) starts nonproductive task;
(2) create semaphore, and signalization amount initial value is 0;
(3) create the mutex amount;
(4) initialization caller task status is an idle condition;
(5) initialization nonproductive task state is an idle condition;
(6) the initialization data buffer zone is empty.
Workflow specifically comprises:
Step 1, caller task call function interface, input required parameter; The described request parameter comprises: message id, message data and Request Processing task ID;
Step 2, function interface are obtained (Get) mutex amount;
Step 3, the function interface data in the buffer zone that clear data, it is waiting status that the caller task status is set;
Step 4, function interface sends to nonproductive task with the ginseng (comprising message id, message data and Request Processing task ID) of going into of caller task;
Step 5, the stand-by period of function interface signalization amount Get, the Get semaphore enters waiting status then;
Adopt the mode of Get semaphore to enter waiting status in this step, be because the initial value of semaphore is 0, if nonproductive task do not discharge (put) semaphore, then function interface can't successful Get semaphore, and then makes function interface enter Get semaphore waiting status.And in the step 8, behind the nonproductive task put semaphore, this moment, the value of semaphore was 1, and function interface can the Get semaphore, and then carries out follow-up associative operation operation.
Step 6 after nonproductive task is received required parameter, is transmitted to the Request Processing task of Request Processing task ID correspondence with message id in the required parameter and message data, and the nonproductive task state is set is waiting status;
Step 7, the Request Processing task is handled after receiving required parameter, and sends response data to nonproductive task;
After step 8, nonproductive task are received the response data of Request Processing task, judge whether the caller task status is waiting status, if, then response data being buffered in the data buffer, it is idle condition that the nonproductive task state is set, Put semaphore, execution in step 9; Otherwise, abandon response data.
Step 9, function interface judge whether the Get semaphore is successful, if read response data from the data buffer, and store out the space of ginseng pointed into, execution in step 10; Otherwise, do not read response data from the data buffer, directly change step 10, at this moment, the length of the response data of returning in the step 10 is 0.
It is idle condition that step 10, function interface are provided with the caller task status, and Put mutex amount, and returns the actual response data length that reads to the caller task, finishes.
Need to prove, function interface is after the stand-by period that step 6 is provided with, if the nonproductive task state still is in waiting status (expression Request Processing task is not to nonproductive task feedback response data), then function interface finishes waiting status, directly execution in step 10; At this moment, the length of the response data of returning in the step 10 is 0.
As shown in Figure 3, the present invention also provides a kind of device that utilizes synchronization function call mechanism to realize the multithreading interacting message, and described device comprises: caller TU task unit 310, function interface 320, nonproductive task unit 330 and Request Processing TU task unit 340;
Caller TU task unit 310 is used for call function interface 320, writes required parameter; And the length of the response data returned of receiver function interface 320;
Wherein, function interface 310 with the concrete reciprocal process of nonproductive task unit 330 is:
Provide a preferred embodiment below, and pass through the description of this preferred embodiment, further provide the ins and outs of device of the present invention.
The described device of the embodiment of the invention comprises: caller TU task unit, function interface, nonproductive task unit and Request Processing TU task unit;
Described caller TU task unit comprises:
Call subelement, be used for the call function interface, write required parameter;
The result obtains subelement, is used for the length of the response data that the receiver function interface returns;
Described function interface comprises: state is provided with subelement, and required parameter issues subelement, data read subelement and data feedback subelement, wherein:
State is provided with subelement, be used for obtaining the mutex amount based on the calling of described caller TU task unit, and the state that described caller TU task unit is set is a waiting status;
Required parameter issues subelement, is used for the described request parameter is sent to described nonproductive task, and the Get stand-by period of signalization amount, the Get semaphore enters waiting status; Wherein the initial value of semaphore is 0.
Wherein, required parameter issues subelement in the stand-by period of the Get semaphore that is provided with when overtime, if the state of nonproductive task unit still be a waiting status, then directly trigger data is fed back subelement;
The data read subelement is used for Get semaphore success, reads the nonproductive task unit and deposits response data in the buffer zone, trigger data feedback subelement in;
Data feedbacks subelement, being used to the state that calls, the state that subelement is provided with described caller TU task unit is set is idle condition, Put mutex amount, and return the length of the described response data that reads to described caller TU task unit.
Described nonproductive task unit comprises:
Required parameter is transmitted subelement, is used for required parameter is sent to the Request Processing TU task unit of required parameter appointment, and the state that the nonproductive task unit is set is a waiting status;
Response data is obtained subelement, is used to receive the response data of described request Processing tasks unit feedback, deposits described response data in default buffer zone, and the state that described nonproductive task unit is set is an idle condition, and the Put semaphore;
Wherein, response data is obtained subelement after the response data that receives Request Processing TU task unit feedback, preferably, judges whether the state of described caller TU task unit is waiting status, if then deposit described response data in default buffer zone; Otherwise, directly abandon described response data.
The Request Processing TU task unit comprises:
Parameter receives subelement, is used to receive the required parameter that the nonproductive task unit sends;
Handle subelement, be used for handling based on described request parameter message data, and the result that will handle in response data feed back to described nonproductive task unit.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (10)
1. one kind is utilized the machine-processed method that realizes the multithreading interacting message of synchronization function call, it is characterized in that described method comprises:
Caller task call function interface writes required parameter;
The described function interface lock port right to use, and the state that described caller task is set is a waiting status;
Described function interface is sent to the Request Processing task by nonproductive task with the described request parameter, and reads the response data that the described request Processing tasks feeds back to described nonproductive task;
The state that described function interface is provided with described caller task is an idle condition, discharges the described interface right to use, and returns the length of the described response data that reads to described caller task.
2. the method for claim 1 is characterized in that,
Described function interface adopts the mode of obtaining the mutex amount that is pre-created to realize the lock port right to use, adopts the mode that discharges described mutex amount to realize the realizing interface right to use.
3. method as claimed in claim 1 or 2, it is characterized in that, described function interface is sent to the Request Processing task by described nonproductive task with the described request parameter, and reads the response data that the described request Processing tasks feeds back to described nonproductive task, specifically comprises:
Described function interface is sent to described nonproductive task with the described request parameter, and sets the stand-by period, enters waiting status;
Described nonproductive task is sent to the Request Processing task of appointment in the described request parameter with the described request parameter, and the state that nonproductive task is set is a waiting status;
Described nonproductive task receives the response data of described request Processing tasks feedback, deposits described response data in default buffer zone, and the state that described nonproductive task is set is an idle condition, and notifies described function interface;
Described function interface receives described notice, reads the response data in the described buffer zone.
4. want 3 described methods as right, it is characterized in that,
Described function interface is set the stand-by period, and the mode that enters waiting status comprises: described function interface obtains the semaphore that is pre-created, and the stand-by period of the described semaphore that obtains is set; The initial value of the described semaphore that is pre-created is 0;
Described nonproductive task notifies the mode of described function interface to comprise: described nonproductive task discharges described semaphore;
The mode that described function interface receives described notice is: described function interface successfully obtains described semaphore.
5. method as claimed in claim 3 is characterized in that, also comprises:
Described function interface if determine that the state of described nonproductive task still is a waiting status, then directly discharges the described interface right to use after the described stand-by period finishes, and returns the length of the response data that reads to described caller task; The length of the response data of wherein, returning is 0.
6. method as claimed in claim 3 is characterized in that, also comprises after the response data of described nonproductive task reception described request Processing tasks feedback:
Described nonproductive task judges whether the state of described caller task is waiting status, if then deposit described response data in default buffer zone; Otherwise, directly abandon described response data.
7. a device that utilizes synchronization function call mechanism to realize the multithreading interacting message is characterized in that, comprising: caller TU task unit, function interface, nonproductive task unit and Request Processing TU task unit;
Described caller TU task unit is used to call described function interface, writes required parameter; And receive the length of the response data that described function interface returns;
Described function interface is used for based on the calling of described caller TU task unit, the lock port right to use, and the state that described caller TU task unit is set is a waiting status; And the described request parameter is sent to the Request Processing TU task unit, and read the response data that described request Processing tasks unit feeds back to described nonproductive task unit by described nonproductive task unit; Then, the state that described caller TU task unit is set is an idle condition, the realizing interface right to use, and return the length of the described response data that reads to described caller TU task unit.
8. device as claimed in claim 7 is characterized in that,
Described function interface adopts the mode of obtaining the mutex amount that is pre-created to realize the lock port right to use; Adopt the mode that discharges described mutex amount to realize the realizing interface right to use.
9. as claim 7 or 8 described devices, it is characterized in that,
Described function interface specifically comprises:
State is provided with subelement, is used for based on the calling of described caller TU task unit, and the lock port right to use, the state that described caller TU task unit is set is a waiting status;
Required parameter issues subelement, is used for the described request parameter is sent to described nonproductive task unit, and sets the stand-by period, enters waiting status;
The data read subelement is used to receive the notice that described nonproductive task unit sends, and reads the response data in the buffer zone;
Data feedbacks subelement, after being used to call described state and state that subelement is provided with described caller TU task unit is set is idle condition, the realizing interface right to use, and return the length of the described response data that reads to described caller TU task unit;
Described nonproductive task unit specifically comprises:
Required parameter is transmitted subelement, be used for the required parameter that described function interface sends is forwarded to the Request Processing TU task unit of described request parameter appointment, and the state that the nonproductive task unit is set is a waiting status;
Response data is obtained subelement, is used to receive the response data of described request Processing tasks unit feedback, deposits described response data in default buffer zone, and the state that described nonproductive task unit is set is an idle condition, and notifies described function interface.
10. device as claimed in claim 9 is characterized in that,
The described request parameter issues subelement and specifically is used for, and the described request parameter is sent to described nonproductive task unit, and the Get stand-by period of signalization amount, and the Get semaphore enters waiting status; The initial value of described semaphore is 0;
Described response data is obtained subelement and specifically is used for, and receives the response data of described request Processing tasks unit feedback, deposits described response data in default buffer zone, and the state that described nonproductive task unit is set is an idle condition, and discharges described semaphore;
Described data read subelement specifically is used for, and successfully obtains described semaphore, reads the response data in the described buffer zone.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110241269 CN102279774A (en) | 2011-08-22 | 2011-08-22 | Method and device for realizing multi-thread message interaction by using synchronous function calling mechanism |
| PCT/CN2011/084660 WO2012152029A1 (en) | 2011-08-22 | 2011-12-26 | Method and device for realizing multi-thread message interaction using synchronous function call mechanism |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110241269 CN102279774A (en) | 2011-08-22 | 2011-08-22 | Method and device for realizing multi-thread message interaction by using synchronous function calling mechanism |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102279774A true CN102279774A (en) | 2011-12-14 |
Family
ID=45105236
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110241269 Pending CN102279774A (en) | 2011-08-22 | 2011-08-22 | Method and device for realizing multi-thread message interaction by using synchronous function calling mechanism |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102279774A (en) |
| WO (1) | WO2012152029A1 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012152029A1 (en) * | 2011-08-22 | 2012-11-15 | 中兴通讯股份有限公司 | Method and device for realizing multi-thread message interaction using synchronous function call mechanism |
| CN104407917A (en) * | 2014-11-13 | 2015-03-11 | 中国建设银行股份有限公司 | JMS (Java messaging service)-based transaction processing method and JMS-based transaction processing device |
| CN105930219A (en) * | 2016-04-22 | 2016-09-07 | 浙江工业大学 | Self-defined multi-thread management control communication method |
| CN107770258A (en) * | 2017-10-10 | 2018-03-06 | 许继电气股份有限公司 | A kind of asynchronous call turns the implementation method of synchronization call |
| CN107766164A (en) * | 2017-11-17 | 2018-03-06 | 深圳市泉眼网络科技有限公司 | Data calling method and device |
| CN108985629A (en) * | 2018-07-17 | 2018-12-11 | 阿里巴巴集团控股有限公司 | The execution method, apparatus and server of service node in business chain |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101097527B (en) * | 2006-06-27 | 2011-11-30 | 中国银联股份有限公司 | Flowpath scheduling method and system of application progress |
| CN101504622B (en) * | 2009-03-25 | 2011-01-05 | 北京飞天诚信科技有限公司 | Method and device for information interaction between threads |
| CN102279774A (en) * | 2011-08-22 | 2011-12-14 | 中兴通讯股份有限公司 | Method and device for realizing multi-thread message interaction by using synchronous function calling mechanism |
-
2011
- 2011-08-22 CN CN 201110241269 patent/CN102279774A/en active Pending
- 2011-12-26 WO PCT/CN2011/084660 patent/WO2012152029A1/en active Application Filing
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012152029A1 (en) * | 2011-08-22 | 2012-11-15 | 中兴通讯股份有限公司 | Method and device for realizing multi-thread message interaction using synchronous function call mechanism |
| CN104407917A (en) * | 2014-11-13 | 2015-03-11 | 中国建设银行股份有限公司 | JMS (Java messaging service)-based transaction processing method and JMS-based transaction processing device |
| CN104407917B (en) * | 2014-11-13 | 2018-10-16 | 中国建设银行股份有限公司 | A kind of transaction processing method and device based on JMS |
| CN105930219A (en) * | 2016-04-22 | 2016-09-07 | 浙江工业大学 | Self-defined multi-thread management control communication method |
| CN105930219B (en) * | 2016-04-22 | 2019-02-05 | 浙江工业大学 | A kind of communication means of customized multithreading control |
| CN107770258A (en) * | 2017-10-10 | 2018-03-06 | 许继电气股份有限公司 | A kind of asynchronous call turns the implementation method of synchronization call |
| CN107766164A (en) * | 2017-11-17 | 2018-03-06 | 深圳市泉眼网络科技有限公司 | Data calling method and device |
| CN108985629A (en) * | 2018-07-17 | 2018-12-11 | 阿里巴巴集团控股有限公司 | The execution method, apparatus and server of service node in business chain |
| CN108985629B (en) * | 2018-07-17 | 2022-04-08 | 创新先进技术有限公司 | Method and device for executing service node in service chain and server |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012152029A1 (en) | 2012-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102279774A (en) | Method and device for realizing multi-thread message interaction by using synchronous function calling mechanism | |
| CN110806923B (en) | Parallel processing method and device for block chain tasks, electronic equipment and medium | |
| CN103425225B (en) | Application programmer in portable data device operating system and operation method thereof | |
| US8438572B2 (en) | Task scheduling method and apparatus | |
| CN101859260B (en) | Timer management device and management method for operating system | |
| US9886077B2 (en) | Processor management via thread status | |
| CN105389209A (en) | Asynchronous batch task processing method and system | |
| CN101365999B (en) | Transmit completion event batching | |
| CN101221541B (en) | Programmable communication controller for SOC and its programming model | |
| CN102096603B (en) | Task decomposition control method in MapReduce system and scheduling node equipment | |
| CN106844017A (en) | The method and apparatus that event is processed for Website server | |
| CN103473138A (en) | Multi-tasking queue scheduling method based on thread pool | |
| JP2017509059A (en) | Synchronize interrupt handling to reduce power consumption | |
| WO2013041366A1 (en) | Concurrent processing of queued messages | |
| JP2007226799A (en) | Apparatus for forcibly terminating thread blocked on input/output operation and method for the same | |
| CN103279331A (en) | Multi-task concurrent processing method and device for Android system | |
| CN105579963B (en) | Task Processing Unit, electronic equipment and method | |
| WO2014088726A1 (en) | Memory based semaphores | |
| TW200825923A (en) | Task processing device | |
| US11775309B2 (en) | Exception stack handling method, system, electronic device and storage medium | |
| CN107391274A (en) | The processing method and processing device of deferred information | |
| CN117539598A (en) | Task processing method and device, electronic equipment and storage medium | |
| CN101349975B (en) | Method for implementing interrupt bottom semi-section mechanism in embedded operation system | |
| CN100432938C (en) | System and method for implicit synchronization of message-queue-based user interface with an automatic code | |
| CN104407917A (en) | JMS (Java messaging service)-based transaction processing method and JMS-based transaction processing device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20111214 |