CN110808956B - Data interaction method and system - Google Patents
Data interaction method and system Download PDFInfo
- Publication number
- CN110808956B CN110808956B CN201910942380.3A CN201910942380A CN110808956B CN 110808956 B CN110808956 B CN 110808956B CN 201910942380 A CN201910942380 A CN 201910942380A CN 110808956 B CN110808956 B CN 110808956B
- Authority
- CN
- China
- Prior art keywords
- data
- server
- container
- client
- request message
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data interaction method and a system, wherein the method comprises the following steps: the client sends a first request message comprising container information and access conditions to the server; the server receives the first request message and returns a first response message comprising the data number and the quantity taking identifier to the client; the client receives the first response message and acquires the number of the data; creating a thread and configuring the processing capacity of the thread according to the number of the data; and sending a second request message including thread processing capability to the server; the server receives the second request message and obtains data meeting the access condition from the database paging; sending the data acquired each time to a container; and the thread of the client acquires data and judges whether the data acquisition is completed. The invention can improve the access efficiency of the client, save the resources of the client and the server and reduce the burden of the server.
Description
Technical Field
The invention relates to the technical field of data processing of forklift equipment, in particular to a data interaction method and a data interaction system.
Background
At present, data interaction between a client and a server mainly adopts the following two ways:
(1) the client side adopts a request access form, namely an interface access form. Specifically, the client sets corresponding parameters according to the interface provided by the server and the condition with good constraint, sends a request to the server and waits for the server to return a response result. The server verifies the request of the client according to the preset condition, if the verification is passed, the result is returned to the client from the corresponding position according to the preset condition, and the client receives the response result returned by the server to indicate that the interaction is finished.
(2) The client takes the form of a request-free access, i.e., via a queue or other buffer, referred to herein as a container. The server side sends data required by the client side to the container in real time or in irregular time; the client needs to start the monitoring thread all the time, monitor the queue or the cache in real time, and retrieve the data when the data in the container is monitored.
When the client side adopts a request access mode, and the data volume returned by the server side is large, the client side needs to wait for a response result for a long time. In addition, when the client side adopts a request access form, when the server side grants a request of the client side and the request is verified to pass, the server side needs to obtain corresponding data from a specific position (such as a database), when the server side successfully fetches the data and returns the data to the client side to fail, the server side indicates that the request access fails, but the server side already does a large part of work (such as a service data processing process in the fetching process), so that waste of space resources (the data fetching needs to be stored in the server or a cache firstly) and time resources (the fetching process needs a certain time, and the time is different due to different data volumes) is caused.
When the client side adopts the non-request access, the client side needs to start a plurality of (more than or equal to 1) threads of the monitoring container all the time, and even if the container has no data, the monitoring threads also need to be started, so that the burden of the client side is increased, and the resources are wasted.
Disclosure of Invention
The invention mainly aims to overcome the defects in the prior art, and provides a data interaction method and a data interaction system, which can improve the access efficiency of a client, save resources of the client and a server, and reduce the burden of the server.
The invention adopts the following technical scheme:
in one aspect, the present invention provides a data interaction method, including:
s101, a client sends a first request message comprising container information and access conditions to a server;
s102, the server receives the first request message and verifies whether the first request message is legal or not; if the data is legal, acquiring the number of the data meeting the access condition from a database according to the access condition, and returning a first response message comprising the number of the data and the access identifier to the client;
s103, the client receives the first response message, judges whether the quantity taking identifier is equal to a first preset value or not, and if so, acquires the number of the data pieces; creating a thread for monitoring the data in the container and the processing capacity of a configuration thread according to the number of the data; and sending a second request message including thread processing capabilities to the server;
s104, the server receives the second request message, and obtains data meeting the access condition from a database page according to the access number and the thread processing capacity; sending a request message including the data acquired each time and the corresponding access ending identifier to the container;
s105, when the thread of the client monitors that the container has data, acquiring the data and judging whether the corresponding access ending identifier is equal to a second preset value or not, and if not, continuing to monitor; if so, the monitoring is ended.
Preferably, after receiving the first request message, the server verifies whether the first request message is legal according to the access condition.
Preferably, if the first request message is illegal, the fetch identifier is set not equal to the first preset value, and the number of data pieces is set to 0.
Preferably, if the first request message is legal, but the server acquires the number of data pieces meeting the fetching condition from the database and equals to 0, the fetching amount identifier is set not to be equal to the first preset value, and the number of data pieces is set to 0.
Preferably, if the first request message is legal but the server fails to acquire the number of data pieces satisfying the fetching condition from the database, the fetching amount identifier is set to be not equal to the first preset value, and the number of data pieces is set to be 0.
Preferably, the container is a queue or a stack; the container information includes a container name, a container address, and a key to access the container.
Preferably, the S104 further includes: and after receiving the request message sent by the server, the container verifies whether one or more items in the container name, the container address and the key for accessing the container are legal, and if so, stores the data sent by the server and the access ending identifier.
Preferably, if the number of threads created in S103 is greater than 1, in S105, the method further includes:
and when the thread of the client judges that the acquired access ending identifier is equal to a second preset value, the access ending identifier equal to the second preset value is sent to other threads, and then the life cycle of the threads is ended.
Preferably, the thread processing capability refers to the amount of data that can be processed by each thread at one time, and the amount of data that the server acquires from the database at one time is equal to the amount of data that can be processed by each thread at one time.
In another aspect, the invention provides a data interaction system, which includes a client, a server and a container according to a data interaction method.
As can be seen from the above description of the present invention, compared with the prior art, the present invention has the following advantages:
the invention relates to a data interaction method and a data interaction system, which comprise three devices, namely a client, a server and a container, wherein the client and the server finish data interaction through two times of handshake; through the implementation method, on one hand, the client side does not need to wait for data returned by the server side for a long time, so that the access efficiency of the client side is improved; in the second aspect, the server end starts the actual data fetching work from the data after the confirmation of the client end is obtained, so that the resources of the server end are saved, and the burden of the server end is lightened; and in the third aspect, the client starts a plurality of threads according to the data volume returned by the server, and recovers thread resources after the data is received, without being in a running state all the time, thereby ensuring that the thread resources are not wasted and saving client resources.
The above description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the description of the technical means more comprehensible.
The above and other objects, advantages and features of the present invention will become more apparent to those skilled in the art from the following detailed description of specific embodiments thereof, taken in conjunction with the accompanying drawings.
Drawings
FIG. 1 is a flow chart of a data interaction method of the present invention;
FIG. 2 is a block diagram of a data interaction method of the present invention;
FIG. 3 is a flow chart of a client process of the present invention;
fig. 4 is a flow chart of the server-side process of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Referring to fig. 1 to 4, in one aspect, a data interaction method according to the present invention includes:
s101, a client sends a first request message comprising container information and access conditions to a server;
s102, the server receives the first request message and verifies whether the first request message is legal or not; if the data is legal, acquiring the number of the data meeting the access condition from a database according to the access condition, and returning a first response message comprising the number of the data and the access identifier to the client;
s103, the client receives the first response message, judges whether the quantity taking identifier is equal to a first preset value or not, and if so, acquires the number of the data pieces; creating a thread for monitoring the data in the container and the processing capacity of a configuration thread according to the number of the data; and sending a second request message including thread processing capabilities to the server;
s104, the server receives the second request message, and obtains data meeting the access condition from a database page according to the access number and the thread processing capacity; sending a request message including the data acquired each time and the corresponding access ending identifier to the container;
s105, when the thread of the client monitors that the container has data, acquiring the data and judging whether the corresponding access ending identifier is equal to a second preset value or not, and if not, continuing to monitor; if so, the monitoring is ended.
The client, server and container are disposed on a computer device. In a specific implementation, the client is deployed independently, and the server and the container may be deployed on the same computer device or on different computer devices.
In this embodiment, before data interaction is performed, the server develops a corresponding data interface according to an access condition agreed with the client, so as to meet an access requirement of the client during subsequent data interaction. The access condition can be understood as data which is queried by the server side in the database and takes the access condition as a unique identifier.
Specifically, the data interaction between the client and the server is specifically applied to data interaction of a forklift. Correspondingly, a contract data interface, a forklift data interface, a client data interface and the like are developed on the server. When the data interface is a contract data interface, the access condition can be a contract creation date, a contract number, a contract modification date and the like; when the data interface is a forklift data interface, the access condition can be a forklift data modification date or a forklift number and the like; when the data interface is a client data interface, the access condition may be a client number or a client data modification date, etc.
Specifically, referring to fig. 2, the two-way handshake between the client and the server mainly includes:
1, the client sends a request to a server (before sending the request, a data fetching condition is set according to a data fetching condition agreed by the server, the request carries relevant information of a container, and in order to save resources, the relevant information of the container is sent to the server only in the first step of two handshaking);
2, when the server receives the request of the client, it needs to verify whether the request in step 1 is legal (i.e. whether the client has corresponding authority), if so, the server stores container information (set as CI, which can be customized) and a data fetching condition (DC), and according to the data fetching condition DC, obtains the number of data strips (i.e. data volume, which only fetches data volume, does not fetch data content, such as 1 hundred million data strips, which only returns 1 hundred million numbers, and is set as TN) meeting the DC from a database, and returns a data fetching identifier (G01) and a data strip number TN to the client according to a certain format, wherein the data fetching identifier G01 is set as a first preset value such as 0 when success, the data fetching identifier G01 is set as not equal to the first preset value such as 1 when failure, and the data strip number TN is set as 0;
3 and 4, after receiving a return value of the server, the client acquires a fetch identifier, and if the fetch identifier is 0 and then reads the data number TN, a certain number of threads are created according to the specific data number TN to monitor a container corresponding to the container information CI (the number of threads needs to be set according to the configuration of the system, which is not too large, wastes too many resources, and affects efficiency too little, for example, the data number TN is 1, one thread processes 1 ten thousand of data for about 1 second, where 10 threads are reasonably started, 10 threads work simultaneously, that is, 1s processes 10 ten thousand of data, and needs 1000s in total, that is, 15mins or so), and then the client returns the data size (thread processing capability PN) that can be processed by each thread once to the server (the related information of the container does not need to be sent in this step any more); simultaneously starting the monitoring of the container by the opened thread;
5, the server receives the thread processing capability PN returned by the client, acquires data from the database according to the access condition DC (here, specific content of the data is acquired, not the number of data pieces TN), and in order to improve efficiency, the access process needs to acquire the data in pages according to the number of data pieces TN and the thread processing capability PN, instead of fetching all TN data at one time, for example, the number of data pieces TN is 1 billion, and the thread processing capability PN is 1 ten thousand, so that the data can be fetched in 1 ten thousand times, and every ten thousand data are fetched, and the data and corresponding information (for example, an access end identifier F01 is spliced together and transmitted to a container corresponding to the CI if the server finishes accessing and sets the access end identifier to a second preset value 0 and does not finish setting the access end identifier to 1);
6. reading data when the thread started by the client monitors that the container has the data;
7. the client analyzes the received data, when the fact that the access ending identifier is equal to a second preset value 0 is analyzed, the client is informed of other access threads firstly, then the life cycle of the thread is ended, and after the other access threads receive notification messages among the threads, the life cycle of the thread is ended (under the condition that a plurality of threads are established by the client, if only one thread exists, the thread directly ends the life cycle of the thread when the fact that the access ending identifier is equal to the second preset value 0 is analyzed); and if the number taking ending identifier is equal to 1 after the analysis, continuing monitoring the data in the container and carrying out processing.
It should be noted that, after S101, the method may further include: and the server verifies the identity information of the client, receives and analyzes the first request message if the identity information of the client passes the verification, and discards the message if the identity information of the client does not pass the verification. Specifically, the identity information of the client may be a client IP address, a user name or a password.
Further, after receiving the first request message, the server verifies whether the first request message is legal according to the access condition. And if the access condition is legal, acquiring the number of the data pieces meeting the access condition from the database according to the access condition, and returning a first response message comprising the number of the data pieces and the access quantity identifier to the client. And if the access condition is illegal, judging that the first request message is illegal.
For example, in the fetching process, a fetching condition is date-related, the date format required by the server side is yy-mm-dd, and the fetching condition sent by the client side is yy/mm/dd, so that the fetching condition is illegal.
And if the first request message is illegal, setting the quantity taking identification to be not equal to a first preset value, and setting the data number to be 0. In this embodiment, the first preset value is set to 0; and if the first request message is illegal, setting the quantity taking identification to be 1.
If the first request message is legal, but the server acquires the number of data pieces meeting the number fetching condition from the database and is equal to 0, the number fetching identification is set to be not equal to the first preset value, and the number of the data pieces is set to be 0. That is, when the first request message is legal but the number of data pieces is equal to 0, the quantity taking identifier is also set to 1, and after the client reads the quantity taking identifier equal to 1, the client does not read the number of data pieces any more.
In addition, if the first request message is legal but the server fails to acquire the number of data pieces meeting the fetching condition from the database, the fetching amount identifier is set to be not equal to the first preset value, and the number of data pieces is set to be 0. Namely, the first request message is legal, but the corresponding access condition does not exist or the server fails to access the database using the corresponding access condition, the access identifier is also set to 1, and after the client reads the access identifier equal to 1, the client does not read the number of data.
Further, the container is a queue or a stack; the container information includes a container name, a container address, and a key to access the container.
The data request message sent by the server to the container includes one or more items of the container name, the container address, and the key for accessing the container, and may specifically be agreed with the container.
Based on the above description, the S104 further includes: and after receiving the request message sent by the server, the container verifies whether one or more items in the container name, the container address and the key for accessing the container are legal, and if so, stores the data sent by the server and the access ending identifier.
It is understood that the client stores the container information of the container, including the container name, the container address, and the key for accessing the container. Correspondingly, after receiving the first request message, the server stores the container information, and a data request message sent to a container in the following includes one or more items of the container name, the container address and a key for accessing the container, so that the container is authenticated. Typically, the container verifies a key for accessing the container, which may be generated using any of the existing methods.
Further, if the number of threads created in S103 is greater than 1, in S105, the method further includes:
and when the thread of the client judges that the acquired access ending identifier is equal to a second preset value, the access ending identifier equal to the second preset value is sent to other threads, and then the life cycle of the threads is ended. Specifically, as illustrated at 7 in fig. 2.
Further, the thread processing capability refers to the amount of data that can be processed by each thread at one time, and the amount of data that the server acquires from the database at one time is equal to the amount of data that can be processed by each thread at one time. In doing so, the server may be read by one thread once each time the amount of data retrieved from the database is placed in the container. If the data volume acquired by the server from the database each time is larger than the data volume which can be processed by one thread at a time, the data read by one thread may not contain the fetching end identifier, so that the thread cannot judge whether the fetching is ended.
In another aspect, the invention provides a data interaction system, which includes a client, a server and a container according to a data interaction method. The specific implementation and working process of the client, the server and the container are as described in a data interaction method, and a repeated description is not repeated in this embodiment.
Finally, it should be further noted that, in the present embodiment, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element. In addition, the above step identifiers are only for convenience of reading, and the steps can be correspondingly adjusted in specific implementation.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A method for data interaction, comprising:
s101, a client sends a first request message comprising container information and access conditions to a server;
s102, the server receives the first request message and verifies whether the first request message is legal or not; if the data is legal, acquiring the number of the data meeting the access condition from a database according to the access condition, and returning a first response message comprising the number of the data and the access identifier to the client;
s103, the client receives the first response message, judges whether the quantity taking identifier is equal to a first preset value or not, and if so, acquires the number of the data pieces; creating a thread for monitoring the data in the container and the processing capacity of a configuration thread according to the number of the data; and sending a second request message including thread processing capabilities to the server;
s104, the server receives the second request message, and obtains data meeting the access condition from a database page according to the access condition and the thread processing capacity; sending a request message including the data acquired each time and the corresponding access ending identifier to the container;
s105, when the thread of the client monitors that the container has data, acquiring the data and judging whether the corresponding access ending identifier is equal to a second preset value or not, and if not, continuing to monitor; if so, the monitoring is ended.
2. The data interaction method according to claim 1, wherein the server verifies whether the first request message is legal according to the access condition after receiving the first request message.
3. The data interaction method of claim 1, wherein if the first request message is illegal, the fetch flag is set not equal to the first preset value, and the number of data pieces is set to 0.
4. The data interaction method of claim 1, wherein if the first request message is legal but the server obtains the number of data pieces satisfying the fetching condition from the database equal to 0, the fetching amount flag is set not equal to the first preset value and the number of data pieces is set to 0.
5. The data interaction method of claim 1, wherein if the first request message is legal but the server fails to obtain the number of data pieces satisfying the fetching condition from the database, the fetching amount flag is set not equal to the first preset value and the number of data pieces is set to 0.
6. The data interaction method of claim 1, wherein the container is a queue or a stack; the container information includes a container name, a container address, and a key to access the container.
7. The data interaction method of claim 6, wherein the S104 further comprises: and after receiving the request message sent by the server, the container verifies whether one or more items in the container name, the container address and the key for accessing the container are legal, and if so, stores the data sent by the server and the access ending identifier.
8. The data interaction method according to claim 1, wherein if the number of threads created in S103 is greater than 1, in S105, the method further comprises:
and when the thread of the client judges that the acquired access ending identifier is equal to a second preset value, the access ending identifier equal to the second preset value is sent to other threads, and then the life cycle of the threads is ended.
9. The data interaction method of claim 1, wherein the thread processing capability refers to the amount of data that can be processed by each thread at one time, and the amount of data that the server can obtain from the database at one time is equal to the amount of data that can be processed by each thread at one time.
10. A data interaction system comprising a client, a server and a container in the method of claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910942380.3A CN110808956B (en) | 2019-09-30 | 2019-09-30 | Data interaction method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910942380.3A CN110808956B (en) | 2019-09-30 | 2019-09-30 | Data interaction method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110808956A CN110808956A (en) | 2020-02-18 |
| CN110808956B true CN110808956B (en) | 2021-09-17 |
Family
ID=69488056
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910942380.3A Active CN110808956B (en) | 2019-09-30 | 2019-09-30 | Data interaction method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110808956B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113973093B (en) * | 2020-07-24 | 2023-10-13 | 中移(苏州)软件技术有限公司 | Data transmission method and device, electronic equipment and readable storage medium |
| CN113704580A (en) * | 2021-08-27 | 2021-11-26 | 中国工商银行股份有限公司 | Information security interaction method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101188570A (en) * | 2006-11-17 | 2008-05-28 | 鸿富锦精密工业（深圳）有限公司 | Instant message processing system and method |
| CN107015850A (en) * | 2016-01-28 | 2017-08-04 | 博雅网络游戏开发（深圳）有限公司 | Thread scheduling method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120144123A1 (en) * | 2010-12-01 | 2012-06-07 | International Business Machines Corporation | Read-ahead processing in networked client-server architecture |
-
2019
- 2019-09-30 CN CN201910942380.3A patent/CN110808956B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101188570A (en) * | 2006-11-17 | 2008-05-28 | 鸿富锦精密工业（深圳）有限公司 | Instant message processing system and method |
| CN107015850A (en) * | 2016-01-28 | 2017-08-04 | 博雅网络游戏开发（深圳）有限公司 | Thread scheduling method and device |
Non-Patent Citations (1)
| Title |
|---|
| "Web应用与其Dockerize后的研究分析";张雷;《电子设计工程》;20180720;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110808956A (en) | 2020-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11233819B2 (en) | Method and apparatus for analyzing cyberattack | |
| CN105611330B (en) | Smart television maintenance method and system, server and mobile terminal | |
| CN103795580B (en) | A kind of data monitoring method, system and relevant device | |
| CN110781070B (en) | Big data test verification method and device, computer equipment and storage medium | |
| CN110808956B (en) | Data interaction method and system | |
| CN112231219A (en) | Automatic test monitoring method, device, equipment and storage medium | |
| CN103034735A (en) | Big data distributed file export method | |
| CN110798445B (en) | Public gateway interface testing method and device, computer equipment and storage medium | |
| CN112035437B (en) | Transmission method and device for medical records data, computer equipment and storage medium | |
| CN103856467A (en) | Method and distributed system for achieving safety scanning | |
| KR20180074774A (en) | How to identify malicious websites, devices and computer storage media | |
| CN108446172B (en) | Data calling method and device, computer equipment and storage medium | |
| CN112468416B (en) | Network flow mirroring method and device, computer equipment and storage medium | |
| CN108173839B (en) | Authority management method and system | |
| CN110661829A (en) | File downloading method and device, client and computer readable storage medium | |
| CN111898036B (en) | Behavior data collecting and processing system and method | |
| CN114615258A (en) | Method and device for uploading large files to file server in fragmented manner | |
| CN111506496A (en) | Test data acquisition method and device, electronic equipment and storage medium | |
| CN111294257B (en) | Method, device and system for automatic pressure test of application server | |
| CN113596105B (en) | Content acquisition method, edge node and computer readable storage medium | |
| CN106161611B (en) | The system and method that platform uploads and obtains image are broadcast live | |
| CN110362464B (en) | Software analysis method and equipment | |
| JP4943759B2 (en) | Link information management system, link information management method, and link information management program | |
| CN108984285B (en) | Data collision flow analysis method and device, storage medium and terminal | |
| CN117193907B (en) | Page processing method and device |
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 |