WO2019019249A1 - Method, apparatus and device for executing network request, and computer-readable storage medium - Google Patents

Abstract

Provided are a method, apparatus and device for executing a network request, and a computer-readable storage medium. The method comprises: if an application program is started, creating a management centre capable of executing a network request of the application program; if it is detected that the application program is to send a network request, determining whether the network request is a pre-set type of network request; if the network request is a pre-set type of network request, controlling the application program so that same sends the network request to the management centre; and the management centre controlling the application program so that same displays a state after the network request is successfully executed and executes the network request. In the embodiments of the present invention, if it is detected that the network request to be sent by the application program is a pre-set type of network request, the management centre controls the application program so that same displays the state after the network request is successfully executed and executes the network request, thereby reducing the time for which a user waits for data loading of the network request, and improving user experience.

Description

 Method, device, device and computer readable storage medium for performing network request

This application claims the priority of the Chinese Patent Application filed on July 24, 2017, the Chinese Patent Application No. 201710607890.6, entitled "A Method for Performing a Network Request, a Terminal, and a Computer-Readable Storage Medium", all of which are The content is incorporated herein by reference.

Technical field

The present invention relates to the field of electronic device technologies, and in particular, to a method, an apparatus, a device, and a computer readable storage medium for performing a network request.

Background technique

With the development of the mobile Internet, mobile applications have been widely used, but the experience is mixed. For example, when the application executes a network request and loads the data requested by the network, the loaded pattern will pop up, and the loaded image will hinder the user from further operations. If the network condition is not ideal, at this time, because the display of the loaded image, the user cannot touch the button on the page of the application, the user needs to wait for a long time to load all the data requested by the network, in order to proceed to the next step. Obviously in this case, the user experience is very bad.

Summary of the invention

The embodiment of the invention provides a method, a device, a device and a computer readable storage medium for executing a network request, which can save time for the user to wait for the network to request data loading, and improve the user experience.

In a first aspect, an embodiment of the present invention provides a method for performing a network request, where the method includes:

If the application launches, create a management center that can execute the application network request;

If it is detected that the application is to send a network request, determine whether the network request is a preset type of network request;

If the network request is a preset type of network request, controlling the application to send the network request to the management center;

The management center controls the application to display a status after the network request is successfully executed and execute the network request.

In a second aspect, an embodiment of the present invention provides an apparatus for performing a network request, where the apparatus includes:

Creating a unit for creating a management center that can execute the application network request if the application is started;

a determining unit, configured to determine, if the application is to send a network request, whether the network request is a preset type of network request;

a control sending unit, configured to: if the network request is a preset type of network request, control the application to send the network request to the management center;

The management center is configured to control the application to display a status after the network request is successfully executed and execute the network request.

In a third aspect, an embodiment of the present invention provides a device for performing a network request, where the device includes: a memory and a processor; the memory stores executable program data; and the processor is configured to run the storage in the memory. The program data is to perform the method of the first aspect above.

In a fourth aspect, an embodiment of the present invention provides a computer readable storage medium, where the one or more program data is stored, and the one or more program data may be processed by one or more processes. The apparatus is executed to implement the method described in the first aspect above.

In the embodiment of the present invention, when the application is started, the management center of the application is created. If it is detected that the application is to send a network request, it is determined whether it is a preset type of network request, and if so, the management center control application displays that the network request is successfully executed. The subsequent state and execution of the network request saves the time for the user to wait for the network to request data loading, thereby improving the user experience.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are some embodiments of the present invention. For the ordinary technicians, other drawings can be obtained based on these drawings without any creative work.

FIG. 1 is a schematic flowchart of a method for executing a network request according to an embodiment of the present invention;

2 is a schematic flowchart of a sub-method of a method for executing a network request according to an embodiment of the present invention;

3 is a schematic flow chart of another sub-method of a method for executing a network request according to an embodiment of the present invention;

4 is a schematic block diagram of an apparatus for executing a network request according to an embodiment of the present invention;

FIG. 5 is a schematic block diagram of a management center according to an embodiment of the present invention; FIG.

6 is a schematic block diagram of a management center according to another embodiment of the present invention;

FIG. 7 is a schematic block diagram of a management center according to another embodiment of the present invention; FIG.

FIG. 8 is a schematic block diagram of an apparatus for performing a network request according to an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

It will be understood that the terms "comprise" and "the" when used in the specification and the appended claims "Comprising" indicates the existence of the described features, integers, steps, operations, elements and/or components, but does not exclude the presence of one or more other features, integers, steps, operations, elements, components and/or combinations thereof Add to.

It should also be understood that the term "and / is used in the description of the invention and the appended claims. Or "" refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

In a specific implementation, the device described in the embodiments of the present invention includes, but is not limited to, a portable device such as a mobile phone, a laptop computer or a tablet computer that can execute an application. It should also be understood that in some embodiments, the device is not a portable communication device, but also includes a desktop computer, television, etc., that can execute an application. The device can install and execute various applications.

FIG. 1 is a schematic flowchart diagram of a method for executing a network request according to an embodiment of the present invention. The method includes S101~S104.

S101. If the application is started, create a management center that can execute an application network request. Among them, the management center is created in the local background of the application, and the management center is part of the application. Creating a management center includes opening up storage space, configuring and saving some parameters, and more. The Management Center is created each time the application is launched. Each time the application is closed, the management center is destroyed to ensure that the management center is not destroyed and consumes device resources if the application is not started. In the management center, you can configure and save related parameters for executing network requests, such as preset number, preset time, preset number, and so on.

S102. If it is detected that the application is to send a network request, determine whether the network request is a preset type of network request. The network request includes many parameters, such as the interface to be sent, the amount of data to be sent, the protocol used, the destination address, the type of network request data, and some other parameters, such as the priority of the network request. Determining whether the network request is a preset type of network request according to a parameter of the network request, wherein the preset type of network request refers to non-real-time or low-time requirements, and does not need to be quickly associated with other devices such as a server. There are further interactive network requests. For the WeChat application, the network request can send a circle of friends, a circle of friends sent by WeChat friends, a message of a friend circle, a message of a favorite message or a WeChat open, and a modified WeChat profile.

S103. If the network request is a preset type of network request, the control application sends the network request to the management center. The control application sends the network request to the management center to save the network request in the management center and obtain a unique identifier assigned by the management center for the network request. If the network request is not a preset type of network request, a network request is sent to the server.

S104. The management center control application displays a status after the network request is successfully executed and executes the network request. For example, if the network request requests the friend circle message sent by the WeChat friend, the management center control application displays the status of the like success, and executes the network request that the friend circle liked for the WeChat friend. It can be understood that the network request is not actually executed, and the state after the network request is successfully executed is displayed first; then the management center executes the network request. In this way, if the network condition is not good, the user does not have to wait for the network request to be successfully executed, and the user can obtain more time to perform other operations in the next step, thereby improving the user experience.

In the foregoing embodiment, when the application is started, the management center of the application is created, and if it is detected that the application is to send a network request, it is determined whether it is a preset type of network request, and if so, the management center control application displays that the network request is successfully executed. The state and execution of the network request saves the time for the user to wait for the network to request data loading, which improves the user experience.

Specifically, as shown in FIG. 2, S104 includes S201-S207 to further define how the management center controls the application to display the state after the network request is successfully executed and execute the network request. The related parameters of the network request, including the preset time, the preset number of times, and the suspension waiting time, can be configured and saved in the management center. The preset time can be understood as the time when the request instance is executed once. One request instance can be executed once to send the network request only once, and can also send the network request multiple times; the preset number can be understood as the number of times the network request is automatically executed.

S201. Create a request instance of the network request to control an application to display a status after the network request is successfully executed. In some embodiments, the priority of the request instance is included in the request instance of the network request, and the preset time corresponding to the request instance, the preset number of times corresponding to the request instance, the suspension waiting time corresponding to the request instance, and the like. . For the same application, different preset times, preset times, and pause waiting times can be set for request instances of different priorities. If the amount of data corresponding to the request instance is large, such as uploading multiple images, the preset time and the preset number of times corresponding to the request instance are larger. In the actual execution, if there are related parameters such as a preset time, a preset number of times, and a suspension waiting time in the request instance of the network request, the relevant parameters in the request instance are taken as the priority, for example, the priority in the request instance is obtained. The preset time, the preset number of times, and the waiting time for the request instance. If there is no relevant parameter in the request instance of the network request, the relevant parameters of the network request configured by the management center shall prevail. The priority of the request instance can be determined according to the function of the application. If there are 5 different requests in the same webpage, according to the function of the application, if the application mainly displays images, the request instance requesting the display image has a higher priority than the request instance corresponding to the request data. level. In other embodiments, for the same application, the same preset time, the preset number of times, the suspension waiting time, and the like may be set for the request instances of different priorities. In other embodiments, the preset time, the preset number of times, and the like corresponding to the request instance may be the same or different for different applications. If the request instance of the network request is successfully created, the control application displays the status after the network request is successfully executed. For the WeChat application, if the network request is a friend circle sent by the WeChat friend, if the request instance of the network request is successfully created, the callback function of the request instance creation success will cause the front end of the application to display that the network request is successfully executed. The state of the point, that is, the state of success.

S202. Determine whether the number of network requests being executed reaches a preset number. The management center can perform multiple network requests at the same time to determine whether the number of network requests being executed reaches a preset number. If the preset number is reached, S203 is performed; if the preset number is not reached, S204 is performed. If no network request is currently being performed, the number of network requests being executed is zero. The management center can execute multiple network requests at the same time, maximizing the utilization of network resources and improving the efficiency of executing network requests.

S203. Put the request instance into a corresponding waiting queue according to the priority of the request instance, and wait for execution. The request instance is divided into different priorities, and the request instances in the corresponding waiting queues with higher priority are preferentially executed to improve the user experience. Then, S202 is executed to determine whether the request instance can be executed. For example, in the process of waiting, if the request instance is successfully executed, the number of network requests being executed does not reach the preset number, and the request instance in the waiting queue can be taken out. Perform a network request.

S204. Perform a network request according to the request instance.

S205. Determine whether the network request is successfully executed. If the network request is successfully executed, S206 is performed; otherwise, S207 is performed.

S206. Delete the request instance.

S207. Perform a network request again according to the request instance. If the network request is not successfully executed, then the network request is executed again according to the request instance. Then judge whether the network request is executed successfully.

In other embodiments, the number of times the network request is executed according to the request instance is not specifically limited, such as three times.

In the above embodiment, when the management center performs the network request, if the number of network requests being executed by the management center reaches a preset number, the request instance is placed in the corresponding waiting queue according to the priority of the request instance, and the execution is performed. The number is set, the network request is executed according to the request instance; the network request is successfully executed, and if the execution is successful, the request instance is deleted, and if the execution is not successful, the network request is executed according to the request instance again. The foregoing embodiment may perform a network request according to the priority of the request instance, so as to preferentially process more important network requests and improve the user experience; and, multiple network requests are simultaneously executed, and the network resources are utilized to the maximum, and the efficiency of executing the network request is improved. In addition, if the network request is not successfully executed, the network request is automatically re-executed according to the request instance, and the network request is automatically executed multiple times, which ensures that the network request can be successfully executed without the user clicking to re-execute, thereby improving the user experience.

3 is a flow chart of method steps after the management center performs the network request multiple times according to the request instance, wherein the multiple times do not exceed the preset number of times, and are associated with the number of execution network requests of the embodiment of FIG. 2 . If the number of times the network request is executed in the embodiment of FIG. 2 is two times, then the multiple times of the embodiment are referred to twice; if the number of times the embodiment of FIG. 2 executes the network request is three times, then the multiple times of the embodiment refers to three times. Preferably, the number of times the network request is executed by the embodiment of FIG. 2 is two times, and the multiple times of the location are referred to twice. Preferably, the preset number of times is five times. As shown in FIG. 3, the step after the management center performs the network request according to the request instance multiple times is still unsuccessful, and includes S301-S310.

S301. If the network request is not successfully executed, determine whether the number of times the network request is executed according to the request instance reaches a preset number of times. If the preset number of times is not reached, S302 is performed; if the preset number of times is reached, S307 is performed.

S302: Put the request instance into a corresponding suspension queue according to the priority of the request instance. Put the request instance into the corresponding deferred queue, and continue to execute the network request according to the request instance after the interval is suspended, thereby increasing the probability of successful execution of the network request.

S303. Determine whether the waiting time is reached. If the waiting time is reached, S304 is executed; if the waiting time is not reached, it is determined whether the waiting time is reached.

S304. The request instance is taken out from the suspension queue and the network request is executed according to the request instance.

S305. Determine whether the network request is successfully executed. If the network request is successfully executed, S306 is performed; if the execution is not successful, S301 is performed.

S306. Delete the request instance.

S307. Destroy the request instance and obtain the reason why the network request is not successfully executed. If the number of times the network request is executed according to the request instance reaches a preset number, and the request instance is destroyed and the reason why the network request is not successfully executed is obtained, it is preferable to return the reason why the last execution of the network request failed. Among them, the reasons include the interface not found, the page not found, the network interruption, and so on.

S308. Determine, according to the reason, whether a request instance that is identical to the request instance needs to be re-created. If it needs to be re-created, execute S310; if it is not necessary to re-create, execute S309. If the reason for the network request not being successfully executed is that the interface cannot be found, the page cannot be found, etc., there is no need to recreate a request instance that is identical to the request instance. If the cause is a network outage, etc., then you need to recreate a request instance that is identical to the request instance.

S309. The control application displays the state before the network request is successfully executed. If it is not necessary to re-create a request instance that is identical to the request instance, the application is controlled according to the unique identifier to display the state before the network request was successfully executed, that is, the state after the successful execution of the network request is revoked.

S310. Create a request instance of the network request. If you need to re-create a request instance that is identical to the request instance, create a request instance for the network request to request more requests from the network to increase the probability of successful network request execution. After the creation is completed, the process returns to S202, that is, the step of determining whether the number of network requests can be simultaneously executed reaches a preset number.

After the network request is not successfully executed, the foregoing embodiment determines whether the number of times the network request is executed according to the request instance reaches a preset number. If the preset number of times is not reached, the network request is suspended, and the interval is suspended after the waiting time continues. The network request is executed to increase the probability that the network request is successfully executed. If the preset number of times is reached, the execution fails within the preset number of times, and the reason why the network request is not successfully executed is obtained. According to the reason, it is determined whether it is necessary to re-create a request instance that is identical to the request instance. If re-creation is required, a request instance of the network request is created to request more request opportunities for the network, thereby increasing the probability of success of the network request execution; There is no need to recreate, undoing the state after the successful execution of the network request.

FIG. 4 is a schematic block diagram of an apparatus for performing a network request according to an embodiment of the present invention. The device 40 includes a creating unit 401, a determining unit 402, a control transmitting unit 403, and a management center 404.

The creating unit 401 is configured to create a management center that can execute an application network request if the application is started. Among them, the management center is created in the local background of the application, and the management center is part of the application. Creating a management center includes opening up storage space, configuring and saving some parameters, and more. The Management Center is created each time the application is launched. Each time the application is closed, the management center is destroyed to ensure that the management center is not destroyed and consumes device resources if the application is not started. In the management center, you can configure and save related parameters for executing network requests, such as preset number, preset time, preset number, and so on.

The determining unit 402 is configured to determine, if the application is to send a network request, whether the network request is a preset type of network request. The network request includes many parameters, such as the interface to be sent, the amount of data sent, the protocol used, the destination address, etc., and some other parameters, such as the priority of the network request. Determining whether the network request is a preset type of network request according to a parameter of the network request, wherein the preset type of network request refers to non-real-time or low-time requirements, and does not need to be quickly associated with other devices such as a server. There are further interactive network requests. For the WeChat application, the network request can send a circle of friends, a circle of friends sent by WeChat friends, a message of a friend circle, a message of a favorite message or a WeChat open, and a modified WeChat profile.

The control sending unit 403 is configured to: if the network request is a preset type of network request, the control application sends the network request to the management center. The control application sends the network request to the management center to save the network request in the management center and obtain a unique identifier assigned by the management center for the network request.

The management center 404 is used to control the application to display the status after the network request is successfully executed and execute the network request. For example, if the network request requests the friend circle message sent by the WeChat friend, the management center control application displays the status of the like success, and executes the network request that the friend circle liked for the WeChat friend. It can be understood that the network request is not actually executed, and the state after the network request is successfully executed is displayed first; then the management center executes the network request. In this way, if the network condition is not good, the user does not have to wait for the network request to be successfully executed, and the user can obtain more time to perform other operations in the next step, thereby improving the user experience.

In the foregoing embodiment, when the application is started, the management center of the application is created, and if it is detected that the application is to send a network request, it is determined whether it is a preset type of network request, and if so, the management center control application displays that the network request is successfully executed. The state and execution of the network request saves the time for the user to wait for the network to request data loading, which improves the user experience.

5 is a schematic block diagram of a management center that defines how to control an application to display a status after the network request is successfully executed and execute the network request. As shown in FIG. 5, the management center 50 includes a request instance creation unit 501, a control determination unit 502, a waiting unit 503, a request execution unit 504, a deletion unit 505, and a storage unit 506. The storage unit 506 is configured to save the request instance, and save the related parameters of the configured network request, and the related parameters of the network request include a preset time, a preset number of times, a suspension waiting time, and the like. The preset time can be understood as the time when the request instance is executed once. One request instance can be executed once to send the network request only once, and can also send the network request multiple times; the preset number can be understood as the number of times the network request is automatically executed.

The request instance creation unit 501 is configured to create a request instance of the network request to control the state of the application after the network request is successfully executed. In some embodiments, the priority of the request instance is included in the request instance of the network request, and the preset time corresponding to the request instance, the preset number of times corresponding to the request instance, the suspension waiting time corresponding to the request instance, and the like. . For the same application, different preset times, preset times, and pause waiting times can be set for request instances of different priorities. If the amount of data corresponding to the request instance is large, such as uploading multiple images, the preset time and the preset number of times corresponding to the request instance are larger. In the actual execution, if there are related parameters such as a preset time, a preset number of times, and a suspension waiting time in the request instance of the network request, the relevant parameters in the request instance are taken as the priority, for example, the priority in the request instance is obtained. The preset time, the preset number of times, and the waiting time for the request instance. If there is no relevant parameter in the request instance of the network request, the relevant parameters of the network request configured by the management center shall prevail. The priority of the request instance can be determined according to the function of the application. If there are 5 different requests in the same webpage, according to the function of the application, if the application mainly displays images, the request instance requesting the display image has a higher priority than the request instance corresponding to the request data. level. In other embodiments, for the same application, the same preset time, the preset number of times, the suspension waiting time, and the like may be set for the request instances of different priorities. In other embodiments, the preset time, the preset number of times, and the like corresponding to the request instance may be the same or different for different applications. If the request instance of the network request is successfully created, the control application displays the status after the network request is successfully executed. For the WeChat application, if the network request is a friend circle sent by the WeChat friend, if the request instance of the network request is successfully created, the callback function will cause the front end of the application to display the state after the network request is successfully executed, that is, the point. Praise the state of success.

The control judging unit 502 is configured to judge whether the number of network requests being executed reaches a preset number. The management center can simultaneously execute multiple network requests to determine whether the number of network requests being executed reaches a preset number. If no network request is currently being performed, the number of network requests being executed is zero. The management center can execute multiple network requests at the same time, maximizing the utilization of network resources and improving the efficiency of executing network requests.

The waiting unit 503 is configured to: if the number of network requests being executed reaches a preset number, put the request instance into a corresponding waiting queue according to the priority of the request instance, and wait for execution. The request instance is divided into different priorities, and the request instances in the corresponding waiting queues with higher priority are preferentially executed to improve the user experience. Then, the control judgment unit is triggered to determine whether the request instance can be executed. For example, in the process of waiting, if the request instance is successfully executed, the number of network requests being executed does not reach the preset number, and the request in the waiting queue can be taken out. An instance to execute a network request.

The request execution unit 504 is configured to execute a network request according to the request instance if the number of network requests being executed does not reach a preset number. In addition, if in the process of waiting, if the request instance is successfully executed, the number of simultaneous network requests that the management center can execute at the same time does not reach the preset number, and the request instance in the waiting queue can be taken out to execute the network request.

The control determining unit 502 is further configured to determine whether the network request is successfully executed.

The deleting unit 505 is configured to delete the request instance if the network request is successfully executed.

The request execution unit 504 is further configured to perform a network request according to the request instance again if the network request execution fails. If the request instance is not successfully executed, the network request is executed again according to the request instance. Then, the judging unit is triggered to judge whether the network request is successfully executed.

In the above embodiment, when the management center performs the network request, if the number of network requests being executed by the management center reaches a preset number, the request instance is placed in the corresponding waiting queue according to the priority of the request instance, and the execution is performed. The number is set, the network request is executed according to the request instance; the network request is successfully executed, and if the execution is successful, the request instance is deleted, and if the execution is not successful, the network request is executed according to the request instance again. The foregoing embodiment may perform a network request according to the priority of the request instance, so as to preferentially process more important network requests and improve the user experience; and, multiple network requests are simultaneously executed, and the network resources are utilized to the maximum, and the efficiency of executing the network request is improved. In addition, if the network request is not successfully executed, the network request is automatically re-executed according to the request instance, and is automatically executed multiple times, which ensures that the network request can be successfully executed without the user clicking to re-execute, thereby improving the user experience.

FIG. 6 is a schematic block diagram of a management center according to another embodiment of the present invention. The management center 60 includes a request instance creation unit 601, a control determination unit 602, a waiting unit 603, a request execution unit 604, a deletion unit 605, a storage unit 606, and a suspension unit 607. The main difference between the management center 60 and the management center 50 in the embodiment of FIG. 5 is that the suspension unit 607 is added. The request instance creation unit 601, the control determination unit 602, the waiting unit 603, the request execution unit 604, the deletion unit 605, and the storage unit 606 refer to the description of the embodiment of FIG. 5, and details are not described herein again. The difference between this embodiment and the embodiment of Figure 5 is that:

The control determining unit 602 is further configured to determine whether the number of times the network request is executed according to the request instance reaches a preset number of times if the network request is not successfully executed multiple times. Wherein, the number of times does not exceed a preset number of times, and is associated with the number of times the network request is executed in the embodiment of FIG. 2. If the number of times the network request is executed in the embodiment of FIG. 2 is two times, then the multiple times of the embodiment are referred to twice; if the number of times the embodiment of FIG. 2 executes the network request is three times, then the multiple times of the embodiment refers to three times. Preferably, the number of times the network request is executed by the embodiment of FIG. 2 is two times, and the multiple times of the location are referred to twice.

The suspending unit 607 is configured to: when the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is placed in the corresponding suspension queue according to the priority of the request instance. Put the request instance into the corresponding deferred queue, and continue to execute the network request according to the request instance after the interval is suspended, thereby increasing the probability of successful execution of the network request.

The control judging unit 602 is further configured to determine whether the suspension waiting time is reached.

The suspension unit 607 is further configured to: if the suspension waiting time is reached, take the request instance from the suspension queue and execute the network request according to the request instance. Then, the judging unit is triggered to judge whether the network request is successfully executed.

The deleting unit 605 is further configured to delete the request instance if the network request is successfully executed. If the network request is not successfully executed, the determining unit is triggered to determine whether the number of times the network request is executed reaches a preset number of times.

FIG. 7 is a schematic block diagram of a management center according to another embodiment of the present invention. The management center 70 includes a request instance creation unit 701, a control determination unit 702, a waiting unit 703, a request execution unit 704, a deletion unit 705, a storage unit 706, a suspension unit 707, a destruction unit 708, and a restoration unit 709. The main difference between the management center 70 and the management center 60 in the embodiment of FIG. 6 is that the destruction unit 708 and the restoration unit 709 are added. The request instance creation unit 701, the control determination unit 702, the waiting unit 703, the request execution unit 704, the deletion unit 705, the storage unit 706, and the suspension unit 707 are referred to the description of the embodiment of FIG. 6, and details are not described herein again. The difference between this embodiment and the embodiment of Fig. 6 is that:

The destroying unit 708 is configured to: if the number of times the network request is executed according to the request instance reaches a preset number of times, destroy the request instance, and obtain a reason why the network request is not successfully executed. It is preferable to return the reason why the last execution of the network request failed. Among them, the reasons include the interface not found, the page not found, the network interruption, and so on.

The control determining unit 702 is further configured to determine, according to the reason, whether a request instance that is identical to the request instance needs to be re-created. If the reason is that the interface is not found, the page is not found, etc., there is no need to recreate a request instance that is identical to the request instance. If the cause is a network outage, etc., then you need to recreate a request instance that is identical to the request instance.

The restore unit 709 is configured to control the application to display the state before the network request was successfully executed without re-creating a request instance that is identical to the request instance. The application is controlled according to the unique identifier to display the state before the execution of the network request is successful, that is, to undo the state after the successful execution of the network request.

The request instance creation unit 701 is further configured to create a request instance of the network request if it is necessary to re-create a request instance that is identical to the request instance. Create a request instance for the network request again to request more requests from the network, increasing the chances of successful network request execution. After the creation is completed, the control determination unit is triggered to determine whether the number of network requests being executed reaches a preset number.

The above apparatus for executing a network request can be implemented in the form of a computer program that can be run on a device as shown in FIG.

FIG. 8 is a schematic block diagram of an apparatus for performing a network request according to an embodiment of the present invention. The device 80 includes one or more input devices 801; one or more output devices 802, one or more memories 803, and one or more processors 804. The input device 801, the output device 802, the memory 803, and the processor 804 are connected by a bus 805. among them:

The input device 801 is configured to provide a request for the user to send a network request, and provide a request instance for the user to re-send the network request. In a specific implementation, the input device 801 of the embodiment of the present invention may include a keyboard, a mouse, a photoelectric input device, a sound input device, a touch input device, and the like.

The output device 802 is configured to display a status after the execution of the network request is successful, a reason why the network request is not successfully executed, and the like. In a specific implementation, the output device 802 of the embodiment of the present invention may include a display, a display screen, a touch screen, a sound output device, and the like.

The memory 803 is used to store program data that implements a network request. The network request, the request instance, the priority of the request instance, the preset time, the preset number, the preset number of times, the suspension waiting time, the suspension queue, the waiting queue, the number of simultaneous execution of the network request, etc., and the callable The program that runs. In a specific implementation, the memory 803 of the embodiment of the present invention may be a system memory, such as a non-volatile (such as a ROM, a flash memory, etc.). In a specific implementation, the memory 803 of the embodiment of the present invention may also be an external memory outside the system, such as a magnetic disk, an optical disk, a magnetic tape, or the like.

The processor 804 is configured to run program data stored in the memory 803 to perform the following steps:

If the application is started, creating a management center that can execute the application network request; if detecting that the application is to send a network request, determining whether the network request is a preset type of network request; if the network request is a preset a type of network request that controls the application to send the network request to the management center; the management center controls the application to display a status after the network request is successfully executed and execute the network request.

The processor 804 also performs the following steps:

Creating a request instance of the network request to control an application to display a status after the network request is successfully executed; determining whether the number of network requests being executed reaches a preset number; if the preset quantity is not reached, according to the request instance Executing a network request; determining whether the network request is successfully executed; if the network request is successful, deleting the request instance; if the network request is not successfully executed within a preset time, performing a network request according to the request instance again.

The processor 804 also performs the following steps:

Determining whether the number of times the network request is executed according to the request instance reaches a preset number of times; if the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is put into the suspension queue; determining whether the waiting time is reached If the hold wait time is reached, the request instance is fetched from the hold queue and a network request is performed according to the request instance.

The processor 804 also performs the following steps:

If the number of times the network request is executed according to the request instance reaches a preset number of times, destroying the request instance, and obtaining a reason why the network request is not successfully executed; determining, according to the reason, whether to re-create a request that is identical to the request instance. Requesting an instance; if there is no need to re-create, the control application displays the state before the network request was successfully executed; if it is to be re-created, the request instance is created and the number of network requests that are determined to be executing is returned to a preset number step.

The processor 804 also performs the following steps:

If the number of network requests being executed by the management center exceeds a preset number, the request instance is put into a waiting queue according to the priority of the request instance to wait for execution; if the network request is executed according to the request instance, the number of times is not executed. If the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is put into the corresponding one according to the priority of the request instance. Deferred queue.

The present invention also provides a computer readable storage medium storing one or more program data, the one or more program data being executable by one or more processors, Implement the following steps:

If the application is started, creating a management center that can execute the application network request; if detecting that the application is to send a network request, determining whether the network request is a preset type of network request; if the network request is a preset a type of network request that controls the application to send the network request to the management center; the management center controls the application to display a status after the network request is successfully executed and execute the network request.

In one of the embodiments, the program data may be executed by the processor to implement the following steps:

Creating a request instance of the network request to control an application to display a status after the network request is successfully executed; determining whether the number of network requests being executed reaches a preset number; if the preset quantity is not reached, according to the request instance Executing a network request; determining whether the network request is successfully executed; if the network request is successful, deleting the request instance; if the network request is not successfully executed within a preset time, performing a network request according to the request instance again.

In one of the embodiments, the program data may be executed by the processor to implement the following steps:

Determining whether the number of times the network request is executed according to the request instance reaches a preset number of times; if the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is put into the suspension queue; determining whether the waiting time is reached If the hold wait time is reached, the request instance is fetched from the hold queue and a network request is performed according to the request instance.

In one of the embodiments, the program data may be executed by the processor to implement the following steps:

If the number of times the network request is executed according to the request instance reaches a preset number of times, destroying the request instance, and obtaining a reason why the network request is not successfully executed; determining, according to the reason, whether to re-create a request that is identical to the request instance. Requesting an instance; if it is not necessary to re-create, the control application displays the state before the network request was successfully executed; if it is to be re-created, the request instance is created, and the number of network requests that determine whether the network request is being executed reaches a preset number A step of.

In one of the embodiments, the program data may be executed by the processor to implement the following steps:

If the number of network requests being executed by the management center exceeds a preset number, the request instance is put into a waiting queue according to the priority of the request instance to wait for execution; if the network request is executed according to the request instance, the number of times is not executed. If the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is put into the corresponding one according to the priority of the request instance. Deferred queue.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the device, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again. Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, for clarity of hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface or unit, or may be an electrical, mechanical or other form of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. Including several instructions to make a device (may be a personal computer, server, mobile device or network device, etc.) Performing all or part of the steps of the method described in various embodiments of the present invention. The foregoing storage medium includes: a USB flash drive, a mobile hard disk, and a read only memory. (ROM, Read-Only Memory), disk or optical disc, etc. Various media that can store program code.

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any equivalent person can be easily conceived within the technical scope of the present invention by any person skilled in the art. Modifications or substitutions are intended to be included within the scope of the invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims (20)

A method for performing a network request, the method comprising: If the application launches, create a management center that can execute the application network request; If it is detected that the application is to send a network request, determine whether the network request is a preset type of network request; If the network request is a preset type of network request, controlling the application to send the network request to the management center; The management center controls the application to display a status after the network request is successfully executed and execute the network request. The method according to claim 1, wherein the management center controls the application to display a status after the network request is successfully executed and executes the network request, including: Creating a request instance of the network request to control an application to display a status after the network request is successfully executed; Determining whether the number of network requests being executed reaches a preset number; If the preset number is not reached, the network request is executed according to the request instance; Determine whether the network request is executed successfully; If the network request is successfully executed, deleting the request instance; If the network request is not successfully executed within the preset time, the network request is executed again according to the request instance. The method of claim 2, wherein the method further comprises: If the network request is not successfully executed, determine whether the number of times the network request is executed according to the request instance reaches a preset number of times; If the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is placed in the deferred queue; Determine whether the waiting time is reached; If the hold wait time is reached, the request instance is fetched from the hold queue and a network request is performed according to the request instance. The method of claim 3, wherein the method further comprises: If the number of times the network request is executed according to the request instance reaches a preset number of times, destroying the request instance, and obtaining a reason why the network request is not successfully executed; Determining, according to the reason, whether a request instance that is identical to the request instance needs to be re-created; Controlling the application to display the state before the network request was successfully executed if no re-creation is required; If re-creation is required, a request instance is created; and the step of determining whether the number of network requests being executed reaches a preset number is returned. The method of claim 3, wherein the request instance includes a priority, the method further comprising: If the number of network requests being executed by the management center exceeds a preset number, placing the request instance into a waiting queue according to the priority of the request instance; If the number of times the network request is executed according to the request instance does not reach the preset number of times, placing the request instance into the suspension queue includes: if the number of times the network request is executed according to the request instance does not reach a preset number, according to the request The priority of the instance puts the request instance into the corresponding deferred queue. An apparatus for performing a network request, the apparatus comprising: Creating a unit for creating a management center that can execute the application network request if the application is started; a determining unit, configured to determine, if the application is to send a network request, whether the network request is a preset type of network request; a control sending unit, configured to: if the network request is a preset type of network request, control the application to send the network request to the management center; The management center is configured to control the application to display a status after the network request is successfully executed and execute the network request. The device according to claim 6, wherein the management center comprises a request instance creation unit, a control determination unit, a request execution unit, a deletion unit, and a storage unit; The request instance creation unit is configured to create a request instance of the network request to control an application to display a state after the network request is successfully executed; The control determining unit is configured to determine whether the number of network requests being executed reaches a preset number; The request execution unit is configured to execute a network request according to the request instance if the number of network requests being executed does not reach a preset number; The control determining unit is further configured to determine whether the network request is successfully executed; The deleting unit is configured to delete the request instance if the network request is successfully executed; The request execution unit is configured to perform a network request according to the request instance again if the network request is not successfully executed within a preset time; The storage unit is configured to store a request instance and a related parameter of the network request, where the related parameter includes a preset quantity. The device according to claim 7, wherein the management center further comprises a suspension unit, wherein the related parameters further include a preset number of times and a suspension waiting time: The control determining unit is further configured to determine whether the number of times the network request is executed according to the request instance reaches a preset number of times; The suspending unit is configured to put the request instance into a deferred queue if the number of times the network request is executed according to the request instance does not reach a preset number of times; The control determining unit is further configured to determine whether the suspension waiting time is reached; The suspension unit is further configured to: if the suspension waiting time is reached, take the request instance from the suspension queue and execute a network request according to the request instance. The device according to claim 8, wherein the management center further comprises: a destruction unit and a restoration unit; wherein The destruction unit is configured to: if the number of times the network request is executed according to the request instance reaches a preset number of times, destroy the request instance, and obtain a reason why the network request is not successfully executed; The control determining unit is further configured to determine, according to the reason, whether a request instance that is identical to the request instance needs to be re-created; The restoring unit is configured to control the application to display a state before the network request is successfully executed if it is not necessary to re-create a request instance that is identical to the request instance; The request instance creation unit is further configured to create a request instance if it is necessary to re-create a request instance that is identical to the request instance; and then trigger a control determination unit to determine whether the number of network requests being executed reaches a preset number. The apparatus according to claim 8, wherein the request instance comprises a priority, and the management center further comprises: a waiting unit; wherein The waiting unit is configured to: if the number of network requests being executed by the management center exceeds a preset number, put the request instance into a waiting queue and wait for execution according to the priority of the request instance; The request execution unit is further configured to: if the number of times the network request is executed according to the request instance does not reach a preset number of times, put the request instance into a corresponding suspension queue according to the priority of the request instance. A device for performing a network request, the device comprising: a memory and a processor; the memory storing program data for implementing a network request; the processor for running the program stored in the memory Data to perform the following steps: If the application launches, create a management center that can execute the application network request; If it is detected that the application is to send a network request, determine whether the network request is a preset type of network request; If the network request is a preset type of network request, controlling the application to send the network request to the management center; The management center controls the application to display a status after the network request is successfully executed and execute the network request. The device of claim 11 wherein said processor further performs the following steps: Creating a request instance of the network request to control an application to display a status after the network request is successfully executed; Determining whether the number of network requests being executed reaches a preset number; If the preset number is not reached, the network request is executed according to the request instance; Determine whether the network request is executed successfully; If the network request is successfully executed, deleting the request instance; If the network request is not successfully executed within the preset time, the network request is executed again according to the request instance. The device of claim 12 wherein said processor further performs the following steps: If the network request is not successfully executed, determine whether the number of times the network request is executed according to the request instance reaches a preset number of times; If the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is placed in the deferred queue; Determine whether the waiting time is reached; If the hold wait time is reached, the request instance is fetched from the hold queue and a network request is performed according to the request instance. The device of claim 13 wherein said processor further performs the following steps: If the number of times the network request is executed according to the request instance reaches a preset number of times, destroying the request instance, and obtaining a reason why the network request is not successfully executed; Determining, according to the reason, whether a request instance that is identical to the request instance needs to be re-created; Controlling the application to display the state before the network request was successfully executed if no re-creation is required; If re-creation is required, a request instance is created; and the step of determining whether the number of network requests being executed reaches a preset number is returned. The device of claim 13, wherein the request instance includes a priority, and the processor further performs the following steps: If the number of network requests being executed by the management center exceeds a preset number, placing the request instance into a waiting queue according to the priority of the request instance; If the number of times the network request is executed according to the request instance does not reach the preset number of times, placing the request instance into the suspension queue includes: if the number of times the network request is executed according to the request instance does not reach a preset number, according to the request The priority of the instance puts the request instance into the corresponding deferred queue. A computer readable storage medium, wherein the computer readable storage medium stores one or more program data, the one or more program data being executable by one or more processors to implement the following step: If the application launches, create a management center that can execute the application network request; If it is detected that the application is to send a network request, determine whether the network request is a preset type of network request; If the network request is a preset type of network request, controlling the application to send the network request to the management center; The management center controls the application to display a status after the network request is successfully executed and execute the network request. The computer readable storage medium of claim 16 wherein said step further comprises: Creating a request instance of the network request to control an application to display a status after the network request is successfully executed; Determining whether the number of network requests being executed reaches a preset number; If the preset number is not reached, the network request is executed according to the request instance; Determine whether the network request is executed successfully; If the network request is successfully executed, deleting the request instance; If the network request is not successfully executed within the preset time, the network request is executed again according to the request instance. The computer readable storage medium of claim 17, wherein the step further comprises: If the network request is not successfully executed, determine whether the number of times the network request is executed according to the request instance reaches a preset number of times; If the number of times the network request is executed according to the request instance does not reach the preset number of times, the request instance is placed in the deferred queue; Determine whether the waiting time is reached; If the hold wait time is reached, the request instance is fetched from the hold queue and a network request is performed according to the request instance. The computer readable storage medium of claim 18, wherein the step further comprises: If the number of times the network request is executed according to the request instance reaches a preset number of times, destroying the request instance, and obtaining a reason why the network request is not successfully executed; Determining, according to the reason, whether a request instance that is identical to the request instance needs to be re-created; Controlling the application to display the state before the network request was successfully executed if no re-creation is required; If re-creation is required, a request instance is created; and the step of determining whether the number of network requests being executed reaches a preset number is returned. The computer readable storage medium of claim 18, wherein the request instance comprises a priority, the step further comprising: If the number of network requests being executed by the management center exceeds a preset number, placing the request instance into a waiting queue according to the priority of the request instance; If the number of times the network request is executed according to the request instance does not reach the preset number of times, placing the request instance into the suspension queue includes: if the number of times the network request is executed according to the request instance does not reach a preset number, according to the request The priority of the instance puts the request instance into the corresponding deferred queue.