CN110515706B - Request processing method, device, equipment and readable storage medium - Google Patents
Request processing method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN110515706B CN110515706B CN201910760128.0A CN201910760128A CN110515706B CN 110515706 B CN110515706 B CN 110515706B CN 201910760128 A CN201910760128 A CN 201910760128A CN 110515706 B CN110515706 B CN 110515706B
- Authority
- CN
- China
- Prior art keywords
- thread
- target
- request
- main
- processing
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 18
- 238000000034 method Methods 0.000 claims abstract description 70
- 238000004590 computer program Methods 0.000 claims description 12
- 230000000694 effects Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000008094 contradictory effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- 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
-
- 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
- G06F9/524—Deadlock detection or avoidance
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a request processing method, which is applied to a server side, wherein the server side and a client side communicate through a CIFS protocol, and the method comprises the following steps: receiving and processing a plurality of requests sent by any client side in parallel through a plurality of threads; if the target request needs to access a database and/or an IPC channel of a server side in the processing process, judging whether a target thread receiving the target request is a main thread; if not, the target thread sends the target request to the main thread so as to access the database and/or the IPC channel by using the main thread, and sends the access result to the target thread so that the target thread processes the target request according to the access result. According to the method and the device, the plurality of requests sent by any client can be received and processed in parallel through the plurality of threads, and the plurality of threads are bound with the plurality of logic channels one by one, so that the receiving and processing efficiency of the server to the requests can be improved. Accordingly, the request processing device, the request processing apparatus and the readable storage medium disclosed by the application also have the technical effects.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a request processing method, apparatus, device, and readable storage medium.
Background
In the prior art, when a client and a server communicate through a CIFS protocol, the client may send a request to the server in parallel through a plurality of logical channels, but the server cannot receive the request in parallel, and only polls each logical channel one by one to receive a plurality of requests sent by the client in parallel. The reasons for the above problems are: the server is only provided with one thread for receiving and processing the request for each client, and the thread is used for receiving and processing the requests sent by a plurality of logical channels, so that the receiving and processing efficiency of the requests is low.
Therefore, when the client and the server communicate through the CIFS protocol, how to improve the efficiency of receiving and processing the request by the server is a problem to be solved by those skilled in the art.
Disclosure of Invention
In view of this, an object of the present application is to provide a request processing method, apparatus, device, and readable storage medium, so as to improve the efficiency of receiving and processing a request by a server when a client and the server communicate through a CIFS protocol. The specific scheme is as follows:
in a first aspect, the present application provides a request processing method, which is applied to a server, where the server and a client communicate via a CIFS protocol, and the method includes:
receiving and processing a plurality of requests sent by any client side in parallel through a plurality of threads; the multiple threads are bound with the multiple logic channels one by one, and comprise a main thread and at least one sub-thread;
if the target request needs to access a database and/or an IPC channel of a server side in the processing process, judging whether a target thread receiving the target request is a main thread; the target request is any one of a plurality of requests;
if not, the target thread sends the target request to the main thread so as to access the database and/or the IPC channel by using the main thread, and sends the access result to the target thread so that the target thread processes the target request according to the access result.
Preferably, the method further comprises the following steps:
if a logic channel creation request sent by a client is received, creating a first logic channel and creating a service process corresponding to the client;
a first thread in the service process is bound to the first logical channel and marked as a main thread.
Preferably, the method further comprises the following steps:
and if the logic channel creation request sent by the client is received again, creating a second logic channel, binding a second thread in the service process with the second logic channel, and marking the second thread as a sub-thread.
Preferably, if there are a plurality of main threads, the target thread sends the target request to the main thread to access the database and/or the IPC channel by using the main thread, including:
the target thread sends the target request to any of the main threads to access the database and/or IPC channel with the main thread receiving the target request.
Preferably, the method further comprises the following steps:
if a plurality of main threads access the database and/or the IPC channel, different main threads access the database and/or the IPC channel in sequence according to the sizes of the identifiers of different main threads.
Preferably, the method further comprises the following steps:
and if the target thread receiving the target request is the main thread, accessing the database and/or the IPC channel by using the target thread, and processing the target request according to an access result.
Preferably, the method further comprises the following steps:
and if the main thread receives a plurality of target requests, adding the target requests to a processing linked list of the main thread according to the receiving time sequence, and accessing the database and/or the IPC channel according to the first-in first-out principle to obtain access results corresponding to different target requests.
In a second aspect, the present application provides a request processing apparatus, applied to a server, including:
the processing module is used for receiving and processing a plurality of requests sent by any client side in parallel through a plurality of threads; the multiple threads are bound with the multiple logic channels one by one, and comprise a main thread and at least one sub-thread;
the judging module is used for judging whether a target thread receiving the target request is a main thread or not if the target request needs to access a database and/or an IPC channel of a server side in the processing process; the target request is any one of a plurality of requests;
and the execution module is used for sending the target request to the main thread by the target thread if the target thread receiving the target request is not the main thread so as to access the database and/or the IPC channel by using the main thread and sending the access result to the target thread so that the target thread processes the target request according to the access result.
In a third aspect, the present application provides a request processing device, including:
a memory for storing a computer program;
a processor for executing a computer program to implement the request processing method disclosed in the foregoing.
In a fourth aspect, the present application provides a readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the request processing method disclosed in the foregoing.
According to the above scheme, the application provides a request processing method, which is applied to a server, where the server and a client communicate through a CIFS protocol, and the method includes: receiving and processing a plurality of requests sent by any client side in parallel through a plurality of threads; the multiple threads are bound with the multiple logic channels one by one, and comprise a main thread and at least one sub-thread; if the target request needs to access a database and/or an IPC channel of a server in the processing process, judging whether a target thread receiving the target request is a main thread; the target request is any one of a plurality of requests; if not, the target thread sends the target request to the main thread so as to access the database and/or the IPC channel by using the main thread, and sends the access result to the target thread so that the target thread processes the target request according to the access result.
Therefore, the method can receive and process a plurality of requests sent by any client side in parallel through a plurality of threads, and the plurality of threads are bound with a plurality of logic channels one by one, so that the receiving and processing efficiency of the server side for the requests can be improved. The IPC channel only allows one connection to be established at the same time, so that a plurality of threads cannot access the database and/or the IPC channel at the same time, and if the threads access the database at the same time, the file lock can be locked. In order to solve the problem, the method and the device enable the multiple threads to comprise a main thread and at least one sub-thread, when a request needing to access the database and/or the IPC channel of the server side is met, the unique main thread is uniformly used for accessing the database and/or the IPC channel, and meanwhile an access result is sent to a target thread processing the current request, so that the target thread continues to process the current request.
Accordingly, the request processing device, the request processing apparatus and the readable storage medium provided by the application also have the technical effects.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flow chart of a request processing method disclosed herein;
FIG. 2 is a flow chart of a logical channel creation method disclosed herein;
FIG. 3 is a schematic diagram of a request processing apparatus disclosed herein;
fig. 4 is a schematic diagram of a request processing device disclosed in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Currently, when a client and a server communicate through a CIFS protocol, the server is only provided with one thread for receiving and processing requests for each client, and the thread is used for receiving and processing requests sent through a plurality of logical channels, which results in low efficiency in receiving and processing requests. Therefore, the request processing scheme is provided, and the receiving and processing efficiency of the server for the request can be improved.
Referring to fig. 1, an embodiment of the present application discloses a first request processing method, which is applied to a server, where the server and a client communicate via a CIFS protocol, and the method includes:
s101, receiving and processing a plurality of requests sent by any client side in parallel through a plurality of threads;
the multiple threads are bound with the multiple logic channels one by one, and the multiple threads comprise a main thread and at least one sub-thread. The main thread can be used to handle many types of requests, and the sub-thread can only be used to handle requests that do not involve databases and IPC channels.
It should be noted that the logical channels are disposed on the physical channels, and a plurality of logical channels may be disposed on one physical channel. The server and a client can communicate through a plurality of logical channels, and the plurality of logical channels can be arranged on the same physical channel or different physical channels.
For example: 10 physical channels are established between the server and all the clients, each physical channel can be provided with 3 logical channels, one client and the server communicate through 4 logical channels, the 4 logical channels can be respectively positioned on 4 different physical channels, and each physical channel is provided with 1 channel; or respectively on 2 different physical channels, each physical channel being provided with 2. Furthermore, the 4 logic channels are respectively and correspondingly bound with 4 threads, wherein one thread is a main thread, and the other thread is a sub-thread.
S102, if the target request needs to access a database and/or an IPC channel of a server side in the processing process, judging whether a target thread receiving the target request is a main thread; if yes, executing S103; if not, executing S104;
wherein the target request is any one of a plurality of requests. The target thread that receives the target request is also any one of the plurality of threads.
S103, accessing the database and/or the IPC channel by using the target thread, and processing the target request according to the access result;
s104, the target thread sends the target request to the main thread so as to access the database and/or the IPC channel by using the main thread, and sends the access result to the target thread so that the target thread processes the target request according to the access result.
In this embodiment, if the main thread receives multiple target requests, the multiple target requests are added to the processing linked list of the main thread according to the receiving time sequence, and the database and/or the IPC channel are accessed according to the first-in first-out principle, so as to obtain access results corresponding to different target requests.
For example: if the main thread receives 3 target requests, the 3 target requests are added to the processing linked list of the main thread according to the receiving time sequence, wherein the receiving time is the time stamp of the main thread receiving the target requests. If the first target request is received at 11:30 am of a day, the second target request is received at 11:31 am of the day, and the third target request is received at 11:32 am of the day, then the first received target request must first be added to the processing chain. Further, accessing the database and/or IPC channels is: firstly, accessing a database and/or an IPC channel according to the requirement of a first target request, obtaining an access result, and feeding back the access result to a target thread for receiving and processing the first target request; then accessing the database and/or the IPC channel according to the requirement of the second target request to obtain an access result, and feeding back the access result to a target thread for receiving and processing the second target request; and finally, accessing the database and/or the IPC channel according to the requirement of the third target request, obtaining an access result, and feeding back the access result to a target thread for receiving and processing the third target request. I.e., access to the database and/or IPC channels on a first-in-first-out basis.
In this embodiment, if there are a plurality of main threads, the target thread sends the target request to the main thread to access the database and/or the IPC channel by using the main thread, including: the target thread sends the target request to any of the main threads to access the database and/or IPC channel with the main thread receiving the target request.
If a plurality of main threads access the database and/or the IPC channel, different main threads access the database and/or the IPC channel in sequence according to the sizes of the identifiers of different main threads. That is, each main thread may set up a different size identifier to access the database and/or IPC channels in order of identifier size. Of course, all threads may set different size identifiers so that all threads can access the database and/or IPC channels in order of identifier size. The order of the sizes of the identifiers may be in a positive order or in a negative order.
Therefore, the embodiment can receive and process a plurality of requests sent by any client side in parallel through a plurality of threads, and the plurality of threads are bound with a plurality of logic channels one by one, so that the receiving and processing efficiency of the server side for the requests can be improved. The request may need to access the database and/or the IPC channel of the server in the processing process, the database is provided with a plurality of file locks, and the IPC channel is only allowed to establish one connection at the same time, so that a plurality of threads cannot access the database and/or the IPC channel at the same time, and if the plurality of threads access the database at the same time, the file locks may be locked. In order to solve the problem, the method and the device enable the multiple threads to comprise a main thread and at least one sub-thread, when a request needing to access the database and/or the IPC channel of the server side is met, the unique main thread is uniformly used for accessing the database and/or the IPC channel, and meanwhile an access result is sent to a target thread processing the current request, so that the target thread continues to process the current request.
Referring to fig. 2, an embodiment of the present application discloses a method for creating a logical channel, including:
s201, receiving a logic channel creation request sent by a client;
s202, creating a first logic channel and creating a service process corresponding to the client;
a plurality of threads are preset in a service process corresponding to the client. Each client corresponds to a service process.
S203, binding a first thread in the service process with the first logic channel;
and S204, marking the first thread as a main thread.
S205, if a logic channel creation request sent by the client is received again, creating a second logic channel;
s206, binding a second thread in the service process with a second logic channel;
and S207, marking the second thread as a sub thread.
It should be noted that, the implementation steps in this embodiment may be mutually referred to with the steps disclosed in the above embodiments.
As can be seen from the above, in this embodiment, a corresponding thread can be bound for each logical channel, so that the server can receive and process multiple requests sent by the client in parallel by using the multiple threads, and simultaneously can return multiple processing results to the client in parallel, thereby improving the efficiency of request reception and processing.
In the following, a request processing apparatus provided by an embodiment of the present application is introduced, and a request processing apparatus described below and a request processing method described above may be referred to each other.
Referring to fig. 3, an embodiment of the present application discloses a request processing apparatus, applied to a server, including:
a processing module 301, configured to receive and process multiple requests sent by any one client in parallel through multiple threads; the multiple threads are bound with the multiple logic channels one by one, and comprise a main thread and at least one sub-thread;
a determining module 302, configured to determine whether a target thread receiving a target request is a main thread if the target request needs to access a database and/or an IPC channel of a server in a processing process; the target request is any one of a plurality of requests;
the execution module 303 is configured to, if the target thread receiving the target request is not the main thread, send the target request to the main thread by the target thread, so as to access the database and/or the IPC channel by using the main thread, and send the access result to the target thread, so that the target thread processes the target request according to the access result.
In a specific embodiment, the method further comprises the following steps:
the first creation module is used for creating a first logic channel and creating a service process corresponding to the client if a logic channel creation request sent by the client is received;
and the binding module is used for binding a first thread in the service process with the first logic channel and marking the first thread as a main thread.
In a specific embodiment, the method further comprises the following steps:
and the second creating module is used for creating a second logic channel, binding a second thread in the service process with the second logic channel and marking the second thread as a sub-thread if the logic channel creating request sent by the client is received again.
In a specific embodiment, the execution module is specifically configured to:
if the number of the main threads is multiple, the target thread sends the target request to any one main thread so as to utilize the main thread receiving the target request to access the database and/or the IPC channel.
In a specific embodiment, the execution module is specifically configured to:
if a plurality of main threads access the database and/or the IPC channel, different main threads access the database and/or the IPC channel in sequence according to the sizes of the identifiers of different main threads.
In a specific embodiment, the execution module is specifically configured to:
and if the target thread receiving the target request is the main thread, accessing the database and/or the IPC channel by using the target thread, and processing the target request according to an access result.
In a specific embodiment, the execution module is specifically configured to:
and if the main thread receives a plurality of target requests, adding the target requests to a processing linked list of the main thread according to the receiving time sequence, and accessing the database and/or the IPC channel according to the first-in first-out principle to obtain access results corresponding to different target requests.
For more specific working processes of each module and unit in this embodiment, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not described here again.
As can be seen, the present embodiment provides a request processing apparatus, including: the device comprises a processing module, a judging module and an executing module. Firstly, a processing module receives and processes a plurality of requests sent by any client side in parallel through a plurality of threads; if the target request needs to access a database and/or an IPC channel of a server side in the processing process, the judging module judges whether a target thread receiving the target request is a main thread; if the target thread receiving the target request is not the main thread, the execution module enables the target thread to send the target request to the main thread so as to utilize the main thread to access the database and/or the IPC channel, and sends an access result to the target thread so that the target thread processes the target request according to the access result. Therefore, all modules are in work division and cooperation and each takes its own role, and the receiving and processing efficiency of the server for the request is improved.
In the following, a request processing device provided by an embodiment of the present application is introduced, and a request processing device described below and a request processing method and apparatus described above may be referred to each other.
Referring to fig. 4, an embodiment of the present application discloses a request processing device, including:
a memory 401 for storing a computer program;
a processor 402 for executing the computer program to implement the method disclosed by any of the embodiments described above.
A readable storage medium provided in the embodiments of the present application is introduced below, and a readable storage medium described below and a request processing method, apparatus, and device described above may be referred to each other.
A readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the request processing method disclosed in the foregoing embodiments. For the specific steps of the method, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
References in this application to "first," "second," "third," "fourth," etc., if any, are intended to distinguish between similar elements and not necessarily to describe a particular order or sequence. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Moreover, the terms "comprises" and "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, or apparatus.
It should be noted that the descriptions in this application referring to "first", "second", etc. are for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present application.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of readable storage medium known in the art.
The principle and the implementation of the present application are explained herein by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (4)
1. A request processing method is applied to a server, the server and a client communicate through a CIFS protocol, and the method comprises the following steps:
receiving and processing a plurality of requests sent by any client side in parallel through a plurality of threads; the multiple threads are bound with the multiple logic channels one by one, and comprise a main thread and at least one sub-thread; the main thread is used for processing various types of requests, and the sub-thread is used for processing requests which do not relate to a database and an IPC channel;
if the target request needs to access the database and the IPC channel of the server in the processing process, judging whether a target thread receiving the target request is the main thread; the target request is any one of the plurality of requests;
if not, the target thread sends the target request to the main thread so as to utilize the main thread to access the database and the IPC channel, and sends an access result to the target thread so that the target thread processes the target request according to the access result;
if the number of the main threads preset by the server is multiple, when the multiple main threads access the database and the IPC channel, different main threads access the database and the IPC channel sequentially according to the size of the identifiers of different main threads;
wherein, still include:
if a logic channel creation request sent by the client is received, creating a first logic channel and creating a service process corresponding to the client;
binding a first thread in the service process with the first logic channel, and marking the first thread as a main thread;
wherein, still include:
if a logic channel creation request sent by the client is received again, creating a second logic channel, binding a second thread in the service process with the second logic channel, and marking the second thread as the sub-thread;
wherein, still include:
if the target thread receiving the target request is a main thread, accessing the database and the IPC channel by using the target thread, and processing the target request according to an access result;
wherein, still include:
and if the main thread receives a plurality of target requests, adding the target requests to a processing linked list of the main thread according to the receiving time sequence, and accessing the database and the IPC channel according to a first-in first-out principle to obtain access results corresponding to different target requests.
2. A request processing apparatus, applied to a server, where the server and a client communicate via a CIFS protocol, comprising:
the processing module is used for receiving and processing a plurality of requests sent by any client side in parallel through a plurality of threads; the multiple threads are bound with the multiple logic channels one by one, and the multiple threads comprise a main thread and at least one sub-thread; the main thread is used for processing various types of requests, and the sub-thread is used for processing requests which do not relate to a database and an IPC channel;
the judging module is used for judging whether a target thread receiving the target request is the main thread or not if the target request needs to access the database and the IPC channel of the server in the processing process; the target request is any one of the plurality of requests;
the execution module is used for sending the target request to the main thread by the target thread if the target thread receiving the target request is not the main thread so as to access the database and the IPC channel by using the main thread and sending an access result to the target thread so that the target thread processes the target request according to the access result;
the execution module is specifically configured to: if the number of the main threads preset by the server is multiple, when the multiple main threads access the database and the IPC channel, different main threads access the database and the IPC channel sequentially according to the size of the identifiers of different main threads;
wherein, still include:
the first creation module is used for creating a first logic channel and creating a service process corresponding to the client if a logic channel creation request sent by the client is received;
a binding module, configured to bind a first thread in the service process with the first logic channel, and mark the first thread as a main thread;
wherein, still include:
a second creating module, configured to create a second logical channel if a logical channel creation request sent by the client is received again, bind a second thread in the service process with the second logical channel, and mark the second thread as the child thread;
wherein the execution module is further configured to:
if the target thread receiving the target request is a main thread, accessing the database and the IPC channel by using the target thread, and processing the target request according to an access result;
wherein the execution module is further configured to:
and if the main thread receives a plurality of target requests, adding the target requests to a processing linked list of the main thread according to a receiving time sequence, and accessing the database and the IPC channel according to a first-in first-out principle to obtain access results corresponding to different target requests.
3. A request processing device, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the request processing method of claim 1.
4. A readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the request processing method of claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910760128.0A CN110515706B (en) | 2019-08-16 | 2019-08-16 | Request processing method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910760128.0A CN110515706B (en) | 2019-08-16 | 2019-08-16 | Request processing method, device, equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110515706A CN110515706A (en) | 2019-11-29 |
| CN110515706B true CN110515706B (en) | 2022-07-08 |
Family
ID=68625552
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910760128.0A Active CN110515706B (en) | 2019-08-16 | 2019-08-16 | Request processing method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110515706B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112929870B (en) * | 2019-12-06 | 2022-07-22 | 华为技术有限公司 | Event subscription method and electronic equipment |
| CN111585827A (en) * | 2020-06-03 | 2020-08-25 | 贵州电网有限责任公司 | Power data transmission method and device, terminal equipment and storage medium |
| CN111654322A (en) * | 2020-06-03 | 2020-09-11 | 贵州电网有限责任公司 | Electric power data transmission method and device based on parallel processing and storage medium |
| CN113268501A (en) * | 2021-05-26 | 2021-08-17 | 杭州迪普科技股份有限公司 | Report generation method and device |
| CN113626226B (en) * | 2021-10-13 | 2022-02-22 | 云和恩墨(北京)信息技术有限公司 | Data communication method and device, processor and computer storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293946A (en) * | 2016-08-16 | 2017-01-04 | 东软集团股份有限公司 | The method of resource acquisition and server |
| CN106528293A (en) * | 2016-11-04 | 2017-03-22 | 武汉斗鱼网络科技有限公司 | Database access method and apparatus |
| CN107704328A (en) * | 2017-10-09 | 2018-02-16 | 郑州云海信息技术有限公司 | Client accesses method, system, device and the storage medium of file system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9171044B2 (en) * | 2010-02-16 | 2015-10-27 | Oracle International Corporation | Method and system for parallelizing database requests |
-
2019
- 2019-08-16 CN CN201910760128.0A patent/CN110515706B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293946A (en) * | 2016-08-16 | 2017-01-04 | 东软集团股份有限公司 | The method of resource acquisition and server |
| CN106528293A (en) * | 2016-11-04 | 2017-03-22 | 武汉斗鱼网络科技有限公司 | Database access method and apparatus |
| CN107704328A (en) * | 2017-10-09 | 2018-02-16 | 郑州云海信息技术有限公司 | Client accesses method, system, device and the storage medium of file system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110515706A (en) | 2019-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110515706B (en) | Request processing method, device, equipment and readable storage medium | |
| CN109327550B (en) | Access request distribution method and device, storage medium and computer equipment | |
| CN106933871B (en) | Short link processing method and device and short link server | |
| CN102263828B (en) | Load balanced sharing method and equipment | |
| EP3170091B1 (en) | Method and server of remote information query | |
| CN108173774B (en) | Client upgrading method and system | |
| EP2942914B1 (en) | Load sharing method and apparatus | |
| CN105630731A (en) | Network card data processing method and device in multi-CPU (Central Processing Unit) environment | |
| CN103095758B (en) | A kind of method processing file data in distributed file system and this system | |
| CN110213392B (en) | Data distribution method and device, computer equipment and storage medium | |
| US20140143339A1 (en) | Method, apparatus, and system for resource sharing | |
| CN111782383A (en) | Task allocation method, server, electronic terminal and computer readable storage medium | |
| CN102713925A (en) | Sensitive information leakage prevention system, sensitive information leakage prevention method and sensitive information leakage prevention program | |
| CN109416646B (en) | Optimization method for container allocation and processing equipment | |
| CN111949856B (en) | Web-based object storage query method and device | |
| CN108363786A (en) | Load method, apparatus, computer equipment and the storage medium of data | |
| CN105792247B (en) | data pushing method and device | |
| CN110008029B (en) | ceph metadata cluster directory distribution method, system, device and readable storage medium | |
| CN111224939A (en) | Task request intercepting method and device, computer equipment and storage medium | |
| CN110619022A (en) | Node detection method, device, equipment and storage medium based on block chain network | |
| CN111327680B (en) | Authentication data synchronization method, device, system, computer equipment and storage medium | |
| US20120265855A1 (en) | Maximizing data transfer through multiple network devices | |
| CN113596105B (en) | Content acquisition method, edge node and computer readable storage medium | |
| CN110908807B (en) | IO task processing method, device, equipment and readable storage medium | |
| CN107231339B (en) | Method and device for detecting DDoS attack |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |