Page updating method and device based on current limiter and computer storage medium

Abstract

The embodiment of the invention provides a page updating method and device based on a current limiter and a computer storage medium, and the method comprises: enabling the current limiter to collect aplurality of tasks; Mounting the plurality of tasks on a current limiter; In the delay period, enabling the current limiter to collect latest data of each task in the plurality of tasks; And at the execution node, executing the plurality of tasks based on the latest data of each task, and displaying a task result. According to the technical scheme, a plurality of tasks are executed based on the delay period and the execution node set by the same current limiter, so that the final interface display result is synchronous, the jamming problem caused by too fast data updating can be avoided, andthe purposes of interface current limiting and interface synchronization are achieved.

Description

Technical field [0001] The present disclosure relates to the field of Internet technology, and in particular to a method and device for updating a page based on a current limiter. Background technique [0002] For applications that need to refresh the interface in real time, such as the real-time refresh of the interface of the stock App, the following problems will generally occur: one is that the back-end data is spit out very quickly, and the interface will be stuck; the other is that the data of different modules is in The problem that the interface refresh is out of sync when different times arrive. [0003] At present, methods such as delay are generally used to address the above problems, but the delay usually causes the loss of first and last data. For example: the 4 tasks of a, b, c, and d are executed in 1, 2, 3, and 4 seconds respectively. If the delay is 2 seconds, only task a and task c will be executed at this time, which will cause task d to be Ignoring it will res...

AI Technical Summary

Problems solved by technology

[0002] For applications that need to refresh the interface in real time, for example: the real-time refresh interface of the stock app, the following problems generally occur: one is that the back-end data is spit out very quickly, and the interface will be stuck; the other is that the data of different modules is in the When different times come, the interface refreshes out of sync

[0003] At present, delays are generally used to solve the above problems, but delays usually cause the loss of first and last data

For example: the four tasks a, b, c, and d are executed in 1, 2, 3, and 4 seconds respectively. If the delay is 2 seconds, only task a and task c will be executed at this time, which will cause task d to be executed. Ignoring it will cause the interface to finally display not the latest data

Because a is executed from 1 second, and it takes 3 seconds to execute task c, it will call task c to execute. After task c is executed, it will be 5s, and no task will be executed. The execution result of task c is displayed instead of the execution result of task d. As a result, the latest data displayed on the interface is not

[0004] For the above problems, no effective solution has been proposed

Images