CN112433872A - Interface request timeout reminding method, system and storage medium - Google Patents
Interface request timeout reminding method, system and storage medium Download PDFInfo
- Publication number
- CN112433872A CN112433872A CN202011150176.7A CN202011150176A CN112433872A CN 112433872 A CN112433872 A CN 112433872A CN 202011150176 A CN202011150176 A CN 202011150176A CN 112433872 A CN112433872 A CN 112433872A
- Authority
- CN
- China
- Prior art keywords
- request
- interface
- global variable
- current
- time
- 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
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000003780 insertion Methods 0.000 claims abstract description 50
- 230000037431 insertion Effects 0.000 claims abstract description 50
- 238000004590 computer program Methods 0.000 claims description 10
- 239000000126 substance Substances 0.000 claims description 2
- 230000000977 initiatory effect Effects 0.000 abstract description 6
- 230000002159 abnormal effect Effects 0.000 abstract description 4
- 238000012545 processing Methods 0.000 description 8
- 230000001186 cumulative effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
- G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
- G06F11/0757—Error or fault detection not based on redundancy by exceeding limits by exceeding a time limit, i.e. time-out, e.g. watchdogs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
Abstract
The invention discloses a method, a system and a storage medium for reminding overtime of an interface request, wherein the method comprises the following steps: predefining a global variable for storing the request identifier; when an HTTP request sent by an interface is detected, a request identifier of the current interface is constructed according to a preset structure and is inserted into the global variable; starting a timer, performing polling traversal on all request identifications in the current global variable, judging whether the accumulated insertion time of each request identification is greater than the preset time, if so, deleting the request identification and sending an overtime prompt of a corresponding interface to the client. The embodiment of the invention can judge the request initiation time of each interface by intensively managing a plurality of interfaces which have sent HTTP requests in the global variable, immediately send overtime reminding to the client when the interface request is overtime, and timely remind the client that the current service is abnormal, thereby avoiding the inconvenience caused by the system being blocked and the use of the user due to the long-time interface request abnormity.
Description
Technical Field
The invention relates to the technical field of computer networks, in particular to an interface request timeout reminding method, an interface request timeout reminding system and a storage medium.
Background
Qt is a very wide technical framework applied in the current software development industry, can conveniently develop desktop application programs of Windows, mac and linux cross-platforms based on C + + language, developers often use a network module QNetworkAccess manager with rich functions at present, generally use the network module QNetworkAccess manager to realize the interaction of get and post requests of HTTP and background data, and when the network is normal, the data is completely normal to be transmitted and received. However, when the interface request is sent to the background through the QNetworkAccessManager, if the network is abnormal, the background server cannot timely reply the request result to the Qt client, and at this time, the existing module has no overtime reminding mechanism, which causes the request to be blocked, cannot remind the user, and cannot perform the subsequent service. At present, some developers realize the overtime processing function through a timer, but the technical implementation mode is very limited, a large number of concurrent interface requests cannot be met, and the efficiency is low.
Accordingly, the prior art is yet to be improved and developed.
Disclosure of Invention
In view of the above-mentioned deficiencies of the prior art, an object of the present invention is to provide a method, a system and a storage medium for reminding timeout of interface requests, which are used to solve the problem that multiple interface requests cannot be processed simultaneously in the prior art.
The technical scheme of the invention is as follows:
an interface request timeout reminding method comprises the following steps:
predefining a global variable for storing the request identifier;
when an HTTP request sent by an interface is detected, a request identifier of the current interface is constructed according to a preset structure and is inserted into the global variable;
starting a timer, performing polling traversal on all request identifications in the current global variable, judging whether the accumulated insertion time of each request identification is greater than the preset time, if so, deleting the request identification and sending an overtime prompt of a corresponding interface to the client.
In the interface request timeout reminding method, after the request identifier of the current interface is constructed according to a preset structure and inserted into the global variable every time when the HTTP request sent by the interface is detected, the method further includes:
and judging whether each interface receives a request result returned by the background server, and if so, deleting the request identifier corresponding to the interface which has received the request result in the global variable.
In the interface request timeout reminding method, when it is detected that the interface sends the HTTP request, the request identifier of the current interface is constructed according to a preset structure and inserted into the global variable, including:
continuously detecting whether each interface sends an HTTP request, if so, acquiring the name of the interface which currently sends the HTTP request and a current timestamp;
and constructing a request identifier of the current interface according to the interface name, the current timestamp and the accumulated insertion time, and inserting the request identifier into the global variable, wherein the initial value of the accumulated insertion time is 0.
In the interface request timeout reminding method, the starting of the timer and the polling traversal of all the request identifiers in the current global variable determine whether the accumulated insertion time of each request identifier is greater than a preset time, and if so, deleting the request identifier and sending the timeout reminding of the corresponding interface to the client, including:
starting a timer and performing polling traversal on all request identifiers in the current global variable;
and judging whether the accumulated insertion time of each request identifier is greater than the preset time during each polling pass, if so, deleting the request identifier and sending an overtime prompt of the corresponding interface to the client.
In the interface request timeout reminding method, the starting of the timer and the polling traversal of all the request identifiers in the current global variable include:
starting a timer to perform polling traversal on all request identifications in the current global variable according to preset interval time;
and updating the accumulated insertion time of each request identifier to T +1 after traversing once, wherein T is the current accumulated insertion time of each request identifier.
In the interface request timeout reminding method, the polling duration of each time judges whether the accumulated insertion time of each request identifier is greater than a preset time, if so, the request identifier is deleted and the timeout reminding of the corresponding interface is sent to the client, including:
acquiring the current accumulated insertion time of each request identifier during each polling;
and judging whether the current accumulated insertion time of each request identifier is greater than the preset time, if so, deleting the corresponding request identifier and sending an overtime prompt of the interface corresponding to the request identifier to the client.
In the interface request timeout reminding method, the preset interval time is 1 second.
The invention also provides an interface request timeout reminding system, which comprises at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the interface request timeout alerting method described above.
Another embodiment of the present invention also provides a non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the interface request timeout alerting method described above.
Yet another embodiment of the present invention provides a computer program product comprising a computer program stored on a non-volatile computer-readable storage medium, the computer program comprising program instructions that, when executed by a processor, cause the processor to perform the above-mentioned interface request timeout alerting method.
Has the advantages that: compared with the prior art, the embodiment of the invention can judge the request initiation time of each interface by centrally managing the interfaces which have sent HTTP requests in the global variable, immediately send overtime reminding to a client when the interface request is overtime, timely remind the client that the current service is abnormal, and avoid inconvenience for the user caused by system jamming due to long-time interface request abnormity.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
FIG. 1 is a flowchart illustrating a method for reminding an interface request timeout according to a preferred embodiment of the present invention;
fig. 2 is a schematic diagram of a hardware structure of a preferred embodiment of the interface request timeout reminding system according to the present invention.
Detailed Description
In order to make the objects, technical solutions and effects of the present invention clearer and clearer, the present invention is described in further detail below. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. Embodiments of the present invention will be described below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for reminding an interface request timeout according to a preferred embodiment of the present invention. As shown in fig. 1, it includes the following steps:
s100, predefining global variables for storing the request identification;
s200, when the HTTP request sent by the interface is detected, constructing a request identifier of the current interface according to a preset structure and inserting the request identifier into the global variable;
s300, starting a timer, performing polling traversal on all request identifiers in the current global variable, judging whether the accumulated insertion time of each request identifier is greater than preset time, if so, deleting the request identifiers and sending overtime reminders of corresponding interfaces to the client.
In this embodiment, the problem of request timeout processing of a large number of concurrent interfaces is solved by centrally managing all interface requests, and specifically, a global variable for storing a request identifier is predefined in advance; then, when an HTTP request sent by the interface is detected, a request identifier of the current interface is constructed according to a preset structure and is inserted into the global variable; and then starting a timer, performing polling traversal on all the request identifiers in the current global variable, judging whether the accumulated insertion time of each request identifier is greater than the preset time, if so, deleting the request identifiers and sending an overtime prompt of a corresponding interface to the client. The interface request timeout reminding method provided by the invention has the advantages that the request identification of the corresponding interface is inserted into the global variable when the QNetworkAccess manager module is used for sending the interface request every time, the duration time of each initiated HTTP request interface is identified through the accumulated insertion time of the request identification, when the interface request is overtime, the corresponding timeout reminding can be timely sent to the client, the current interface request of a user is effectively reminded of the abnormality, the overtime reminding of a plurality of concurrent interface requests can be realized through the polling traversal and accumulated insertion time judgment of all the request identifications, a timer is not required to be independently set for each interface, the efficiency of processing the overtime reminding of the interface request is greatly improved, and the memory resource is saved.
Further, when it is detected that the interface sends the HTTP request, after the request identifier of the current interface is constructed according to a preset structure and inserted into the global variable, the method further includes:
and judging whether each interface receives a request result returned by the background server, and if so, deleting the request identifier corresponding to the interface which has received the request result in the global variable.
In this embodiment, after it is detected that an interface sends an HTTP request and inserts a request identifier thereof into a global variable, a request return result of each interface needs to be determined, and if the current network is normal, each interface can normally receive a request result returned by a background server, and delete the request identifier corresponding to the interface that has received the request result in the global variable, that is, it is ensured that none of the interfaces corresponding to the request identifier in the global variable temporarily receives an interface that has not received the request result returned by the background server, thereby avoiding determining cumulative insertion time of the interfaces that have received the request result, and wasting memory resources, thereby effectively improving the efficiency of timeout processing of multiple parallel interface requests.
Further, when it is detected that the interface sends the HTTP request, the request identifier of the current interface is constructed according to a preset structure and inserted into the global variable, including:
continuously detecting whether each interface sends an HTTP request, if so, acquiring the name of the interface which currently sends the HTTP request and a current timestamp;
and constructing a request identifier of the current interface according to the interface name, the current timestamp and the accumulated insertion time, and inserting the request identifier into the global variable, wherein the initial value of the accumulated insertion time is 0.
In this embodiment, a plurality of interfaces are continuously detected, whether each interface sends an HTTP request is detected, specifically, each interface sends an HTTP request to a backend server through a QNetworkAccessManage module, when it is detected that an interface sends an HTTP request, an interface name and a current timestamp of the current sending request are immediately obtained, an interface and an initiating time of the sending request are clarified, then a request identifier of the current interface is constructed according to the interface name, the current timestamp and an accumulated insertion time and is inserted into the global variable, that is, the request identifier of each interface is composed of the interface name plus the current timestamp and the accumulated insertion time, an initial value of the accumulated insertion time is 0, the initiating time and the duration time of the sending request of the corresponding interface and the interface can be known through each request identifier, and a plurality of parallel interfaces are centrally managed through the request identifiers in the global variable, the efficient multi-interface overtime request reminding processing is realized, and the workload of developers is saved.
Further, the starting of the timer and the polling traversal of all the request identifiers in the current global variable determine whether the accumulated insertion time of each request identifier is greater than a preset time, and if so, deleting the request identifier and sending an overtime prompt of the corresponding interface to the client, including:
starting a timer and performing polling traversal on all request identifiers in the current global variable;
and judging whether the accumulated insertion time of each request identifier is greater than the preset time during each polling pass, if so, deleting the request identifier and sending an overtime prompt of the corresponding interface to the client.
In the embodiment, the timer is started and the polling traversal is performed on all the request identifiers in the global variable, each polling traversal judges whether the accumulated insertion time of each request identifier is greater than the preset time, the accumulated insertion time of the request identifiers is cleared when the request identifiers are inserted into the global variable, namely, the accumulated time is started after the request identifiers are inserted into the global variable, so that the accumulated insertion time in the request identifiers represents the request initiation duration of the corresponding interface, if the accumulated insertion time is greater than the preset time, the current corresponding interface has initiated the request for a certain time and does not receive the request result, in order to avoid the situation that a user cannot know that the interface is overtime to delay the subsequent service processing due to the system card death, the request identifier of the overtime interface is deleted in the global variable, and an overtime prompt is sent to the client, so that the user is prompted to have an overtime condition at present, the user can conveniently carry out debugging processing, and the normal operation of the system is ensured.
Further, the starting the timer and performing polling traversal on all request identifiers in the current global variable includes:
starting a timer to perform polling traversal on all request identifications in the current global variable according to preset interval time;
and updating the accumulated insertion time of each request identifier to T +1 after traversing once, wherein T is the current accumulated insertion time of each request identifier.
In this embodiment, after each interface sends an HTTP request to a background server and inserts its corresponding request identifier into a global variable, a timer is started to perform polling traversal on all request identifiers in a current global variable according to a preset interval time, all request identifiers are polled and traversed once at a certain interval, and the cumulative insertion time of each request identifier is updated after each traversal, specifically, the cumulative insertion time of each request identifier is updated to T +1 after each traversal, and T is the current cumulative insertion time of each request identifier, that is, 1 is added to the current cumulative insertion time of each request identifier every traversal, so as to represent the duration of the request initiated by each interface. In specific implementation, the preset interval time is 1 second, all the request identifiers inserted into the global variable are traversed once every 1 second, and 1 is added for updating the accumulated insertion time of each request identifier, so that subsequent timeout judgment is facilitated, and accurate parallel interface timeout reminding is realized.
Further, the polling duration of each time judges whether the accumulated insertion time of each request identifier is greater than the preset time, if so, the request identifier is deleted and the timeout reminder of the corresponding interface is sent to the client, including:
acquiring the current accumulated insertion time of each request identifier during each polling;
and judging whether the current accumulated insertion time of each request identifier is greater than the preset time, if so, deleting the corresponding request identifier and sending an overtime prompt of the interface corresponding to the request identifier to the client.
In this embodiment, when performing timeout determination, traversing all request identifiers in a current global variable once every second, acquiring current accumulated insertion time of each request identifier during each polling identifier, determining whether each acquired accumulated insertion time is greater than a preset time, if so, sending timeout prompt of interfaces corresponding to the timeout request identifiers to a client, and deleting the timeout request identifiers from the global variable, so that elements in the global variable are updated in real time while multiple parallel interfaces prompt in time for timeout, it is ensured that the request identifiers in the global variable correspond to interfaces which have not received a request result temporarily and have not timed out, data redundancy is not caused, and accuracy and timeliness of the timeout prompt are ensured.
Another embodiment of the present invention provides an interface request timeout reminding system, as shown in fig. 2, the system 10 includes:
one or more processors 110 and a memory 120, where one processor 110 is illustrated in fig. 2, the processor 110 and the memory 120 may be connected by a bus or other means, and the connection by the bus is illustrated in fig. 2.
The memory 120 is a non-volatile computer-readable storage medium, and can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions corresponding to the interface request timeout reminding method in the embodiment of the present invention. The processor 110 executes various functional applications and data processing of the system 10 by executing the nonvolatile software programs, instructions and units stored in the memory 120, that is, implementing the interface request timeout reminding method in the above method embodiments.
The memory 120 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the system 10, and the like. Further, the memory 120 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 120 optionally includes memory located remotely from processor 110, which may be connected to system 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
One or more units are stored in the memory 120, and when executed by the one or more processors 110, perform the interface request timeout alerting method in any of the above-described method embodiments, for example, perform the above-described method steps S100 to S300 in fig. 1.
Embodiments of the present invention provide a non-transitory computer-readable storage medium storing computer-executable instructions for execution by one or more processors, for example, to perform method steps S100-S300 of fig. 1 described above.
By way of example, non-volatile storage media can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as Synchronous RAM (SRAM), dynamic RAM, (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The disclosed memory components or memory of the operating environment described herein are intended to comprise one or more of these and/or any other suitable types of memory.
Another embodiment of the present invention provides a computer program product comprising a computer program stored on a non-volatile computer-readable storage medium, the computer program comprising program instructions which, when executed by a processor, cause the processor to perform the interface request timeout alerting method of the above-described method embodiment. For example, the method steps S100 to S300 in fig. 1 described above are performed.
In summary, in the interface request timeout reminding method, system and storage medium disclosed in the present invention, the method includes: predefining a global variable for storing the request identifier; when an HTTP request sent by an interface is detected, a request identifier of the current interface is constructed according to a preset structure and is inserted into the global variable; starting a timer, performing polling traversal on all request identifications in the current global variable, judging whether the accumulated insertion time of each request identification is greater than the preset time, if so, deleting the request identification and sending an overtime prompt of a corresponding interface to the client. The embodiment of the invention can judge the request initiation time of each interface by centrally managing the interfaces which have sent the HTTP requests in the global variable, immediately send the overtime reminding to the client when the interface request is overtime, and timely remind the client that the current service is abnormal, thereby avoiding the inconvenience caused by the system being blocked and the use of the user due to the long-time interface request abnormity.
The above-described embodiments are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment.
Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments may be implemented by software plus a general hardware platform, and may also be implemented by hardware. With this in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer electronic device (which may be a personal computer, a server, or a network electronic device, etc.) to execute the methods of the various embodiments or some parts of the embodiments.
Conditional language such as "can," "might," or "may" is generally intended to convey that a particular embodiment can include (yet other embodiments do not include) particular features, elements, and/or operations, among others, unless specifically stated otherwise or otherwise understood within the context as used. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without student input or prompting, whether such features, elements, and/or operations are included or are to be performed in any particular embodiment.
What has been described herein in the specification and drawings includes examples of methods, systems, and storage media capable of providing an interface request timeout reminder. It will, of course, not be possible to describe every conceivable combination of components and/or methodologies for purposes of describing the various features of the disclosure, but it can be appreciated that many further combinations and permutations of the disclosed features are possible. It is therefore evident that various modifications can be made to the disclosure without departing from the scope or spirit thereof. In addition, or in the alternative, other embodiments of the disclosure may be apparent from consideration of the specification and drawings and from practice of the disclosure as presented herein. It is intended that the examples set forth in this specification and the drawings be considered in all respects as illustrative and not restrictive. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims (10)
1. An interface request timeout reminding method is characterized by comprising the following steps:
predefining a global variable for storing the request identifier;
when an HTTP request sent by an interface is detected, a request identifier of the current interface is constructed according to a preset structure and is inserted into the global variable;
starting a timer, performing polling traversal on all request identifications in the current global variable, judging whether the accumulated insertion time of each request identification is greater than the preset time, if so, deleting the request identification and sending an overtime prompt of a corresponding interface to the client.
2. The method according to claim 1, wherein each time an HTTP request is detected to be sent by an interface, after a request identifier of a current interface is constructed according to a preset structure and inserted into the global variable, the method further comprises:
and judging whether each interface receives a request result returned by the background server, and if so, deleting the request identifier corresponding to the interface which has received the request result in the global variable.
3. The interface request timeout reminding method according to claim 1, wherein each time it is detected that the interface sends an HTTP request, the method constructs a request identifier of a current interface according to a preset structure and inserts the request identifier into the global variable, and includes:
continuously detecting whether each interface sends an HTTP request, if so, acquiring the name of the interface which currently sends the HTTP request and a current timestamp;
and constructing a request identifier of the current interface according to the interface name, the current timestamp and the accumulated insertion time, and inserting the request identifier into the global variable, wherein the initial value of the accumulated insertion time is 0.
4. The interface request timeout reminding method according to claim 1, wherein the starting a timer and performing polling traversal on all request identifiers in a current global variable, determining whether an accumulated insertion time of each request identifier is greater than a preset time, and if so, deleting the request identifier and sending a timeout reminder of a corresponding interface to a client, includes:
starting a timer and performing polling traversal on all request identifiers in the current global variable;
and judging whether the accumulated insertion time of each request identifier is greater than the preset time during each polling pass, if so, deleting the request identifier and sending an overtime prompt of the corresponding interface to the client.
5. The interface request timeout reminding method according to claim 4, wherein the starting a timer and performing a polling traversal on all request identifiers in a current global variable includes:
starting a timer to perform polling traversal on all request identifications in the current global variable according to preset interval time;
and updating the accumulated insertion time of each request identifier to T +1 after traversing once, wherein T is the current accumulated insertion time of each request identifier.
6. The interface request timeout reminding method according to claim 4, wherein the polling duration of each time judges whether the accumulated insertion time of each request identifier is greater than a preset time, and if so, the request identifier is deleted and the timeout reminder of the corresponding interface is sent to the client, including:
acquiring the current accumulated insertion time of each request identifier during each polling;
and judging whether the current accumulated insertion time of each request identifier is greater than the preset time, if so, deleting the corresponding request identifier and sending an overtime prompt of the interface corresponding to the request identifier to the client.
7. The interface request timeout alerting method of claim 5, wherein the preset interval time is 1 second.
8. An interface request timeout alerting system, said system comprising at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the interface request timeout alerting method of any one of claims 1-7.
9. A non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the interface request timeout alerting method of any one of claims 1-7.
10. A computer program product, characterized in that the computer program product comprises a computer program stored on a non-volatile computer-readable storage medium, the computer program comprising program instructions which, when executed by a processor, cause the processor to carry out the interface request timeout alerting method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011150176.7A CN112433872A (en) | 2020-10-23 | 2020-10-23 | Interface request timeout reminding method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011150176.7A CN112433872A (en) | 2020-10-23 | 2020-10-23 | Interface request timeout reminding method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112433872A true CN112433872A (en) | 2021-03-02 |
Family
ID=74696005
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011150176.7A Pending CN112433872A (en) | 2020-10-23 | 2020-10-23 | Interface request timeout reminding method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112433872A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115277847A (en) * | 2022-07-27 | 2022-11-01 | 阿里巴巴（中国）有限公司 | Service processing method, device, equipment, platform, medium and program product |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030200329A1 (en) * | 2002-04-23 | 2003-10-23 | Delaney William P. | Polling-based mechanism for improved RPC timeout handling |
| CN101800663A (en) * | 2010-02-09 | 2010-08-11 | 中国电信股份有限公司 | Interface buffering method and system |
| CN102143226A (en) * | 2011-02-12 | 2011-08-03 | 华为技术有限公司 | Time-out control method, time-out control device and time-out control system |
| US20120110109A1 (en) * | 2010-11-01 | 2012-05-03 | Michael Luna | Caching adapted for mobile application behavior and network conditions |
| CN106712979A (en) * | 2015-07-16 | 2017-05-24 | 中兴通讯股份有限公司 | Network element monitoring method and device |
| CN109451020A (en) * | 2018-11-06 | 2019-03-08 | 深圳前海微众银行股份有限公司 | Overtime management method, equipment and computer readable storage medium |
| CN110149356A (en) * | 2019-02-28 | 2019-08-20 | 深圳点猫科技有限公司 | Method and device is uniformly processed in a kind of network request abnormality |
| CN110493291A (en) * | 2018-05-14 | 2019-11-22 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus handling HTTP request |
| CN111309548A (en) * | 2020-02-03 | 2020-06-19 | 中国银联股份有限公司 | Timeout monitoring method and device and computer readable storage medium |
-
2020
- 2020-10-23 CN CN202011150176.7A patent/CN112433872A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030200329A1 (en) * | 2002-04-23 | 2003-10-23 | Delaney William P. | Polling-based mechanism for improved RPC timeout handling |
| CN101800663A (en) * | 2010-02-09 | 2010-08-11 | 中国电信股份有限公司 | Interface buffering method and system |
| US20120110109A1 (en) * | 2010-11-01 | 2012-05-03 | Michael Luna | Caching adapted for mobile application behavior and network conditions |
| CN102143226A (en) * | 2011-02-12 | 2011-08-03 | 华为技术有限公司 | Time-out control method, time-out control device and time-out control system |
| CN106712979A (en) * | 2015-07-16 | 2017-05-24 | 中兴通讯股份有限公司 | Network element monitoring method and device |
| CN110493291A (en) * | 2018-05-14 | 2019-11-22 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus handling HTTP request |
| CN109451020A (en) * | 2018-11-06 | 2019-03-08 | 深圳前海微众银行股份有限公司 | Overtime management method, equipment and computer readable storage medium |
| CN110149356A (en) * | 2019-02-28 | 2019-08-20 | 深圳点猫科技有限公司 | Method and device is uniformly processed in a kind of network request abnormality |
| CN111309548A (en) * | 2020-02-03 | 2020-06-19 | 中国银联股份有限公司 | Timeout monitoring method and device and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115277847A (en) * | 2022-07-27 | 2022-11-01 | 阿里巴巴（中国）有限公司 | Service processing method, device, equipment, platform, medium and program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109766262B (en) | Interface data processing method, automatic testing method, device, equipment and medium | |
| WO2019179027A1 (en) | Electronic device, firewall provisioning verification method, system and storage medium | |
| US10218717B1 (en) | System and method for detecting a malicious activity in a computing environment | |
| CN110765001B (en) | Modularized automatic test method and device for application system | |
| CN111106976B (en) | Detection method and device for CDN network, electronic equipment and readable storage medium | |
| WO2019242455A1 (en) | Method and apparatus for user request forwarding, reverse proxy and computer readable storage medium | |
| CN110781070A (en) | Big data test verification method and device, computer equipment and storage medium | |
| CN111522711A (en) | Data monitoring processing system, method, execution end, monitoring end and electronic equipment | |
| CN108733545B (en) | Pressure testing method and device | |
| CN112416794A (en) | Method, device and equipment for processing code coverage rate and storage medium | |
| WO2020233065A1 (en) | Network environment testing method and apparatus, and terminal device | |
| CN112433872A (en) | Interface request timeout reminding method, system and storage medium | |
| CN111538602A (en) | Message forwarding method and device for message queue | |
| WO2020233064A1 (en) | Function test-based factor influence degree determination method and apparatus, and terminal device | |
| CN109246234B (en) | Image file downloading method and device, electronic equipment and storage medium | |
| CN108171862B (en) | Number sending method and number sender | |
| CN111984520A (en) | Buried point testing method, computer device and computer-readable storage medium | |
| CN109815083B (en) | Application crash monitoring method and device, electronic equipment and medium | |
| CN111078418B (en) | Operation synchronization method, device, electronic equipment and computer readable storage medium | |
| CN112653736A (en) | Parallel source returning method and device and electronic equipment | |
| US9880813B2 (en) | RTE code generating method and apparatus performing the same | |
| CN110417597B (en) | Method and device for monitoring certificate, electronic equipment and readable storage medium | |
| CN113268183B (en) | List page countdown display method and device | |
| EP3866031A1 (en) | Webpage loading method, intermediate server, and webpage loading system | |
| US11729246B2 (en) | Apparatus and method for determining types of uniform resource locator |
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 |