CN110209888A - The storage method and device of interface requests - Google Patents
The storage method and device of interface requests Download PDFInfo
- Publication number
- CN110209888A CN110209888A CN201910381771.2A CN201910381771A CN110209888A CN 110209888 A CN110209888 A CN 110209888A CN 201910381771 A CN201910381771 A CN 201910381771A CN 110209888 A CN110209888 A CN 110209888A
- Authority
- CN
- China
- Prior art keywords
- interface requests
- deposited
- interface
- stored
- requests
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
Abstract
The disclosure is directed to the storage method of interface requests and devices.This method comprises: obtaining interface requests to be deposited；According to the interface requests to be deposited, the corresponding URL of the interface requests to be deposited, request type and required parameter are obtained；The argument structure mark of the interface requests to be deposited is determined according to the required parameter；It is not stored in flow library to have when identifying interface requests all the same with the URL, request type and argument structure wait deposit interface requests, the interface requests to be deposited are stored in the flow library；Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.The technical solution can be to avoid a large amount of identical interface requests of storage, storage pressure is reduced, it is also possible to which the interface requests of different business scene are stored, the interface requests that different parameters logic can be thus stored with least memory space, cover more business scenarios.
Description
Technical field
This disclosure relates to the storage method and device of field of computer technology more particularly to interface requests.
Background technique
Network scenarios reproduction is an emerging research direction being gradually taken seriously in recent years, and key problem is to reproduce symbol
Close the flow of live network scene.Network scenarios reproduces research and is of great significance for fields such as network interface tests.
It is to record tool by flow to record flow true on network that network scenarios, which reproduces mostly, at present, then with flowing
The flow of recording is played back out by amount replay tool.In conventional flow recording scheme, it will usually flow is all stored or
Person part stores, if by flow, all storage then wastes the memory space of terminal, if flow part storage can then be made
The flow of some interface scenes is not recorded.
Summary of the invention
The embodiment of the present disclosure provides the storage method and device of a kind of interface requests.The technical solution is as follows:
According to the first aspect of the embodiments of the present disclosure, a kind of storage method of interface requests is provided, comprising:
Obtain interface requests to be deposited；
According to the interface requests to be deposited, the corresponding URL of the interface requests to be deposited, request type and request ginseng are obtained
Number；
The argument structure mark of the interface requests to be deposited is determined according to the required parameter；
It is not stored in flow library to have with the URL, request type and argument structure of the interface requests to be deposited mark homogeneously
With interface requests when, the interface requests to be deposited are stored in the flow library；
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
In one embodiment, the argument structure mark that the interface requests to be deposited are determined according to the required parameter
Know, comprising:
Obtain each key value of the required parameter of the interface requests to be deposited；
Each key value is spliced into character string, Hash calculation is carried out to the character string, obtains argument structure Hash
Value.
In one embodiment, the interface requests to be deposited include the request of hypertext transfer protocol HTTP interface.
In one embodiment, the method also includes:
While storing the interface requests to be deposited in the flow library, storage is described in the flow library connects wait deposit
Mouth requests corresponding URL, request type and argument structure mark.
In one embodiment, the method also includes:
It is stored in flow library all the same with the URL, request type and argument structure of the interface requests to be deposited mark
Interface requests when, abandon the interface requests to be deposited.
According to the second aspect of an embodiment of the present disclosure, a kind of storage device of interface requests is provided, comprising:
First obtains module, for obtaining interface requests to be deposited；
Second obtains module, for according to the interface requests to be deposited, obtain the corresponding URL of the interface requests to be deposited,
Request type and required parameter；
Determining module, for determining that the argument structure of the interface requests to be deposited identifies according to the required parameter；
First memory module, in flow library it is not stored have with the URL of the interface requests to be deposited, request type and
When argument structure identifies interface requests all the same, the interface requests to be deposited are stored in the flow library；
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
In one embodiment, the determining module includes:
Acquisition submodule, each key value of the required parameter for obtaining the interface requests to be deposited；
Computational submodule carries out Hash calculation to the character string, obtains for each key value to be spliced into character string
To argument structure cryptographic Hash.
In one embodiment, the interface requests to be deposited include the request of hypertext transfer protocol HTTP interface.
In one embodiment, described device further include:
Second memory module, while for storing the interface requests to be deposited in the flow library, in the flow
The corresponding URL of the interface requests to be deposited, request type and argument structure mark are stored in library.
In one embodiment, described device further include:
Discard module, for being stored with URL, request type and parameter knot with the interface requests to be deposited in flow library
When structure identifies interface requests all the same, the interface requests to be deposited are abandoned.
According to the third aspect of an embodiment of the present disclosure, a kind of storage device of interface requests is provided, comprising:
Processor；
Memory for storage processor executable instruction；
Wherein, the processor is configured to executing the step in the above method.
According to a fourth aspect of embodiments of the present disclosure, a kind of computer readable storage medium is provided, computer is stored with and refers to
It enables, the step in the above method is realized when the computer instruction is executed by processor.
The technical scheme provided by this disclosed embodiment can include the following benefits: the present embodiment can be according to acquisition
Interface requests to be deposited, obtain the corresponding URL of the interface requests to be deposited, request type and required parameter；According to the request
Parameter determines the argument structure mark of the interface requests to be deposited；In this way, not stored only in flow library can have and institute
When stating the URL wait deposit interface requests, request type and argument structure and identifying interface requests all the same, just in the flow library
The interface requests to be deposited are stored, avoids storing a large amount of identical interface requests, storage pressure is reduced, it is also possible to will not
Interface requests with business scenario store, and the interface of different parameters logic can be thus stored with least memory space
Request, covers more business scenarios.
It should be understood that above general description and following detailed description be only it is exemplary and explanatory, not
The disclosure can be limited.
Detailed description of the invention
The drawings herein are incorporated into the specification and forms part of this specification, and shows the implementation for meeting the disclosure
Example, and together with specification for explaining the principles of this disclosure.
Fig. 1 is a kind of flow chart of the storage method of interface requests shown according to an exemplary embodiment.
Fig. 2 is a kind of flow chart of the storage method of interface requests shown according to an exemplary embodiment.
Fig. 3 is a kind of block diagram of the storage device of interface requests shown according to an exemplary embodiment.
Fig. 4 is a kind of block diagram of the storage device of interface requests shown according to an exemplary embodiment.
Fig. 5 is a kind of block diagram of the storage device of interface requests shown according to an exemplary embodiment.
Fig. 6 is a kind of block diagram of the storage device of interface requests shown according to an exemplary embodiment.
Fig. 7 is a kind of block diagram of the storage device of interface requests shown according to an exemplary embodiment.
Specific embodiment
Example embodiments are described in detail here, and the example is illustrated in the accompanying drawings.Following description is related to
When attached drawing, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements.Following exemplary embodiment
Described in embodiment do not represent all implementations consistent with this disclosure.On the contrary, they be only with it is such as appended
The example of the consistent device and method of some aspects be described in detail in claims, the disclosure.
Fig. 1 is a kind of flow chart of the storage method of interface requests shown according to an exemplary embodiment, such as Fig. 1 institute
To show, the storage method of the interface requests can be used in server, include the following steps 101-104:
In a step 101, interface requests to be deposited are obtained.
Here, plug-in unit can be installed in client, crawl module etc., the plug-in unit or crawl module can timing by client
It holds each interface requests sent to be reported to server, it is to be stored to determine whether the interface requests need by server, this
These are needed to determine whether that stored interface requests are known as interface requests to be deposited in embodiment.
In a step 102, according to the interface requests to be deposited, the corresponding URL of the interface requests to be deposited, request class are obtained
Type and required parameter.
Here, server is being got after depositing interface requests, can be waited depositing from this and is got URL in interface requests
(Uniform Resource Locator, uniform resource locator), request type and required parameter.The URL is that should connect wait deposit
The address of mouth request requested resource, server directly can wait depositing from this obtains URL in interface requests.The type of the request
It mainly include the types such as POST (submissions) class, GET (acquisition) class, PUT (upload) class, wherein GET class is requested for specific
Resource issues request；POST class request for specified resource submit data carry out processing request (such as submission form or
Transmitting file), data are comprised in request body；PUT class is requested for uploading its what be new to specified resource location.Server
Request.getMethod () method acquisition request type can be passed through.Required parameter is mainly used to allow server and obtains
Context data, and based on context data are the request feedback response, exemplary, the required parameter in the request of GET class is usual
It all writes in URL, the required parameter in the request of GET class can be obtained by getQueryString method；POST class is asked
Parameter can be put into Request body (request body) the inside by asking, and can be got parms POST by getInputStream method
Required parameter in the request of class.
In step 103, determine that the argument structure of the interface requests to be deposited identifies according to the required parameter.
Here, different interface requests due to the content of request it is different, therefore the number of required parameter and type are all different,
Server can determine the argument structure of interface requests to be deposited according to the required parameter of acquisition, obtain the interface requests to be deposited
Argument structure mark.
At step 104, not stored URL, request type and the parameter having with the interface requests to be deposited in flow library
When structural identification interface requests all the same, interface requests to be deposited and the corresponding URL are stored in the flow library, is asked
Type and argument structure is asked to identify.
Here, it is stored in the flow library of server and has deposited the corresponding URL of interface requests, request type and argument structure mark
Know, server can be with query flows library, if not having URL, the request type of storage with the interface requests to be deposited in the flow library
When identifying interface requests all the same with argument structure, show not stored in server have at same resource address to same class
Shape parameter requests the interface requests of same treatment, at this point, requesting same to play back identical business scenario later
When carrying out same treatment to same type parameter at resource address, server needs storage is described in the flow library to connect wait deposit
Mouth request.
What needs to be explained here is that the storage is empty in the persistent storage space for the server that the flow library can store
Between including but not limited to database, file, caching etc..
The present embodiment can obtain the corresponding URL of the interface requests to be deposited, request according to the interface requests to be deposited of acquisition
Type and required parameter；The argument structure mark of the interface requests to be deposited is determined according to the required parameter；In this way,
Only in flow library it is not stored have identified with URL, request type and the argument structure of the interface requests to be deposited it is all the same
When interface requests, the interface requests to be deposited just are stored in the flow library, are avoided storing a large amount of identical interface requests, be subtracted
Pressure is stored less, it is also possible to which the interface requests of different business scene are stored, can thus use least storage
Space stores the interface requests of different parameters logic, covers more business scenarios.
In a kind of possible embodiment, it can be implemented as in the storage method of above-mentioned interface requests in step 103
Following steps A1 to A2.
In step A1, each key value of the required parameter of the interface requests to be deposited is obtained；
In step A2, each key value is spliced into character string, Hash calculation is carried out to the character string, is joined
Table structure cryptographic Hash.
Here, the required parameter that server is got is substantially Key Value (key-value) structure, and server can obtain
All key values of required parameter are taken, and these key values are spliced into a character string, Hash calculation is carried out to the character string, is obtained
To argument structure cryptographic Hash structure_params_hash.The binary value of random length can be mapped as by Hash calculation
The binary value of shorter regular length, this small binary value are known as cryptographic Hash, and cryptographic Hash is that one piece of data is unique and pole
Its compact numerical value representation, if hashing a Duan Mingwen and even only changing a letter of the paragraph, subsequent Kazakhstan
It is uncommon all to generate different values；Therefore server carries out the argument structure obtained after Hash calculation to the character string that key value is spliced into
Cryptographic Hash can be the unique identification of the argument structure of the required parameter.
Each key value of the required parameter of the available interface requests to be deposited of the present embodiment；Each key value is spliced
At character string, Hash calculation is carried out to the character string, argument structure cryptographic Hash is obtained as argument structure mark, realizes letter
It is single.
In a kind of possible embodiment, in the storage method of above-mentioned interface requests, the interface requests to be deposited include
The request of hypertext transfer protocol HTTP interface.
In a kind of possible embodiment, the storage method of above-mentioned interface requests can also include the following steps B1.
In step bl is determined, while the interface requests to be deposited are stored in the flow library, the interface to be deposited is stored
Request corresponding URL, request type and argument structure mark.
Here, server is while storing interface requests to be deposited, can also by the corresponding URL of the interface requests to be deposited,
Request type and argument structure mark also are stored in flow library, in this way, when getting URL, request type and parameter subsequent
Structural identification is all the same when depositing interface requests, and server can determine to have at same resource address accordingly to same
The interface requests of type parameter request same treatment are stored, and server would not store the interface requests again at this time, facilitate
Subsequent server decides whether to storage should interface requests be deposited.
The present embodiment can be while storing the interface requests to be deposited in the flow library, and storage is described to be connect wait deposit
Mouthful corresponding URL, request type and argument structure mark are requested, facilitates server and decide whether to store and subsequent connect wait deposit
Mouth request.
In a kind of possible embodiment, the storage method of above-mentioned interface requests can also include the following steps C1.
In step C1, URL, request type and the argument structure with the interface requests to be deposited are stored in flow library
When identifying interface requests all the same, the interface requests to be deposited are abandoned.
Here, server is stored with URL, request type and argument structure with the interface requests to be deposited in flow library
When identifying interface requests all the same, shows to have same type parameter request same treatment is connect at same resource address
Mouthful request is stored, and be can be used and stored is asked at same resource address to same type parameter with the interface requests to be deposited
The interface requests of same treatment are sought to carry out flow playback, therefore server can abandon the interface requests to be deposited.
The present embodiment can be stored with URL, request type and parameter knot with the interface requests to be deposited in flow library
When structure identifies interface requests all the same, the interface requests to be deposited are abandoned, the interface requests of identical services scene can be filtered
It removes, the interface requests of different parameters logic can be stored with least memory space, cover more business scenarios.
Realization process is discussed in detail below by several embodiments.
Fig. 2 is a kind of flow chart of the storage method of interface requests shown according to an exemplary embodiment, such as Fig. 2 institute
Show, the storage method of the interface requests can be realized by equipment such as servers, including step 201-207.
In step 201, interface requests to be deposited are obtained, the interface requests to be deposited include that hypertext transfer protocol HTTP connects
Mouth request.
In step 202, according to the interface requests to be deposited, the corresponding URL of the interface requests to be deposited, request class are obtained
Type and required parameter.
In step 203, each key value of the required parameter of the interface requests to be deposited is obtained.
In step 204, each key value is spliced into character string, Hash calculation is carried out to the character string, is joined
Table structure cryptographic Hash.
In step 205, not stored URL, request type and the parameter having with the interface requests to be deposited in flow library
When structural identification interface requests all the same, the interface requests to be deposited are stored in the flow library.
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
In step 206, it while the interface requests to be deposited are stored in the flow library, is deposited in the flow library
Store up the corresponding URL of the interface requests to be deposited, request type and argument structure mark.
In step 207, the URL, request type and parameter knot with the interface requests to be deposited are stored in flow library
When structure identifies interface requests all the same, the interface requests to be deposited are abandoned.
Following is embodiment of the present disclosure, can be used for executing embodiments of the present disclosure.
Fig. 3 is a kind of block diagram of the storage device of interface requests shown according to an exemplary embodiment, which can be with
Pass through being implemented in combination with as some or all of of electronic equipment for software, hardware or both.As shown in figure 3, the interface is asked
The storage device asked includes:
First obtains module 301, for obtaining interface requests to be deposited；
Second obtains module 302, for it is corresponding to obtain the interface requests to be deposited according to the interface requests to be deposited
URL, request type and required parameter；
Determining module 303, for determining that the argument structure of the interface requests to be deposited identifies according to the required parameter；
First memory module 304 has and the URL of the interface requests to be deposited, request class for not stored in flow library
When type and argument structure identify interface requests all the same, the interface requests to be deposited are stored in the flow library；
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
As a kind of possible embodiment, Fig. 4 is a kind of storage of interface requests shown according to an exemplary embodiment
The block diagram of device, as shown in figure 4, the storage device of interface requests disclosed above can also be configured to determining module 303 to wrap
Include acquisition submodule 3031 and computational submodule 3032, in which:
Acquisition submodule 3031, each key value of the required parameter for obtaining the interface requests to be deposited；
Computational submodule 3032 carries out Hash meter to the character string for each key value to be spliced into character string
It calculates, obtains argument structure cryptographic Hash.
As a kind of possible embodiment, in the storage device of interface requests disclosed above, the interface requests to be deposited
It is requested including hypertext transfer protocol HTTP interface.
As a kind of possible embodiment, Fig. 5 is a kind of storage of interface requests shown according to an exemplary embodiment
The block diagram of device, as shown in figure 5, the storage device of interface requests disclosed above can be configured to include the second storage mould
Block 305, in which:
Second memory module 305, while for storing the interface requests to be deposited in the flow library, in the stream
It measures and stores the corresponding URL of the interface requests to be deposited, request type and argument structure mark in library.
As a kind of possible embodiment, Fig. 6 is a kind of storage of interface requests shown according to an exemplary embodiment
The block diagram of device, as shown in fig. 6, the storage device of interface requests disclosed above can be configured to include discard module
306, in which:
Discard module 306, for being stored with URL, request type and ginseng with the interface requests to be deposited in flow library
When table structure identifies interface requests all the same, the interface requests to be deposited are abandoned.
About the device in above-described embodiment, wherein modules execute the concrete mode of operation in related this method
Embodiment in be described in detail, no detailed explanation will be given here.
Fig. 7 is a kind of block diagram of the storage device of interface requests shown according to an exemplary embodiment.For example, device
700 may be provided as a server.Device 700 includes processing component 711, further comprises one or more processors,
And the memory resource as representated by memory 712, it can be by the instruction of the execution of processing component 711 for storing, such as answer
Use program.The application program stored in memory 712 may include it is one or more each correspond to one group of instruction
Module.In addition, processing component 711 is configured as executing instruction, to execute the above method.
Device 700 can also include the power management that a power supply module 713 is configured as executive device 700, and one has
Line or radio network interface 714 are configured as device 700 being connected to network and input and output (I/O) interface 715.Dress
Setting 700 can operate based on the operating system for being stored in memory 712, such as Windows ServerTM, Mac OS XTM,
UnixTM, LinuxTM, FreeBSDTM or similar.
A kind of non-transitorycomputer readable storage medium, when the instruction in the storage medium is by the processing of device 700
When device executes, so that device 700 is able to carry out the storage method of above-mentioned interface requests, which comprises
Obtain interface requests to be deposited；
According to the interface requests to be deposited, the corresponding URL of the interface requests to be deposited, request type and request ginseng are obtained
Number；
The argument structure mark of the interface requests to be deposited is determined according to the required parameter；
It is not stored in flow library to have with the URL, request type and argument structure of the interface requests to be deposited mark homogeneously
With interface requests when, the interface requests to be deposited are stored in the flow library；
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
In one embodiment, the argument structure mark that the interface requests to be deposited are determined according to the required parameter
Know, comprising:
Obtain each key value of the required parameter of the interface requests to be deposited；
Each key value is spliced into character string, Hash calculation is carried out to the character string, obtains argument structure Hash
Value.
In one embodiment, the interface requests to be deposited include the request of hypertext transfer protocol HTTP interface.
In one embodiment, the method also includes:
While storing the interface requests to be deposited in the flow library, storage is described in the flow library connects wait deposit
Mouth requests corresponding URL, request type and argument structure mark.
In one embodiment, the method also includes:
It is stored in flow library all the same with the URL, request type and argument structure of the interface requests to be deposited mark
Interface requests when, abandon the interface requests to be deposited.
The present embodiment additionally provides a kind of storage device of interface requests, comprising:
Processor；
Memory for storage processor executable instruction；
Wherein, the processor is configured to:
Obtain interface requests to be deposited；
According to the interface requests to be deposited, the corresponding URL of the interface requests to be deposited, request type and request ginseng are obtained
Number；
The argument structure mark of the interface requests to be deposited is determined according to the required parameter；
It is not stored in flow library to have with the URL, request type and argument structure of the interface requests to be deposited mark homogeneously
With interface requests when, the interface requests to be deposited are stored in the flow library；
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
In one embodiment, above-mentioned processor can be additionally configured to:
It is described to determine that the argument structure of the interface requests to be deposited identifies according to the required parameter, comprising:
Obtain each key value of the required parameter of the interface requests to be deposited；
Each key value is spliced into character string, Hash calculation is carried out to the character string, obtains argument structure Hash
Value.
In one embodiment, above-mentioned processor can be additionally configured to:
The interface requests to be deposited include the request of hypertext transfer protocol HTTP interface.
In one embodiment, above-mentioned processor can be additionally configured to:
The method also includes:
While storing the interface requests to be deposited in the flow library, storage is described in the flow library connects wait deposit
Mouth requests corresponding URL, request type and argument structure mark.
In one embodiment, above-mentioned processor can be additionally configured to:
The method also includes:
It is stored in flow library all the same with the URL, request type and argument structure of the interface requests to be deposited mark
Interface requests when, abandon the interface requests to be deposited.
Those skilled in the art will readily occur to its of the disclosure after considering specification and practicing disclosure disclosed herein
Its embodiment.This application is intended to cover any variations, uses, or adaptations of the disclosure, these modifications, purposes or
Person's adaptive change follows the general principles of this disclosure and including the undocumented common knowledge in the art of the disclosure
Or conventional techniques.The description and examples are only to be considered as illustrative, and the true scope and spirit of the disclosure are by following
Claim is pointed out.
It should be understood that the present disclosure is not limited to the precise structures that have been described above and shown in the drawings, and
And various modifications and changes may be made without departing from the scope thereof.The scope of the present disclosure is only limited by the accompanying claims.
Claims (12)
1. a kind of storage method of interface requests characterized by comprising
Obtain interface requests to be deposited；
According to the interface requests to be deposited, the corresponding URL of the interface requests to be deposited, request type and required parameter are obtained；
The argument structure mark of the interface requests to be deposited is determined according to the required parameter；
In flow library it is not stored have identified with URL, request type and the argument structure of the interface requests to be deposited it is all the same
When interface requests, the interface requests to be deposited are stored in the flow library；
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
2. the method according to claim 1, wherein described determine the interface to be deposited according to the required parameter
The argument structure of request identifies, comprising:
Obtain each key value of the required parameter of the interface requests to be deposited；
Each key value is spliced into character string, Hash calculation is carried out to the character string, obtains argument structure cryptographic Hash.
3. the method according to claim 1, wherein the interface requests to be deposited include hypertext transfer protocol
HTTP interface request.
4. the method according to claim 1, wherein the method also includes:
While storing the interface requests to be deposited in the flow library, the interface to be deposited is stored in the flow library and is asked
Ask corresponding URL, request type and argument structure mark.
5. the method according to claim 1, wherein the method also includes:
It is stored in flow library and identifies all the same connect with URL, request type and the argument structure of the interface requests to be deposited
When mouth request, the interface requests to be deposited are abandoned.
6. a kind of storage device of interface requests characterized by comprising
First obtains module, for obtaining interface requests to be deposited；
Second obtains module, for obtaining the corresponding URL of the interface requests to be deposited, request according to the interface requests to be deposited
Type and required parameter；
Determining module, for determining that the argument structure of the interface requests to be deposited identifies according to the required parameter；
First memory module, for URL, request type and the parameter having with the interface requests to be deposited not stored in flow library
When structural identification interface requests all the same, the interface requests to be deposited are stored in the flow library；
Wherein, it is stored in the flow library and has deposited the corresponding URL of interface requests, request type and argument structure mark.
7. device according to claim 6, which is characterized in that the determining module includes:
Acquisition submodule, each key value of the required parameter for obtaining the interface requests to be deposited；
Computational submodule carries out Hash calculation to the character string, is joined for each key value to be spliced into character string
Table structure cryptographic Hash.
8. device according to claim 6, which is characterized in that the interface requests to be deposited include hypertext transfer protocol
HTTP interface request.
9. device according to claim 6, which is characterized in that described device further include:
Second memory module, while for storing the interface requests to be deposited in the flow library, in the flow library
Store the corresponding URL of the interface requests to be deposited, request type and argument structure mark.
10. device according to claim 6, which is characterized in that described device further include:
Discard module, for being stored with URL, request type and argument structure mark with the interface requests to be deposited in flow library
When knowing interface requests all the same, the interface requests to be deposited are abandoned.
11. a kind of storage device of interface requests characterized by comprising
Processor；
Memory for storage processor executable instruction；
Wherein, the processor is configured to perform claim requires the step in any one of 1 to 5 the method.
12. a kind of computer readable storage medium, is stored with computer instruction, which is characterized in that the computer instruction is located
Manage the step realized in any one of claim 1 to 5 the method when device executes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910381771.2A CN110209888A (en) | 2019-05-08 | 2019-05-08 | The storage method and device of interface requests |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910381771.2A CN110209888A (en) | 2019-05-08 | 2019-05-08 | The storage method and device of interface requests |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110209888A true CN110209888A (en) | 2019-09-06 |
Family
ID=67785700
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910381771.2A Pending CN110209888A (en) | 2019-05-08 | 2019-05-08 | The storage method and device of interface requests |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110209888A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112015483A (en) * | 2020-08-07 | 2020-12-01 | 北京浪潮数据技术有限公司 | POST request parameter automatic processing method and device and readable storage medium |
| CN112765045A (en) * | 2021-04-07 | 2021-05-07 | 四川新网银行股份有限公司 | Case template-based flow playback method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103457993A (en) * | 2012-06-01 | 2013-12-18 | Sk电信有限公司 | Local caching device and method for providing content caching service |
| CN106331153A (en) * | 2016-09-20 | 2017-01-11 | 北京华为数字技术有限公司 | Service request filtering method, service request filtering device and service request filtering system |
| WO2017149592A1 (en) * | 2016-02-29 | 2017-09-08 | 株式会社日立製作所 | Storage device |
| CN108008918A (en) * | 2017-11-30 | 2018-05-08 | 联想(北京)有限公司 | Data processing method, memory node and distributed memory system |
| WO2018090703A1 (en) * | 2016-11-15 | 2018-05-24 | 杭州海康威视数字技术股份有限公司 | Data storage and deletion method and apparatus |
| CN109408761A (en) * | 2018-10-16 | 2019-03-01 | 翟红鹰 | A kind of filter method of repetitive requests, system, equipment and storage medium |
-
2019
- 2019-05-08 CN CN201910381771.2A patent/CN110209888A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103457993A (en) * | 2012-06-01 | 2013-12-18 | Sk电信有限公司 | Local caching device and method for providing content caching service |
| WO2017149592A1 (en) * | 2016-02-29 | 2017-09-08 | 株式会社日立製作所 | Storage device |
| CN106331153A (en) * | 2016-09-20 | 2017-01-11 | 北京华为数字技术有限公司 | Service request filtering method, service request filtering device and service request filtering system |
| WO2018090703A1 (en) * | 2016-11-15 | 2018-05-24 | 杭州海康威视数字技术股份有限公司 | Data storage and deletion method and apparatus |
| CN108008918A (en) * | 2017-11-30 | 2018-05-08 | 联想(北京)有限公司 | Data processing method, memory node and distributed memory system |
| CN109408761A (en) * | 2018-10-16 | 2019-03-01 | 翟红鹰 | A kind of filter method of repetitive requests, system, equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 吴昊: "网络流量回放***的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
| 时立锋 等: "基于数据去重的广域网络传输优化***研究", 《中国信通信》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112015483A (en) * | 2020-08-07 | 2020-12-01 | 北京浪潮数据技术有限公司 | POST request parameter automatic processing method and device and readable storage medium |
| CN112015483B (en) * | 2020-08-07 | 2021-12-03 | 北京浪潮数据技术有限公司 | POST request parameter automatic processing method and device and readable storage medium |
| CN112765045A (en) * | 2021-04-07 | 2021-05-07 | 四川新网银行股份有限公司 | Case template-based flow playback method |
| CN112765045B (en) * | 2021-04-07 | 2021-11-09 | 四川新网银行股份有限公司 | Case template-based flow playback method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8140580B2 (en) | Aggregating persisted operational data in a distributed environment | |
| EP2671360B1 (en) | Correlating input and output requests between client and server components in a multi-tier application | |
| CN108494755B (en) | Method and device for transmitting Application Programming Interface (API) request | |
| TWI354475B (en) | Dispatching client requests to appropriate server- | |
| JP2008538428A5 (en) | ||
| JP2019521576A (en) | Maintaining Messaging System Persistence | |
| CN109815025A (en) | Business model call method, device and storage medium | |
| CN107172177A (en) | A kind of information recommendation method and device | |
| CN110489315A (en) | A kind of tracking of operation requests, tracking device and server | |
| CN110209888A (en) | The storage method and device of interface requests | |
| CN111966967A (en) | Copyright storage method and system based on block chain technology and CDN | |
| CN105184559B (en) | A kind of payment system and method | |
| CN112463833A (en) | Data set acquisition method, system, device and medium | |
| WO2022134830A1 (en) | Method and apparatus for processing block node data, computer device, and storage medium | |
| CN109618187A (en) | A kind of acquisition methods and device of video data | |
| US11777852B1 (en) | System and method for web service atomic transaction (WS-AT) affinity routing | |
| CN113553206B (en) | Data event execution method and device, electronic equipment and computer readable medium | |
| CN113055350B (en) | Data transmission method, device, equipment and readable storage medium | |
| CN111131860A (en) | Audio and video playing method, device, equipment and medium | |
| CN106201942B (en) | By the associated method of event between computer equipment, equipment and system | |
| CN105991560B (en) | Audio/video communication method for network access and audio/video communication network access device | |
| CN113986955B (en) | Service chain determining method and device, electronic equipment and medium | |
| CN113301134B (en) | Error-tolerant cooperative decision method suitable for edge Internet of things agent device | |
| US9191438B2 (en) | Methods and apparatus for identifying peers on a peer-to-peer network | |
| CN108810609A (en) | A kind of memory management method, equipment and system |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190906 |