CN112839100B - Method, equipment and storage medium for suspending http requests in batches - Google Patents
Method, equipment and storage medium for suspending http requests in batches Download PDFInfo
- Publication number
- CN112839100B CN112839100B CN202110131207.2A CN202110131207A CN112839100B CN 112839100 B CN112839100 B CN 112839100B CN 202110131207 A CN202110131207 A CN 202110131207A CN 112839100 B CN112839100 B CN 112839100B
- Authority
- CN
- China
- Prior art keywords
- request
- requests
- suspension
- monitored
- callback function
- 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
- 238000000034 method Methods 0.000 title claims abstract description 44
- 230000006870 function Effects 0.000 claims abstract description 57
- 239000000725 suspension Substances 0.000 claims abstract description 50
- 230000001960 triggered effect Effects 0.000 claims abstract description 18
- 238000012544 monitoring process Methods 0.000 claims abstract description 16
- 230000005540 biological transmission Effects 0.000 claims abstract description 10
- 238000004590 computer program Methods 0.000 claims description 3
- 230000009191 jumping Effects 0.000 claims description 3
- 230000003993 interaction Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- QLKDMIUEWFNEPV-UHFFFAOYSA-N 4,5,6,7-Tetrachloro-2-trifluoromethylbenzimidazole Chemical compound ClC1=C(Cl)C(Cl)=C2NC(C(F)(F)F)=NC2=C1Cl QLKDMIUEWFNEPV-UHFFFAOYSA-N 0.000 description 1
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000002474 experimental method Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
Images
Classifications
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- 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/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a method, equipment and storage medium for suspending http requests in batches, wherein the method comprises the following steps: monitoring project requests, and setting callback functions before request transmission and callback functions after request completion; judging whether the monitored request meets the registration condition, if yes, registering all the requests meeting the registration condition into the object before the request is sent based on a callback function before the request is sent, otherwise, returning to continue to monitor the project request; based on the request completion callback function, deleting the corresponding completed request information in the object after the request is completed; when a batch suspension request scene is triggered, suspension operations are sequentially performed on the remaining requests in the current object. Compared with the prior art, the method and the device can realize the purpose of batch suspension of the requests in large-scale projects, and can lighten the pressure of the server, shorten the waiting time of the requests and improve the user experience.
Description
Technical Field
The invention relates to the technical field of internet data interaction processing, in particular to a method, equipment and storage medium for suspending http requests in batches.
Background
As the website interaction function becomes more complex, the data interaction between the website and the server becomes frequent, when the user performs the interaction, it is assumed that the user wants to give up the interaction and perform other operations due to the slow response speed of the interface, or when the user enters a page due to misoperation, the page initiates a plurality of requests, and at this time, the user switches to other pages, and the requests are still continued, so that on one hand, the interaction requests which are useless for the current operation of the user increase the pressure of the server, and on the other hand, if the requests fail, the errors are directly thrown to the current interface of the user, and the user experience is poor. Thus, when faced with the above-described situation, how to effectively suspend these requests to improve user experience and website performance has become the focus of current research.
The existing jQuery provides a single ajax request suspension method, namely an abart method, wherein the abart method cannot directly suspend requests in batches, and in the existing project, suspension requests need to use the abart method for the requests in each controller respectively and execute suspension operation on the unfinished requests when appropriate. If a request is intercepted at the outer layer and an abort is attempted, only a single request can be aborted, for example: if three requests are sent simultaneously by a page, when a callback function of which the request is completed is received, it cannot be judged which request is completed, and no matter how many times of the function is called, the last sent and unfinished request can be stopped.
Therefore, when the above method is adopted, if a plurality of requests need to be suspended at the same time, the above method cannot meet the requirement, and for large-scale projects, the above method cannot provide a suspending request function well, and how to realize batch suspending requests in large-scale projects is a problem to be solved currently.
Disclosure of Invention
The present invention is directed to a method, apparatus and storage medium for batch suspension of http requests, so as to overcome the above-mentioned drawbacks of the prior art, and perform batch suspension operation on all outstanding requests when a scenario requiring batch suspension of the requests is triggered.
The aim of the invention can be achieved by the following technical scheme: a method for suspending http requests in batches, comprising the steps of:
s1, monitoring project requests, and setting callback functions before request transmission and callback functions after request completion;
s2, judging whether the monitored request meets the registration condition, if so, executing a step S3, otherwise, returning to the step S1;
s3, based on a callback function before request transmission, registering all requests meeting registration conditions in the object before request transmission;
s4, completing a callback function based on the request, and deleting the corresponding completed request information in the object after the request is completed;
s5, when a batch suspension request scene is triggered, sequentially performing suspension operation on the rest requests in the current object.
Further, in the step S1, the monitoring of the project request is specifically to set an ajax request monitoring function in the project entry file to monitor the project request initiated by the user.
Further, the specific process of step S2 is as follows: judging whether the monitored request occurs in the page jumping process, if so, returning to the step S1, otherwise, executing the step S3.
Further, the specific process of registering the request to the object in step S3 is as follows:
s31, creating an empty object;
s32, if the popup creation event is monitored, recording the ID of the popup into the object, and then executing step S33;
if the popup creation event is not monitored, directly executing step S33;
and S33, triggering a callback function before the request is sent, registering a request to be sent in the callback function before the request is sent, taking a URL (Uniform Resource Locator ) of the request as a key, and taking an XMLHttpRequest object as a value corresponding to the key.
Further, the step S4 specifically includes the following steps:
s41, triggering a callback function after the request is completed, and transmitting back the URL of the request by the callback function after the request is completed;
s42, deleting the corresponding request in the object according to the returned URL information.
Further, in the step S5, the batch suspension request scenario includes successful page jump and popup window closing.
Further, in the step S5, if the triggered batch suspension request scenario is that the page jump is successful, the step S5 specifically includes the following steps:
s51, changing the page jump state mark from true to false, namely, successful page jump;
s52, after the page jump success event is monitored, all requests in the current object are sequentially subjected to suspension operation.
Further, in the step S5, if the triggered batch suspension request scenario is that the popup window is closed, the specific process in the step S5 is as follows: after the popup window closing event is monitored, all requests in the object recorded with the popup window ID are sequentially subjected to suspension operation.
The device for suspending http requests in batches comprises a processor, wherein the processor is in communication connection with a memory, the memory stores a computer readable program, and the processor realizes the method for suspending http requests in batches when executing the computer readable program.
A computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the batch suspension http request method described above.
Compared with the prior art, the method monitors and records all requests in the project entry file and registers the requests in the object; the callback function is completed through expanding the request, specific information of the completed request can be obtained after the request is completed, and the completed request is deleted from the object based on the information; when a scene requiring batch suspension requests is triggered, all outstanding requests in the object can be suspended at one time, so that the purpose of batch suspension requests is realized, and the development workload is greatly reduced. The method of the invention is used for suspending the interfaces in batches in a proper scene, thereby reducing the pressure of the server to a certain extent, shortening the waiting time of the request and improving the user experience.
Drawings
FIG. 1 is a schematic flow chart of the method of the present invention;
FIG. 2 is a schematic diagram of a batch suspension flow in an embodiment;
FIG. 3 is a schematic diagram of a batch suspension request flow during page skip in an embodiment;
FIG. 4 is a flow chart of a batch suspension request when closing a pop-up window according to an embodiment.
Detailed Description
The invention will now be described in detail with reference to the drawings and specific examples.
Examples
As shown in fig. 1, a method for suspending http requests in batches includes the following steps:
s1, monitoring a project request, and setting a callback function before request transmission and a callback function after request completion, wherein the project request monitoring is specifically to set an ajax request monitoring function in a project entry file so as to monitor the project request initiated by a user;
s2, judging whether the monitored request meets the registration condition, if yes, executing a step S3, otherwise returning to the step S1, and if the monitored request occurs in the page jumping process, not meeting the registration condition;
s3, based on a callback function before request transmission, all requests meeting registration conditions are registered in the object before the request transmission, and the specific process of registering the requests is as follows:
s31, creating an empty object;
s32, if the popup creation event is monitored, recording the ID of the popup into the object, and then executing step S33;
if the popup creation event is not monitored, directly executing step S33;
s33, triggering a callback function before the request is sent, registering a request to be sent in the callback function before the request is sent, taking the URL of the request as a key and taking an XMLHttpRequest object as a value corresponding to the key;
s4, based on the request completion callback function, deleting the corresponding completed request information in the object after the request is completed, specifically triggering the callback function after the request is completed, and transmitting back the URL of the request by the request completion callback function; then deleting the corresponding request in the object according to the returned URL information;
s5, when a batch suspension request scene is triggered (the batch suspension request scene comprises successful page jump and popup window closing), sequentially performing suspension operation on the rest requests in the current object:
if the triggered batch suspension request scene is that the page jump is successful, changing the page jump state mark from true to false, namely that the page jump is successful; after monitoring a page skip success event, sequentially carrying out suspension operation on all requests in the current object;
if the triggered batch suspension request scene is a popup window closing, after a popup window closing event is monitored, suspension operation is sequentially carried out on all requests in the object recorded with the popup window ID.
Based on the technical scheme provided by the invention, the embodiment obtains the completed request information by expanding the complex callback function in the ajaxSetup of the jQuery, thereby obtaining the set of the incomplete requests, and then carrying out batch suspension operation on the incomplete requests when triggering the scene requiring batch suspension of the requests. The method specifically includes monitoring requests of items in an item entry file, recording all requested information into an Obj object, obtaining completed request information by expanding parameters of a complex function, deleting the completed request information from the Obj according to the information, and recording all the completed requests in the Obj in a state of incomplete requests. When a scene requiring batch suspension requests is triggered, suspension operations are sequentially carried out on all requests recorded in Obj, and the function of batch suspension requests can be realized.
The specific process is shown in fig. 2:
1. and setting an ajax request monitoring function in the project entry file, and setting callback functions before request sending and after request completion.
2. In the callback function before the request is sent, registering the request to be sent, recording the request into an Obj object, using url of the request as a key, and using an XMLHttpRequest object as a value corresponding to the key.
3. Modifying source codes corresponding to ajexsetup in jQuery and triggering complex callback functions, and returning url of the request. And after the request is completed, triggering a corresponding callback function, taking url information of the completed request, and deleting the corresponding request information in Obj based on the url information.
4. When the batch suspension requests are needed, suspension operation is sequentially carried out on the requests recorded in the Obj object.
In this embodiment, after a batch request is made for a user entering the interface a, the user leaves the interface a to enter the interface B, and triggers a scenario called by the interface B, experiments are performed on a Chrome with version 76, and when the technical scheme of the present invention is used and the technical scheme of the present invention is not used in the scenario, response time called by the interface B is recorded, so that data as shown in table 1 are obtained:
TABLE 1
According to the data analysis, when the batch request number is 200, 1000 and 2000, the response speed of the interface can be respectively improved by 7 times, 27.4 times and 53.5 times by using the technical scheme of the invention.
Noun interpretation: stabed refers to the waiting time from when the browser gets an instruction to issue the request to when the request can be issued; waiting (TTFB) refers to the time it takes to receive the first byte of a response after a request is issued (Time To Fist Byte).
In this embodiment, batch suspension requests are made based on jQuery, and items use the angularJs framework. Before implementation, a project built based on angularJs needs to be prepared, and a jQuery library is introduced into the project. The popup in the following embodiments uses an ngDialog implementation.
For batch suspension requests for different scenarios, specific examples are as follows:
1. batch suspension requests are required at page jumps, as shown in FIG. 3:
1. all requests of the project are monitored in the project entry file, and callback functions before the request is sent and when the request is completed are set.
2. And registering the to-be-transmitted request in a callback event before the request is transmitted, and registering the to-be-transmitted request in an object for recording request information.
2.1 creating an empty Object for recording the information of the request to be sent.
2.2 in the callback function before the request is sent, the request is registered in the Object, url of the request is used as a key, and the XMLHttpRequest Object is a value corresponding to the key.
3. In the callback function after the request is finished, the completed request is logged off.
3.1 modifying source codes of triggering complex callback functions in the ajexsetup function in the jQuery, and returning url of the request.
And 3.2, deleting the corresponding request data in the Object according to the returned url when the complex callback function of the monitoring request in the entry file is triggered.
4. Before the page jumps, an angular $ stateChangeStart event is triggered, and after the event is monitored, the state of the page is marked with an identifier iststatechange. If the sending request is monitored in the page skip process, the sending request is not registered in the Object.
5. After the page is successfully jumped, an annular $stateChangeSuccess event is triggered, and after the event is monitored, a suspension method is sequentially called for record requests in objects, so that a batch suspension function of incomplete requests is realized.
2. When the current page closes the popup window, a request sent in the batch suspension popup window is performed, as shown in fig. 4:
1. all requests of the project are monitored in the project entry file, and callback functions before the request is sent and when the request is completed are set.
2. After monitoring for a create pop event, the request sent in the pop is recorded.
2.1 creating an empty Object for recording the information of the request to be sent.
2.2 after hearing a popup window open event, an Object id Object is generated for recording the request in this popup window, where id is the id of the popup window.
2.3 when the callback function before the request is sent is triggered, the request is registered in the Object [ id ] Object, url of the request is used as a key, and the XMLHttpRequest Object is used as a value corresponding to the key.
3. In the callback function after the request is finished, the completed request is logged off.
3.1 modifying source codes corresponding to ajexsetup in jQuery and triggering complex callback functions, and returning url of the request.
3.2 when the complete callback function of the monitoring request in the entry file is triggered, according to url information of the returned request, judging that if the request is recorded in the Object [ id ], deleting the information of the completed request from the Object.
4. When the window closing event is monitored, an abort method is sequentially called for the requests recorded in the outstanding requests, namely the objects, sent in the window, so that the batch abort request function during window closing is realized.
The embodiment also discloses equipment for suspending http requests in batches, which comprises a processor, wherein the processor is in communication connection with a memory, the memory stores a computer readable program, and the batch suspending http request method is realized when the processor executes the computer readable program.
The embodiment also discloses a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the batch suspension http request method described above.
In summary, the technical scheme provided by the invention can monitor and suspend http requests in batches in the regular JS framework, so that development workload is greatly reduced, and user experience is improved.
Claims (6)
1. A method for suspending http requests in batches, comprising the steps of:
s1, monitoring project requests, and setting callback functions before request transmission and callback functions after request completion;
s2, judging whether the monitored request meets the registration condition, if so, executing a step S3, otherwise, returning to the step S1;
s3, based on a callback function before request transmission, registering all requests meeting registration conditions in the object before request transmission;
s4, completing a callback function based on the request, and deleting the corresponding completed request information in the object after the request is completed;
s5, when a batch suspension request scene is triggered, sequentially performing suspension operation on the rest requests in the current object;
the step S1 of monitoring the project request is to set an ajax request monitoring function in a project entry file to monitor the project request initiated by a user;
the specific process of the step S2 is as follows: judging whether the monitored request occurs in the page jumping process, if so, returning to the step S1, otherwise, executing the step S3;
the specific process of registering the request to the object in the step S3 is as follows:
s31, creating an empty object;
s32, if the popup creation event is monitored, recording the ID of the popup into the object, and then executing step S33;
if the popup creation event is not monitored, directly executing step S33;
s33, triggering a callback function before the request is sent, registering a request to be sent in the callback function before the request is sent, taking the URL of the request as a key and taking an XMLHttpRequest object as a value corresponding to the key;
the step S4 specifically includes the following steps:
s41, triggering a callback function after the request is completed, and transmitting back the URL of the request by the callback function after the request is completed;
s42, deleting the corresponding request in the object according to the returned URL information.
2. A method according to claim 1, wherein the batch suspension request scenario in step S5 includes page jump success and popup closing.
3. The method of claim 2, wherein in step S5, if the triggered batch suspension request scenario is that the page jump is successful, step S5 specifically includes the following steps:
s51, changing the page jump state mark from true to false, namely, successful page jump;
s52, after the page jump success event is monitored, all requests in the current object are sequentially subjected to suspension operation.
4. The method of claim 2, wherein in step S5, if the triggered batch suspension request scenario is a popup window closing, the specific process of step S5 is as follows: after the popup window closing event is monitored, all requests in the object recorded with the popup window ID are sequentially subjected to suspension operation.
5. An apparatus for suspending http requests in bulk, comprising a processor communicatively coupled to a memory, the memory storing a computer readable program, the processor executing the computer readable program to implement a method for suspending http requests in bulk as claimed in any one of claims 1-4.
6. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, implements the steps of a method of suspending http requests in batches according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110131207.2A CN112839100B (en) | 2021-01-30 | 2021-01-30 | Method, equipment and storage medium for suspending http requests in batches |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110131207.2A CN112839100B (en) | 2021-01-30 | 2021-01-30 | Method, equipment and storage medium for suspending http requests in batches |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112839100A CN112839100A (en) | 2021-05-25 |
| CN112839100B true CN112839100B (en) | 2023-04-25 |
Family
ID=75932519
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110131207.2A Active CN112839100B (en) | 2021-01-30 | 2021-01-30 | Method, equipment and storage medium for suspending http requests in batches |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112839100B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106452977A (en) * | 2016-11-24 | 2017-02-22 | 武汉斗鱼网络科技有限公司 | Dynamic adaptive heartbeat sending method and system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2494027B (en) * | 2011-08-25 | 2014-05-21 | Ibm | A computer-implemented method enabling a web application to call at least one native function of a mobile device |
| US10536560B2 (en) * | 2013-09-13 | 2020-01-14 | John Wason | System and method for implementing augmented object members for remote procedure call |
| US20160291940A1 (en) * | 2014-07-07 | 2016-10-06 | Symphony Teleca Corporation | Remote Embedded Device Update Platform Apparatuses, Methods and Systems |
| CN106095886B (en) * | 2016-06-03 | 2020-10-09 | 腾讯科技（深圳）有限公司 | Data processing method and device |
| CN106789307B (en) * | 2016-12-30 | 2019-12-03 | 腾讯科技（深圳）有限公司 | Configuration data processing method, apparatus and system |
| CN108200122A (en) * | 2017-12-08 | 2018-06-22 | 北京奇虎科技有限公司 | A kind of HTTP data processing methods and device |
| CN108696568B (en) * | 2018-02-23 | 2021-07-06 | 福建天泉教育科技有限公司 | Request batch processing method and terminal |
-
2021
- 2021-01-30 CN CN202110131207.2A patent/CN112839100B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106452977A (en) * | 2016-11-24 | 2017-02-22 | 武汉斗鱼网络科技有限公司 | Dynamic adaptive heartbeat sending method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112839100A (en) | 2021-05-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9003423B1 (en) | Dynamic browser compatibility checker | |
| US9483307B2 (en) | Asynchronous, interactive task workflows | |
| US8756614B2 (en) | Central registry for binding features using dynamic pointers | |
| JP6742650B2 (en) | Application calling method and device using mobile browser | |
| US8756593B2 (en) | Map generator for representing interrelationships between app features forged by dynamic pointers | |
| US8589876B1 (en) | Detection of central-registry events influencing dynamic pointers and app feature dependencies | |
| WO2017196635A1 (en) | Page component dynamic layout | |
| CN106133698A (en) | Framework for user model collapse report | |
| US20150089415A1 (en) | Method of processing big data, apparatus performing the same and storage media storing the same | |
| CN113760763A (en) | Software testing method, device, server and system | |
| CN112988185A (en) | Cloud application updating method, device and system, electronic equipment and storage medium | |
| CN111679976A (en) | Method and device for searching page object | |
| CN111294377B (en) | Dependency network request sending method, terminal device and storage medium | |
| EP3869330A1 (en) | Method and apparatus for lazy loading of js script | |
| CN112839100B (en) | Method, equipment and storage medium for suspending http requests in batches | |
| JP2016071398A (en) | Test execution device, test execution method, and computer program | |
| CN111026947A (en) | Crawler method and embedded crawler implementation method based on browser | |
| CN108062224B (en) | Data reading and writing method and device based on file handle and computing equipment | |
| US20140245159A1 (en) | Transport script generation based on a user interface script | |
| US10545729B2 (en) | Computer program interface | |
| CN113176952A (en) | Data processing method and device and readable storage medium | |
| JP7216767B2 (en) | Access method, communication system and program | |
| JP2016071397A (en) | Test execution device, test execution method, and computer program | |
| JP6353759B2 (en) | Test execution device, test execution method, and computer program | |
| CN114385054B (en) | Form filling method and device, electronic equipment and storage medium |
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 | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A method, device, and storage medium for batch terminating HTTP requests Effective date of registration: 20231115 Granted publication date: 20230425 Pledgee: Bank of Shanghai Limited by Share Ltd. Pudong branch Pledgor: SHANGHAI EISOO INFORMATION TECHNOLOGY Co.,Ltd. Registration number: Y2023310000743 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |