CN111294377B - Dependency network request sending method, terminal device and storage medium - Google Patents
Dependency network request sending method, terminal device and storage medium Download PDFInfo
- Publication number
- CN111294377B CN111294377B CN201811501788.9A CN201811501788A CN111294377B CN 111294377 B CN111294377 B CN 111294377B CN 201811501788 A CN201811501788 A CN 201811501788A CN 111294377 B CN111294377 B CN 111294377B
- Authority
- CN
- China
- Prior art keywords
- network request
- array
- request object
- callback
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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
- H04L67/62—Establishing a time schedule for servicing the requests
-
- 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
Abstract
The invention discloses a network request sending method, a terminal device and a storage medium of a dependency relationship, which are applicable to the field of application development. The method provided by the invention comprises the following steps: when a user initiates a network request, storing a network request object with a dependency relationship into a predefined array; defining a callback of the network request object, setting in the callback that when the current network request is successful, controlling the initiation of the next network request according to the return result of the current network request object; and acquiring a first network request object in the array to initiate a network request. The invention can simplify the logic relation between different network requests, reduce the code redundancy and facilitate the later maintenance.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method for sending a network request of a dependency relationship, a terminal device, and a storage medium.
Background
When a new page is opened to a web site, new page resources are often loaded, which are obtained by initiating a network request. In practice, the initiation of one network request often depends on the completion of another request, and because multiple network requests are simultaneously sent each time a resource request is initiated, there is a complex logical relationship between the network requests. For network requests with dependencies, the usual approach is to define various complex internal processing logic to manage the initiation of the network request, which not only creates a significant amount of code redundancy, but also is inconvenient to maintain.
Thus, there is a need for a method that can simplify handling network requests with dependencies.
Disclosure of Invention
In view of the above, the embodiments of the present invention provide a method, a terminal device, and a storage medium for sending a network request with a dependency relationship, which are used for solving the problem of code redundancy existing in the existing network request initiation method with a dependency relationship.
In a first aspect of the embodiment of the present invention, a method for sending a network request of a dependency relationship is provided, including:
when a user initiates a network request, storing a network request object with a dependency relationship into a predefined array;
defining a callback function of the network request object, setting in the callback function that when the current network request is successful, controlling the initiation of the next network request according to the return result of the current network request object;
and acquiring a first network request object in the array to initiate a network request.
In a second aspect of the embodiment of the present invention, there is provided a network request sending terminal apparatus of a dependency relationship, including:
the storage module is used for storing the network request object with the dependency relationship into a predefined array when a user initiates a network request;
the setting module is used for defining a callback function of the network request object, setting that when the current network request is successful in the callback function, and controlling the initiation of the next network request according to the return result of the current network request object;
and the initiating module is used for acquiring a first network request object in the array to initiate a network request.
In a third aspect of the embodiments of the present invention, there is provided a terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to the first aspect of the embodiments of the present invention when the computer program is executed.
In a fourth aspect of the embodiments of the present invention, there is provided a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method provided by the first aspect of the embodiments of the present invention.
In a fifth aspect of the embodiments of the present invention, there is provided a computer program product comprising a computer program which, when executed by one or more processors, implements the steps of the method provided by the first aspect of the embodiments of the present invention.
In the embodiment of the invention, the network requests with the dependency relationship are put into the same array, and each network request is set to have a more returned result, so that the initiation of the next request is controlled, and the associated initiation of the network requests is realized. The logic relationship initiated by different network requests can be simplified, the code redundancy is reduced, and the later maintenance is convenient.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of an embodiment of a method for sending a network request of a dependency relationship according to an embodiment of the present invention;
FIG. 2 is a flowchart of another embodiment of a method for sending a network request of a dependency relationship according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a terminal device for sending a network request of a dependency relationship according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a network request sending method, a terminal device and a storage medium of a dependency relationship, which are used for simplifying a network request initiating mode with the dependency relationship.
In order to make the objects, features and advantages of the present invention more comprehensible, the technical solutions in the embodiments of the present invention are described in detail below with reference to the accompanying drawings, and it is apparent that the embodiments described below are only some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Embodiment one:
referring to fig. 1, a flowchart of a network performance parameter acquisition method provided by an embodiment of the present invention includes the following steps:
s101, when a user initiates a network request, storing a network request object with a dependency relationship into a predefined array;
the network request is typically a data request sent by a client to a server through a network, and each data request is initiated by sending a corresponding network request object. In the embodiment of the invention, a network request class is defined, a network request object is generated by instantiating the class, and response data of a server side is transmitted back to a client side through the network request object. Preferably, the network request is a network request in an IOS.
The dependency relationship refers to that the initiation of one network request depends on the successful initiation and response of the other data, and when the network requests are initiated, the concurrent requests can be managed through multiple threads, and the requests with the dependency relationship can be initiated in sequence.
In each network request object, there is a callback of the server response result, and each time the network request object initiates a network request, the callback can transmit response information of the server side, preferably, in the embodiment of the invention, the callback is rewritten, and the rewritten callback can control the initiation of the associated network request in the array according to the server return information.
Optionally, defining a network request class, and defining a sending method in the network request class, when a user initiates a network request, instantiating the network request class to generate a network request object. Specifically, a network request class is defined, after a user initiated request is monitored, the network request class is instantiated, request parameters are transmitted through the generated network request object, and response data of a server are returned.
Optionally, creating a classification of the data, and after each network request object is set in the classification to initiate a network request, returning a request result to a network request initiating place; and (3) rewriting the system callback method, wherein in the rewritten system callback method, a method for controlling the next network request object to initiate calling is defined according to a request result returned by each network request object. After the array is defined and classified, the array elements and the network request objects can realize the blocking of request synchronization by a classification definition method, and a dependency network request initiating method is created, and the method can call back the network request result.
S102, defining a callback function of the network request object, and setting a callback function to control the initiation of a next network request according to a return result of the current network request object when the current network request is successful;
the callback is a callback function, and is used for one party to call under specific conditions through a function called by a function pointer, and in the callback, the initiation of a network request is set.
When generating network request objects, a callback type is extended for each network request object for controlling the initiation of network requests. Preferably, the callback method after the network request is rewritten is set, the network request is finished, the original callback method is executed, a request response result is returned, the next network request is controlled to be initiated through the rewritten callback, and the delay time of the initiation is set.
Optionally, according to the network request result sent by the current network request object callback, controlling a delay time length initiated by a next network request in the array, wherein the network request result contains delay time; and terminating the initiation of the next network request when the delay time is less than zero. The response result of the server side generally comprises request result data, such as request errors, response data, request delay and the like, and the time length of delay initiation of the next request is controlled or the sending of the next request is directly stopped according to the returned result. The delay time is preset time, the initiation of terminating the network request can be represented by a value smaller than zero, and the delay time length of the network request can be represented by a value larger than or equal to zero.
S103, acquiring a first network request object in the array to initiate a network request.
And taking out the first network request object in the array, and calling a sending method of the object to initiate a network request.
Optionally, before initiating the network request, further includes: and traversing all elements in the array, judging whether all elements are of the network request object type, and initiating a network request when all elements are of the network request object type.
And in the array, acquiring a first network request object according to an array subscript, calling a sending method thereof to initiate a network request, and selecting to initiate the next request or resend the current request or stop sending according to a server-side response result.
According to the step, the callback method is expanded in each network object, and the initiation of the next request is controlled according to the returned result of the current object, so that the initiation of the network request with the dependency relationship can be simplified.
Embodiment two:
taking program code as an example on the basis of fig. 1, a specific implementation process of processing a network request is described in detail in connection with fig. 2, as follows:
after a user initiates a network request, the client sends request data to the server through the request object, and the server returns response data to the client.
S201, network request objectification encapsulation
When a user initiates a network request, the network request needs to be subjected to objectification encapsulation through a predefined class, and a network request object is generated. Generally, a network request object will initiate a request to a server carrying various request parameters.
Illustratively, a network request class is first created, named 'DYRequest', in which a request method, a request path url, a request parameter params, and callback completions and send methods send are defined. In the system callback, callback completions calling the DYRequest return the response result to the originating request.
The customized network request class can carry various customized parameters in the network request process, so that the control of each network request object is facilitated.
S202, expanding a system array and creating a classification;
the classification can expand the system array attribute, and in the implementation of the invention, the generated network request object can be put into the defined array, and the invocation of each network request object can be conveniently carried out through the classification of the array, so as to control the initiation of the network request.
In the predefined array, the attribute is extended for each network request object, and the service scheduling logic for implementing the network request, for example, creates a class for the system type array NSArray, and defines a callback block type 'RequestSyncBlock' in the class, where the incoming parameters of the callback function include: network request object, error of system error type NSerror, server response and latency of system time type.
Further, a method 'sendsynccomposition (RequestSyncBlock) composition' is created that relies on sending network requests, by which the current request result is returned through the composition each time the network request is successful in the array.
Setting each network request object to return a network request result in the classification of the array, and facilitating control of all the network request objects in the array according to the returned result.
S203, expanding a callback type of the network request object;
and initiating a network request through each network request object, and after the server responds successfully, returning a request result through a callback function of the system. And expanding the callback type of the network request object, namely expanding and defining a control method called by the next network request on the basis of system callback.
Illustratively, in the system request class, a callback block type is defined as the 'RequestSectionBlock' of which parameters include: network request object, request error and server response. An attribute setcomponent of the 'requestsetblock' type is defined for the network request class 'DYRequest'.
Further, the network request type attribute 'completion' method is rewritten, when 'completion' is called, a call callback function 'section completion' is set and called, and a request per se, a request error and a server response are transmitted. An int type attribute index is defined for the network request class 'DYRequest'. An attribute nextRequest of the 'DYRequest' type is defined for the network request class.
After defining a class 'NSArray+Request' of the system array in S202, setting each network Request object to initiate a network Request and returning a Request result to a network Request initiating place after the callback of the block type is defined by the class; and (3) rewriting a system callback method, and newly adding and calling a 'section completion' callback, wherein the callback defines a request result returned according to each network request object, and controls calling logic initiated by the next network request object.
Wherein index is used to mark the location of the network request object in the array, and next request represents the next network request object. The overwrite callback function section facilitates controlling the initiation of the next network request according to the response result.
Specifically, when the network request object for realizing the dependency relationship is sent, the initiation of the next network request is controlled by the method defined in the array classification.
Exemplary, a 'sendSyncCompletion' method is implemented: first, all elements in the NSArray are traversed, and the network request object type is judged. When the callback is called, the current network request is indicated to be completed, a completion Block in 'sendSyncComposition' is called, the call is referred to as a request (current request itself) returned by a callback function 'section', an error (error of the current request), a response (server response) is taken to a return value and recorded as a delay (request delay time), whether a next request 'of the current request' exists or not is judged, and if the next request 'exists, the waiting time for a send method for calling the next request' to initiate a request is set according to the delay time. If delay is less than 0, nothing is processed.
And secondly, extracting the subscript of the network request with the response in the array, and extracting the next network request object of the array. The send method is then invoked and the request is initiated by the first network request object.
After the network request object is created, an array is created according to the generated network request object and an extended callback method is called. When one network request is completed, a result is obtained, and the control of the delayed initiation or stop of the next network request is returned to the initiation according to the result. The process loops until all requests are completed.
Embodiment III:
the above mainly describes a network request method, and a terminal apparatus of a network request will be described in detail below.
Fig. 3 is a schematic structural diagram of a terminal device for sending a network request of a dependency relationship, including:
the storage module 310: the network request object with the dependency relationship is stored in a predefined array when a user initiates a network request;
the network request is typically a data request sent by a client to a server through a network, and each data request is initiated by sending a corresponding network request object. In the embodiment of the invention, a network request class is defined, a network request object is generated by instantiating the class, and response data of a server side is transmitted back to a client side through the network request object. Preferably, the network request is a network request in an IOS. The dependency relationship refers to that the initiation of one network request depends on the successful initiation and response of the other data, and when the network requests are initiated, the concurrent requests can be managed through multiple threads, and the requests with the dependency relationship can be initiated in sequence.
Optionally, defining a network request class, and defining a sending method in the network request class, when a user initiates a network request, instantiating the network request class to generate a network request object. Each network request of the user can generate a request task in a corresponding object, and once the request initiating method is called, a response result can be transmitted to an initiating request place after the server side responds to the user request.
Optionally, creating a classification of the data, and after each network request object is set in the classification to initiate a network request, returning a request result to a network request initiating place; and (3) rewriting the system callback method, wherein in the rewritten system callback method, a method for controlling the next network request object to initiate the call is defined according to the request result returned by each network request object.
The setting module 320: and a callback function used for defining the network request object, wherein when the current network request is successful, the callback function is used for controlling the initiation of the next network request according to the return value of the current network request object.
The callback is a callback function, and is used for one party to call under specific conditions through a function called by a function pointer, and in the callback, the initiation of a network request is set. When generating network request objects, a callback type is extended for each network request object for controlling the initiation of network requests. Preferably, the callback method after the network request is rewritten is used for setting the network request completion to carry out callback through the original callback method, returning a request response result and controlling the initiation of the next network request through the rewritten callback.
Optionally, the controlling the initiation of the next network request according to the return value of the current network request object further includes:
according to the network request result transmitted by the callback of the current network request object, controlling the delay time length initiated by the next network request in the array, wherein the network request result comprises delay time; and terminating the initiation of the next network request when the delay time is less than zero. The response result of the server side generally comprises request result data, such as request errors, response data, request delay and the like, and the time length of delay initiation of the next request is controlled or the sending of the next request is directly stopped according to the returned result.
The initiation module 330: the method comprises the steps of acquiring a first network request object in the array to initiate a network request.
And calling a sending method of the first network request object in the array to initiate a network request.
Optionally, the initiating module 330 includes:
traversing unit: and traversing all elements in the array, judging whether the elements are network request object types, and initiating a network request when all the elements are network request object types. Before the network request is initiated, ensuring whether all network requests are of the network request object type or not through the traversing unit, and preventing the subsequent type operation from being in error and causing the system to crash.
The terminal device uses the setting module to set and utilize the return result of each network request object to control the initiation of the network requests in the array with the dependency relationship, thereby simplifying the logic relationship between the network requests and facilitating the initiation of the network requests.
Embodiment four:
fig. 4 is a schematic diagram of a structure of a terminal device for sending a network request of a dependency relationship according to an embodiment of the present invention. The terminal device is a mobile computer device with a touch screen, and comprises a smart phone, a smart watch, a notebook, a tablet computer, a POS machine and even a vehicle-mounted computer. As shown in fig. 4, the server 4 of this embodiment includes: memory 410, processor 420, and system bus 430, wherein memory 410 includes an executable program 4101 stored thereon, and those skilled in the art will appreciate that the server architecture shown in fig. 4 is not limiting of servers and may include more or less components than illustrated, or may combine certain components, or a different arrangement of components.
The following describes the respective constituent elements of the terminal device in detail with reference to fig. 4:
the memory 410 may be used to store software programs and modules, and the processor 420 performs various functional applications of the terminal and data processing by executing the software programs and modules stored in the memory 410. The memory 410 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data (such as audio data, phonebooks, etc.) created according to the use of the server, etc. In addition, memory 410 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 volatile solid-state storage device.
An executable 4101 containing network request methods on memory 410, the executable
The sequence 4101 may be partitioned into one or more modules/units that are stored in the memory 410 and executed by the processor 420 to initiate network requests, which may be a series of computer program instruction segments capable of accomplishing specific functions describing the execution of the computer program 4101 in the server 4. For example, the computer program 4101 may be divided into a storage module, a setting module, and an initiating module.
The processor 420 is a control center of the server, connects various parts of the entire terminal device using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and/or modules stored in the memory 410, and calling data stored in the memory 410, thereby performing overall monitoring of the terminal. Optionally, the processor 420 may include one or more processing units; preferably, the processor 420 may integrate an application processor that primarily handles operating systems, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 420.
The system bus 430 is used to connect various functional units inside the computer, and can transfer data information, address information, and control information, and its kind may be, for example, a PCI bus, an ISA bus, a VESA bus, etc. Instructions from the processor 420 are transferred to the memory 410 via the bus, the memory 410 feeds back data to the processor 420, and the system bus 430 is responsible for data and instruction interaction between the processor 420 and the memory 410. Of course, the system bus 430 may also access other devices, such as a network interface, a display device, etc.
The terminal device should at least include a network card, an output device, etc., and other components will not be described herein.
In the embodiment of the present invention, the executable program executed by the terminal device 420 included in the server is specifically:
a network request sending method of a dependency relationship includes:
when a user initiates a network request, storing a network request object with a dependency relationship into a predefined array;
defining a callback function of the network request object, setting in the callback function that when the current network request is successful, controlling the initiation of the next network request according to the return result of the current network request object;
and acquiring a first network request object in the array to initiate a network request.
Further, when the user initiates the network request, storing the network request object with the dependency relationship into the predefined array further includes:
defining a network request class, defining a sending method in the network request class, and instantiating the network request class to generate a network request object when a user initiates a network request.
Further, storing the network request object with the dependency relationship into a predefined array further includes:
creating a classification of the data, setting each network request object in the classification to initiate a network request, and returning a request result to a network request initiating place; and (3) rewriting the system callback method, wherein in the rewritten system callback method, a method for controlling the next network request object to initiate the call is defined according to the request result returned by each network request object.
Further, the controlling the initiation of the next network request according to the return value of the current network request object further includes:
according to the network request result transmitted by the callback of the current network request object, controlling the delay time length initiated by the next network request in the array, wherein the network request result comprises delay time; terminating initiation of the next network request when the delay time is less than zero
Further, before the acquiring the first network request object in the array initiates the network request, the method further includes:
and traversing all elements in the array, and judging whether all elements are of the network request object type.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (9)
1. A method for sending a network request of a dependency relationship, comprising:
when a user initiates a network request, storing a network request object with a dependency relationship into a predefined array;
defining a callback function of the network request object, setting in the callback function that when the current network request is successful, controlling the initiation of the next network request according to the return result of the current network request object;
acquiring a first network request object in the array to initiate a network request;
the step of controlling the initiation of the next network request according to the return value of the current network request object specifically comprises the following steps: according to the network request result transmitted by the callback of the current network request object, controlling the delay time length initiated by the next network request in the array, wherein the network request result comprises delay time; and terminating the initiation of the next network request when the delay time is less than zero.
2. The method of claim 1, wherein storing the network request object having the dependency relationship in the predefined array when the user initiates the network request further comprises:
defining a network request class, defining a sending method in the network request class, and instantiating the network request class to generate a network request object when a user initiates a network request.
3. The method of claim 1, wherein storing the network request object with the dependency in the predefined array further comprises:
creating a class of the array, setting each network request object in the class to initiate a network request, and returning a request result to a network request initiating place;
and (3) rewriting the system callback method, wherein in the rewritten system callback method, a method for controlling the next network request object to initiate the call is defined according to the request result returned by each network request object.
4. The method of claim 1, wherein the obtaining the first network request object in the array before initiating the network request further comprises:
traversing all elements in the array, and judging whether all elements are of the network request object type;
when all elements are of the network request object type, a network request is initiated.
5. A terminal apparatus, comprising:
the storage module is used for storing the network request object with the dependency relationship into a predefined array when a user initiates a network request;
the setting module is used for defining a callback function of the network request object, setting that when the current network request is successful in the callback function, and controlling the initiation of the next network request according to the return result of the current network request object; the step of controlling the initiation of the next network request according to the return value of the current network request object specifically comprises the following steps: according to the network request result transmitted by the callback of the current network request object, controlling the delay time length initiated by the next network request in the array, wherein the network request result comprises delay time; terminating initiation of a next network request when the delay time is less than zero;
and the initiating module is used for acquiring a first network request object in the array to initiate a network request.
6. The terminal device according to claim 5, wherein controlling initiation of a next network request according to the return value of the current network request object further comprises:
creating a class of the array, setting each network request object in the class to initiate a network request, and returning a request result to a network request initiating place;
and (3) rewriting the system callback method, wherein in the rewritten system callback method, a method for controlling the next network request object to initiate the call is defined according to the request result returned by each network request object.
7. The terminal device of claim 5, wherein the initiating module further comprises:
the traversing unit is used for traversing all elements in the array and judging whether the elements are all of the network request object type; when all elements are of the network request object type, a network request is initiated.
8. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor, when executing the computer program, implements the steps of the network request transmission method of the dependency according to any one of claims 1 to 4.
9. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of the network request transmission method of the dependency according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811501788.9A CN111294377B (en) | 2018-12-10 | 2018-12-10 | Dependency network request sending method, terminal device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811501788.9A CN111294377B (en) | 2018-12-10 | 2018-12-10 | Dependency network request sending method, terminal device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111294377A CN111294377A (en) | 2020-06-16 |
| CN111294377B true CN111294377B (en) | 2023-07-04 |
Family
ID=71023112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811501788.9A Active CN111294377B (en) | 2018-12-10 | 2018-12-10 | Dependency network request sending method, terminal device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111294377B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113852647A (en) * | 2020-06-26 | 2021-12-28 | 武汉斗鱼鱼乐网络科技有限公司 | Method, device, medium and equipment for marking network request based on top view |
| CN112422692A (en) * | 2020-11-23 | 2021-02-26 | 平安普惠企业管理有限公司 | Network request method and related device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528257A (en) * | 2016-10-31 | 2017-03-22 | 国云科技股份有限公司 | A method for simplifying and restricting concurrent ajax requests |
| CN107247634A (en) * | 2017-06-06 | 2017-10-13 | 广州视源电子科技股份有限公司 | A kind of method and apparatus of Robotic Dynamic asynchronous remote procedure call |
| CN108234624A (en) * | 2017-12-29 | 2018-06-29 | 贵阳语玩科技有限公司 | The processing method and system of request of data |
| CN108900627A (en) * | 2018-07-19 | 2018-11-27 | 武汉斗鱼网络科技有限公司 | A kind of network request method, terminal installation and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7548974B2 (en) * | 2004-10-12 | 2009-06-16 | International Business Machines Corporation | Adaptively processing client requests to a network server |
-
2018
- 2018-12-10 CN CN201811501788.9A patent/CN111294377B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528257A (en) * | 2016-10-31 | 2017-03-22 | 国云科技股份有限公司 | A method for simplifying and restricting concurrent ajax requests |
| CN107247634A (en) * | 2017-06-06 | 2017-10-13 | 广州视源电子科技股份有限公司 | A kind of method and apparatus of Robotic Dynamic asynchronous remote procedure call |
| CN108234624A (en) * | 2017-12-29 | 2018-06-29 | 贵阳语玩科技有限公司 | The processing method and system of request of data |
| CN108900627A (en) * | 2018-07-19 | 2018-11-27 | 武汉斗鱼网络科技有限公司 | A kind of network request method, terminal installation and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111294377A (en) | 2020-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018137564A1 (en) | Service processing method and apparatus | |
| CA3000422C (en) | Workflow service using state transfer | |
| US20200328984A1 (en) | Method and apparatus for allocating resource | |
| CN107832100B (en) | APK plug-in loading method and terminal thereof | |
| CN109951547B (en) | Transaction request parallel processing method, device, equipment and medium | |
| US10666758B2 (en) | Browser resource pre-pulling method, terminal and storage medium | |
| CN109309712B (en) | Data transmission method based on interface asynchronous call, server and storage medium | |
| CN107689976B (en) | File transmission method and device | |
| CN104239156A (en) | External service call method and system | |
| CN111277639A (en) | Method and device for maintaining data consistency | |
| CN108900627B (en) | Network request method, terminal device and storage medium | |
| CN113961346A (en) | Data cache management and scheduling method and device, electronic equipment and storage medium | |
| CN111294377B (en) | Dependency network request sending method, terminal device and storage medium | |
| WO2009143105A2 (en) | Method and apparatus for providing a synchronous interface for an asynchronous service | |
| CN109725887B (en) | Data interaction method and device based on message research and development framework and terminal equipment | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN110764930B (en) | Request or response processing method and device based on message mode | |
| CN113297305A (en) | Session state processing method, device, equipment and storage medium | |
| CN112241398A (en) | Data migration method and system | |
| CN113779122B (en) | Method and device for exporting data | |
| CN113760487B (en) | Service processing method and device | |
| CN108809763B (en) | Network performance parameter acquisition method, terminal device and storage medium | |
| CN113032118A (en) | Asynchronous operation processing method for computer application program and corresponding system | |
| CN114817166B (en) | Method, device and medium for canceling file operation | |
| CN111400060A (en) | Equipment linkage method, device, server and 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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230612 Address after: 518000, Floor B9 and B10, Building 1, Xinsheng Green Valley, No. 2380 Bixin Road, Xinsheng Community, Longgang Street, Longgang District, Shenzhen, Guangdong Province Applicant after: SHENZHEN LIANRUI ELECTRONICS Co.,Ltd. Address before: 430000 East Lake Development Zone, Wuhan City, Hubei Province, No. 1 Software Park East Road 4.1 Phase B1 Building 11 Building Applicant before: WUHAN DOUYU NETWORK TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |