WO2016029790A1

WO2016029790A1 - Data transmission method and device

Info

Publication number: WO2016029790A1
Application number: PCT/CN2015/086479
Authority: WO
Inventors: 陈非; 王超; 朱超
Original assignee: 北京奇虎科技有限公司; 奇智软件（北京）有限公司
Priority date: 2014-08-28
Filing date: 2015-08-10
Publication date: 2016-03-03
Also published as: CN105373420B; CN105373420A

Abstract

A data transmission method and device. The method comprises: middleware allocates a first thread to a client and a database, such that the client and the database transmit data via the first thread (S101); the middleware releases the first thread after the first thread finishes transmitting the data (S102); a networking event of the client and the database is monitored (S103); and after a specified networking event is monitored, a second thread is reallocated to the client and the database (S104). Thus, limited thread resources of middleware are not only saved for providing data services to the data transmission between a client and a database, but also the use efficiency of a thread is effectively improved.

Description

Data transmission method and device

Technical field

The present invention relates to the field of computer technologies, and in particular, to a data transmission method and apparatus.

Background technique

With the development of information technology, users can access the Internet through the client to obtain all kinds of data required. All kinds of data in the Internet are stored in different databases (such as MySQL database, Oracle database, etc.), which means that users access the corresponding database through the network to obtain the required data.

In the prior art, a middleware (a data transfer device) is usually disposed between the database and the client to manage the connection interaction between the database and a large number of clients, and provide data services for each client, that is, the client. The data is transmitted between the terminal and the database through middleware.

The middleware contains multiple threads that provide data services. Each thread is assigned to a client to provide data services for the client. When a thread receives a client's data request, the thread requests the data. Forward to the database and wait for the result of the database processing the data request, after which the thread feeds the result back to the client that issued the data request.

However, the database will receive a large number of data requests, and the number of data requests processed in parallel is limited. That is, after the thread forwards the data request to the database, the data request may be in the waiting queue, and the database processes the data request itself. It takes a certain amount of time (a few seconds to tens of seconds), and it is not possible to generate processing results immediately. During this time, the thread will remain in a wait state (in this state, the thread cannot process other services) until receiving After the result of the processing of the feedback to the database, the result can be forwarded to the client, and then the data service can be provided to other clients or other services can be processed. Therefore, the waste of the thread resources is caused, and the thread utilization is also low.

Summary of the invention

In view of the above problems, the present invention has been made in order to provide a data transmission method and apparatus that overcomes the above problems or at least partially solves the above problems, and can effectively save the existing client and database in the process of data communication. Threads that improve thread utilization.

According to an aspect of the present invention, a data transmission method is provided for data transmission between a client and a server through an intermediate device, the method comprising:

The middleware allocates a first thread to the client and the database, so that the client and the database transmit data through the first thread;

The middleware releases the first thread after the first thread completes the transmission of the data;

Listening to network events of the client and database;

After listening to the specified network event, re-allocate the second thread to the client and database.

According to another aspect of the present invention, a data transmission apparatus is further provided for data transmission between a client and a server, the apparatus comprising: a first distribution module, a release module, a monitoring module, and a second distribution module, among them,

The first allocating module is configured to allocate a first thread to the client and the database, so that the client and the database transmit data through the first thread;

The releasing module is configured to release the first thread after the first thread completes the transmission of the data;

The monitoring module is configured to listen to network events of the client and the database;

The second allocation module is configured to re-allocate the second thread to the client and the database after listening to the specified network event.

According to still another aspect of the present invention, a computer program is provided, comprising computer readable code that, when executed on a computing device, causes the computing device to perform data transmission according to the above method.

According to still another aspect of the present invention, a computer readable medium storing the above computer program is provided.

The beneficial effects of the invention are:

According to the thread management method provided by the present invention, after the middleware allocates the first thread to send data to the client or the database, the first thread is released, and the first thread is turned into an idle state for allocation to other clients or processing. Other services, at the same time, the middleware will re-allocate the second thread for the client and the database to transfer data after the specified network event occurs between the client and the database, thereby saving the limited amount of middleware. Thread resources provide data services for data transfer between the client and the database, and also effectively improve thread utilization.

The above description is only an overview of the technical solutions of the present invention, and the above-described and other objects, features and advantages of the present invention can be more clearly understood. Specific embodiments of the invention are set forth below.

DRAWINGS

Various other advantages and benefits will become apparent to those skilled in the art from a The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

1 is a schematic flow chart of a data transmission method according to an embodiment of the present invention;

2 to 5 are schematic diagrams showing a connection structure of a client, a middleware, and a database in an actual application scenario according to an embodiment of the present invention;

6 is a schematic structural diagram of a data transmission apparatus according to an embodiment of the present invention;

Figure 7 is a schematic block diagram showing a computing device for performing a data transmission method in accordance with the present invention;

Fig. 8 schematically shows a storage unit for holding or carrying program code implementing the data transmission method according to the present invention.

detailed description

The invention is further described below in conjunction with the drawings and specific embodiments.

FIG. 1 is a data transmission method according to an embodiment of the present invention. In this embodiment, a client and a server are connected through a middleware, and the method may include the following steps:

S101: The middleware allocates a first thread to the client and the database, so that the client and the database transmit data through the first thread.

S102: The middleware releases the first thread after the first thread completes the transmission of the data.

S103: Monitor network events of the client and the database.

S104: Re-allocate the second thread to the client and the database after listening to the specified network event.

As can be seen from the above, in this embodiment, after the middleware allocates the first thread to send data to the client or the database, the first thread is released, and the first thread is turned into an idle state for allocation to other clients or Processing other services, at the same time, the middleware will re-allocate the second thread for data transfer between the client and the database after listening to the specified network event between the client and the database, thereby saving not only the middleware. The thread resource provides data services for data transfer between the client and the database, and also effectively improves the utilization of the thread.

According to an embodiment of the present invention, the data includes: first data sent by the client to the database, or second data sent by the database to the client. among them, The first data sent by the client may specifically be different types of data requests, such as: reading data requests and writing data requests, or file data uploaded to the database, backup data, and the like. The second data sent by the database may specifically be update data, file data, backup data, and the like pushed to the client.

The first data and the second data are transmitted by the first thread allocated by the middleware. In an actual application, for the database, after the database receives the first data, the first data needs to be processed. In a certain period of time, in addition, the same database may connect multiple clients at the same time through the middleware. After the data transmission, the database will process multiple data sent by multiple clients at the same time, and the database is limited by the hardware conditions of the database itself. At the same time, the limited amount of data processed in parallel causes the data to wait in the database. For the client, after the second data is received by the client, the processing of the second data also takes a certain time, which causes the second data to enter the waiting state in the client.

Therefore, in the above step S102, in order to improve the data transmission efficiency, once the middleware monitors that the allocated first thread has sent the data to the database or the client, the middleware immediately releases the first thread, so that the middle thread The first thread is idle to handle other data traffic.

According to an embodiment of the present invention, after the middleware sends the first data to the database, or sends the second data to the client, the client or the database processes the received data, and after processing the data, A response is generated and the corresponding response data is sent, ie the corresponding network event occurs at the client or the database. In this way, the middleware needs to monitor the network events of the client and the database after completing the transmission of the first data and the second data.

Of course, according to an embodiment of the present invention, a plurality of network events occur in the client and the database, and not all network events are related to the middleware allocation thread. For example, the network event that the client establishes a connection to the database is not caused by The middleware allocates threads to complete the establishment of the connection. Therefore, in the foregoing step S103, the middleware needs to listen to the specified network event related to the data transmission, where the specified network event includes: the database generates a network event of the first response data according to the first data, or The client generates a network event of the second response data according to the second data.

Specifically, when a network event in which the database generates the first response data according to the first data occurs, it indicates that the database has processed and generated a response after receiving the first data sent by the client. For example, the client issues a download request (ie, the first data), and the first thread allocated by the middleware sends the download request to the database, and the database receives the download request. After that, the data corresponding to the download request is retrieved, and the data is the response made by the database according to the download request, that is, the first response data.

Similarly, when the network event of the second response data generated by the client according to the second data occurs, it indicates that the client processes and generates a response after receiving the second data sent by the database, and the client generates a response. The data is the second response data.

The first response data may be, for example, data corresponding to the first data generated by the database according to the first data sent by the client, such as: download data corresponding to the download request, query result data corresponding to the query request, and the like. . The second response data may be, for example, data corresponding to the second data generated by the client according to the second data sent by the database, such as authentication data fed back by the client according to the security instruction data of the database.

According to an embodiment of the present invention, for step S104, the method may include: when listening to the network event that the database generates the first response data according to the first data, the middleware is re-initiated as the client And the database allocates a second thread, so that the database transmits the first response data to the client by the redistributed second thread, or when the client is monitored to generate the according to the second data When the second response data, the middleware re-allocates the second thread to the client and the database, and causes the client to transmit the second response data to the database through the redistributed second thread.

According to another embodiment of the present invention, when a client or a database processes data at the same time (for example, the database receives data sent by multiple clients for processing, or the client processes data sent by multiple databases), a storage space appears. (eg, cache) saturation, in this case, the client or database can no longer receive externally sent data, but need to wait for the current data processing to complete, then receive the data, then, if on the client or When the storage space of the database is saturated, the middleware sends the first response data to the client or sends the second response data to the database, which will inevitably lead to the transmission failure. Therefore, the middleware also needs to monitor the storage space of the client or the database. .

Therefore, the specified network event in the embodiment of the present invention includes: in addition to the network event that the database generates the first response data according to the first data and the network event that the client generates the second response data according to the second data, the method further includes: The client or database storage space is not saturated with network events. In this case, for the step S104, the method may include: when listening to the network event that the database generates the first response data according to the first data, and the storage space of the client is not saturated When the network event occurs, the middleware re-allocates the second thread to the client and the database, so that the database transmits the first response data to the client through the redistributed second thread, or when listening The customer And generating, by the terminal, a network event of the second response data according to the second data, and a network event in which the storage space of the database is not saturated, the middleware re-allocating the second thread to the client and the database, so that the The client transmits the second response data to the database through the reassigned second thread.

According to an embodiment of the present invention, the re-allocating the second thread to the client and the database in step S104 specifically includes: using the first thread used by the client and the database to transmit the data as the second thread, Reassigned to the client and database.

2 to 5, the specific practical application of the data transmission method according to the present invention is as follows:

2 to 5, in the actual application, the client, middleware and database connection architecture, wherein the database is a MySQL database, the client C1 ~ C4 are simultaneously connected to the MySQL database through the middleware, the client C1 ~ The data between C4 and the MySQL database is transmitted through the thread allocated by the middleware, and the connection between the client C1 and C4 and the middleware and the middleware and the MySQL database is based on the TCP protocol. It should be noted here that the four clients C1 to C4 in the figure respectively perform data transmission with the MySQL database according to the numbering sequence, and the dotted line indicates that the connection has been established, but no data transmission is performed.

In Figure 2, client C1 wants to query the data in the MySQL database, including the steps:

Step 1: The middleware allocates a thread TR1 to the client C1 and the MySQL database, and transmits a query request sent by the client C1 to the MySQL database through the thread TR1.

Step 2: After the thread TR1 transmits the query request to the MySQL database, the middleware releases the thread TR1.

Step 3: The middleware listens for the specified network event between the client C1 and the MySQL database.

Step 4: When the MySQL database is listened to generate corresponding query result data according to the query request, and the storage space of the client C1 is not saturated, the middleware re-assigns the second thread to the client C1 and the MySQL database to make the MySQL database. The query result data is transmitted to the client C1 through the reassigned second thread.

The query request sent by the client C1 is the first data, and the query request sent by the client C1 may be a query request based on a Structured Query Language (SQL), for example, if the client If C1 wants to query a certain data in a certain data table in the MySQL database, the query request of the client C1 adopts the statement of "SELECT data item name FROM data table name". Of course, this does not constitute a limitation of the present invention. .

After the client C1 establishes a connection with the MySQL database, the middleware automatically allocates a thread to provide a data transmission service between the client C1 and the MySQL database, that is, transmits the first data sent by the client C1 to the MySQL database, or The second data sent by the MySQL database to the client C1. At this time, the thread allocated by the middleware is the first thread, that is, the thread TR1.

According to an embodiment of the present invention, if the client C1 establishes a connection with the MySQL database and does not transmit data within a predetermined time, the middleware can release the already allocated thread TR1, so that the thread TR1 is another client. The data transmission service is performed at the end. The middleware listens to the specified network event of the client C1 and the MySQL database. When the data transmission between the client C1 and the MySQL database is monitored, the middleware allocates the thread TR1 for the client C1 and the MySQL database to transmit data. . For the above-mentioned preset time, it will be set by the middleware, and, in a feasible way, the middleware can dynamically set the time according to the number of idle threads that can be allocated, in the freely assignable When the number of threads is large, you can extend the time, otherwise shorten the time. Of course, the setting of time herein does not constitute a limitation of the present invention.

For the foregoing step 3, the specified network event includes: a network event in which the MySQL database generates the query result data according to the query request sent by the client C1, and a network event in which the storage space of the client C1 is not saturated. Among them, the query result data here is the first response data.

It should be noted here that, in step four, as a preferred mode, the second thread re-allocated between the client C1 and the MySQL database is still the thread TR1, because the thread TR1 is in the client C1. During the process of transferring the query data to the MySQL database, the thread TR1 is provided with parameters related to the client C1, such as the Internet Protocol (IP) address of the client C1, the transmission port number, etc., so the reallocation is reallocated. When the thread TR1 is used, it is not necessary to set the relevant parameters again. However, if the thread TR1 is allocated to other clients after the transfer of the query request is released, the middleware selects any thread in the idle state as the second thread in the threads TR2~4, and reassigns it to the client C1 and MySQL database.

In Figure 3, client C2 wants to read data from the MySQL database, including the steps:

Step 1: The middleware allocates a thread TR2 for the client C2 and the MySQL database, and transmits the read request issued by the client C2 to the MySQL database through the thread TR2.

Step 2: After the thread TR2 transfers the read request to the MySQL database, the middleware releases Put the thread TR2.

Step 3: The middleware listens for the specified network event between the client C2 and the MySQL database.

Step 4: When the MySQL database is listened to generate a network event corresponding to the read result data according to the read request, but the network event of the client C2 storage space is not monitored, the middleware is not the client C2 and the MySQL database. Reassign the second thread and continue to listen for network events that are not saturated with client C2's storage space.

Step 5: When monitoring the network event of the client C2 storage space is not saturated, the middleware re-allocates the second thread to the client C2 and the MySQL database, so that the MySQL database transmits the read result data through the redistributed second thread. To the client C2.

The read request sent by the client C2 is the first data, and the read result data generated by the MySQL database according to the read request is the first response data.

For the above step three, the specified network event includes: a network event in which the MySQL database generates the read result data according to the read request sent by the client C2, and a network event in which the storage space of the client C2 is not saturated.

After the MySQL database generates the read result data according to the read request sent by the client C2, the MySQL database notifies the middleware that the read result data can be transmitted. However, if the storage space of the client C2 is saturated, the transmission of the read result data will fail. If the middleware does not listen to the network event of the client C2 whose storage space is not saturated, it indicates that the storage space of the client C2 is saturated and cannot receive the read result data of the transmission, so in the fourth step, the middleware is in the waiting state. And will not redistribute the second thread. Only when the middleware simultaneously listens to the above two network events, the second thread is re-allocated, and the read result data is transmitted to the client C2, that is, the above step 5.

For the above step five, preferably, the second thread that the middleware reassigns between the client C2 and the MySQL database is still the thread TR2.

In FIG. 4, after the client C3 is connected to the MySQL database, the MySQL database sends the security command data to the client C3 to determine whether the client C3 is an authentication client, and the steps include:

Step 1: The middleware allocates a thread TR3 for the MySQL database and the client C3, and transmits the security instruction data sent by the MySQL database to the client C3 through the thread TR3.

Step 2: After the thread TR3 transmits the security instruction data to the client C3, the middleware releases the thread TR3.

Step 3: The middleware listens to the specified network between the MySQL database and the client C3. Pieces.

Step 4: When the client C3 is detected to generate the corresponding identity authentication data according to the security instruction data and the network event of the MySQL database storage space is not saturated, the middleware re-allocates the second thread to the MySQL database and the client C3, so that the client C3 transmits the authentication data to the MySQL database through the reassigned second thread.

The security command data sent by the MySQL database is the second data, and the identity authentication data generated by the client C1 according to the security command data is the second response data.

For the above step three, the specified network event includes: a network event in which the client C3 generates identity authentication data according to the security instruction data sent by the MySQL database, and a network event in which the storage space of the MySQL database is not saturated.

For the above step four, preferably, the second thread that the middleware reassigns between the MySQL database and the client C3 is still the thread TR3.

In FIG. 5, after the client C4 is connected to the MySQL database, the MySQL database pushes the update data to the client C4, specifically including the steps:

Step 1: The middleware allocates the thread TR4 to the MySQL database and the client C4, and transmits the updated data sent by the MySQL database to the client C4 through the thread TR4.

Step 2: After the thread TR4 transmits the update data to the client C4, the middleware releases the thread TR4.

Step 3: The middleware listens for the specified network event between the MySQL database and the client C4.

Step 4: When the network time of the corresponding update feedback data is generated by the client C4 according to the update data, but the network event of the MySQL database storage space is not monitored, the middleware is not reallocated for the MySQL database and the client C4. The second thread continues to listen to MySQL database storage space for unsaturated network events.

Step 5: When the network event of the MySQL database storage space is not saturated, the middleware re-allocates the second thread to the MySQL database and the client C4, so that the client C4 transmits the update feedback data to the second thread through the reassignment. MySQL database.

The update data sent by the MySQL database is the second data, and the update feedback data generated by the client C1 according to the update data is the second response data.

For the above step three, the specified network event includes: a network event in which the client C4 generates update feedback data according to the update data sent by the MySQL database, and a network event in which the storage space of the MySQL database is not saturated.

After the client C4 generates the update feedback data according to the update data sent by the MySQL database, the client C4 notifies the middleware that the update feedback data can be transmitted. However, if the storage space is saturated in the MySQL database, the transmission of the update feedback data will fail. The middleware does not listen to the MySQL database storage space is not saturated network events, it indicates that the MySQL database storage space is saturated, can not receive the transmitted update feedback data, so in the fourth step, the middleware is in a waiting state, nor The second thread is reassigned, and the second thread is reassigned only when the middleware simultaneously listens to the above two network events, and the update feedback data is transmitted to the MySQL database, that is, step 5 above.

For the above step five, preferably, the second thread re-allocated between the middleware for the MySQL database and the client C4 is still the thread TR4.

In the above-mentioned actual application scenario, the client may suddenly go offline due to power failure, network congestion, etc. If the middleware detects such a situation, the client may be offline as a special cause. The network event is processed, that is, the client has transmitted the corresponding data through the thread allocated by the middleware, and then the middleware monitors that the client is suddenly offline, and continues to allocate the thread to transfer data according to the state of the data processing. Taking Figure 2 as an example: after the client C1 transmits the query request to the MySQL database through the thread TR1 allocated by the middleware, the MySQL database processes the query request, the middleware releases the thread TR1, and the middleware listens to the client C1. Network events between the MySQL database and the MySQL database. At this point, the middleware listens to the network event that the client C1 suddenly goes offline, and the MySQL database has generated the corresponding query result data according to the query request of the client C1, and the middleware also listens to the MySQL database to generate the query result data. The network event, then, the middleware will still allocate a second thread, transfer the query result data to the middleware itself for caching, and then the middleware releases the second thread to listen to the network event that the client C1 is back online. Upon monitoring that the client C1 is back online and connected to the middleware, the middleware reassigns the third thread to send the cached query result data to the client C1. In this way, even if the client C1 is back online, there is no need to issue a request to the MySQL database to reacquire the query result data, but the middleware directly allocates the thread to transmit the query result data to the client C1, thereby effectively increasing the data transmission. Efficiency and convenience.

Of course, the second thread and the third thread allocated by the above middleware, in a preferred manner, are the first thread assigned to the client C1 and the MySQL database, that is, the thread TR1.

The above is the data transmission method provided by the embodiment of the present invention. Based on the same idea, the embodiment of the present invention further provides a data transmission apparatus, as shown in FIG. 6.

The data transmission device in Figure 6 is set in the middleware for use on the client and server The data transmission is performed, and the device includes: a first distribution module 601, a release module 602, a monitoring module 603, and a second distribution module 604, where

The first allocating module 601 is configured to allocate a first thread to the client and the database, so that the client and the database transmit data through the first thread.

The releasing module 602 is configured to release the first thread after the first thread completes the transmission of the data.

The monitoring module 603 is configured to listen to network events of the client and the database.

The second allocation module 604 is configured to re-allocate the second thread to the client and the database after listening to the specified network event.

In an embodiment of the present invention, the data includes: first data sent by the client to the database, or second data sent by the database to the client. The specified network event includes: the database generating a network event of the first response data according to the first data, or the client generating a network event of the second response data according to the second data.

Specifically, the second allocating module 604 is specifically configured to re-allocate the client and the database when the network event of the first response data is generated according to the first data is monitored. a thread, the database is caused to transmit the first response data to the client by a redistributed second thread, or when the client is monitored to generate the second response data according to the second data, Re-assigning the second thread to the client and the database, causing the client to transmit the second response data to the database through the reassigned second thread.

In another embodiment of the present invention, the specifying a network event further comprises: a network event in which the storage space of the client or database is not saturated.

Specifically, the second allocation module 604 is specifically configured to: when listening to the network event that the database generates the first response data according to the first data, and a network event that is not saturated by the storage space of the client Re-allocating the second thread to the client and the database, causing the database to transmit the first response data to the client through the reassigned second thread, or when listening to the client according to the The second data generates a network event of the second response data, and when the storage space of the database is not saturated, re-allocating the second thread to the client and the database, so that the client passes the redistributed The second thread transmits the second response data to the database.

In an embodiment of the present invention, the second allocation module 604 is specifically configured to: use the first thread used by the client and the database to transmit the data as a second thread, and Assigned to the client and database.

An embodiment of the present invention provides a thread management method and apparatus. After the middleware allocates data to a client or a database, the middleware releases the first thread, and the first thread is turned into an idle state for allocation. Give other clients or handle other services. At the same time, the middleware will re-allocate the second thread for data transfer between the client and the database after listening to the specified network event between the client and the database. The limited thread resources in the middleware provide data services for data transmission between the client and the database, and also effectively improve the utilization of threads.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of the description.

Similarly, the various features of the invention are sometimes grouped together into a single embodiment, in the above description of the exemplary embodiments of the invention, Figure, or a description of it. However, the method disclosed is not to be interpreted as reflecting the intention that the claimed invention requires more features than those recited in the claims. Rather, as the following claims reflect, inventive aspects reside in less than all features of the single embodiments disclosed herein. Therefore, the claims following the specific embodiments are hereby explicitly incorporated into the embodiments, and each of the claims as a separate embodiment of the invention.

Those skilled in the art will appreciate that the modules in the devices of the embodiments can be adaptively changed and placed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and further they may be divided into a plurality of sub-modules or sub-units or sub-components. In addition to such features and/or at least some of the processes or units being mutually exclusive, any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the device are combined. Each feature disclosed in this specification (including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.

In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features that are included in other embodiments and not in other features, combinations of features of different embodiments are intended to be within the scope of the present invention. Different embodiments are formed and formed. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Technology in the field It should be understood that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components of a data transmission device in accordance with embodiments of the present invention. The invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

For example, Figure 7 illustrates a computing device that can implement a data transfer method. The computing device conventionally includes a processor 710 and a computer program product or computer readable medium in the form of a memory 720. Memory 720 can be an electronic memory such as a flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM. Memory 720 has a memory space 730 for program code 731 for performing any of the method steps described above. For example, storage space 730 for program code may include various program code 731 for implementing various steps in the above methods, respectively. The program code can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. Such a computer program product is typically a portable or fixed storage unit as described with reference to FIG. The storage unit may have storage segments, storage spaces, and the like that are similarly arranged to memory 720 in the computing device of FIG. The program code can be compressed, for example, in an appropriate form. Typically, the storage unit includes computer readable code 731', ie, code readable by a processor, such as 710, that when executed by a computing device causes the computing device to perform each of the methods described above step.

"an embodiment," or "an embodiment," or "an embodiment," In addition, it is noted that the phrase "in one embodiment" is not necessarily referring to the same embodiment.

It is to be noted that the above-described embodiments are illustrative of the invention and are not intended to be limiting, and that the invention may be devised without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as a limitation. The word "comprising" does not exclude the presence of the elements or steps that are not recited in the claims. The word "a" or "an" The invention can be implemented by means of hardware comprising several distinct elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means can be embodied by the same hardware item. The use of the words first, second, and third does not indicate any order. These words can be interpreted as names.

In addition, it should be noted that the language used in the specification has been selected for the purpose of readability and teaching, and is not intended to be construed or limited. Therefore, many modifications and changes will be apparent to those skilled in the art without departing from the scope of the invention. The disclosure of the present invention is intended to be illustrative, and not restrictive, and the scope of the invention is defined by the appended claims.

Claims

A data transmission method for data transmission between a client and a server by using a middleware, the method comprising:

The middleware allocates a first thread to the client and the database, so that the client and the database transmit data through the first thread;

The middleware releases the first thread after the first thread completes the transmission of the data;

Listening to network events of the client and database;

After listening to the specified network event, re-allocate the second thread to the client and database.
The method of claim 1, wherein the data comprises: first data sent by the client to the database, or second data sent by the database to the client;

The specified network event includes: the database generating a network event of the first response data according to the first data, or the client generating a network event of the second response data according to the second data.
The method of claim 2, wherein after the specified network event is detected, the second thread is re-allocated to the client and the database, including:

When the network event of the first response data is generated according to the first data, the middleware re-allocates a second thread to the client and the database, so that the database is redistributed. Two threads transmitting the first response data to the client; or

When the client is monitored to generate the second response data according to the second data, the middleware re-allocates a second thread to the client and the database, so that the client passes the second redistributed The thread transmits the second response data to the database.
The method of claim 2, wherein the specifying a network event further comprises: a network event in which the storage space of the client or database is not saturated;

After listening to the specified network event, re-allocating the second thread to the client and the database, including:

The middleware re-allocates the client and the database when the network event of the first response data is generated according to the first data, and the network event of the client's storage space is not saturated. a second thread, causing the database to transmit the first response data to the client through a redistributed second thread; or

When the network event of the second response data is generated by the client according to the second data, and the network event of the storage space of the database is not saturated, the middleware re-assigns the client and the database. Two threads that enable the client to pass the redistribution The second thread transmits the second response data to the database.
The method of any one of claims 1 to 4, wherein reassigning the second thread to the client and the database comprises:

The first thread used by the client and the database to transfer the data is reassigned to the client and database as a second thread.
A data transmission device, configured to perform data transmission between a client and a server, the device comprising: a first distribution module, a release module, a monitoring module, and a second distribution module, wherein

The first allocating module is configured to allocate a first thread to the client and the database, so that the client and the database transmit data through the first thread;

The release module is configured to release the first thread after the thread completes the transmission of the data;

The monitoring module is configured to listen to network events of the client and the database;

The second allocation module is configured to re-allocate the second thread to the client and the database after listening to the specified network event.
The apparatus according to claim 6, wherein the data comprises: first data sent by the client to the database, or second data sent by the database to the client;

The specified network event includes: the database generating a network event of the first response data according to the first data, or the client generating a network event of the second response data according to the second data.
The device of claim 7, wherein the second distribution module is specifically configured to:

Retrieving a second thread to the client and the database when the network event of the first response data is generated according to the first data is monitored, so that the database is to be re-allocated by the second thread Transmitting first response data to the client; or

And when the client is configured to generate the second response data according to the second data, re-allocating the second thread to the client and the database, and causing the client to pass the second thread by redistributing The second response data is transmitted to the database.
The device of claim 7, wherein the specified network event further comprises: a network event in which the storage space of the client or the database is not saturated; and the second allocation module is specifically configured to:

Retrieving a second thread for the client and the database when the network event of the first response data is generated according to the first data, and the network event of the client is not saturated, Causing the database to transmit the first response data to the client via a redistributed second thread; or

Retrieving the client when listening to a network event in which the client generates second response data according to the second data, and a network event in which the storage space of the database is not saturated The end and the database allocate a second thread, causing the client to transmit the second response data to the database through the reassigned second thread.
The apparatus according to any one of claims 6 to 9, wherein the second distribution module is specifically configured to:

The first thread used by the client and the database to transfer the data is reassigned to the client and database as a second thread.
A computer program comprising computer readable code that, when executed on a computing device, causes the computing device to perform the data transmission method of any one of claims 1 to 5.
A computer readable medium storing the computer program of claim 11.