TERMINAL, METHOD AND NON-TRANSITORY COMPUTER-READABLE MEDIUM INCLUDING PROGRAM INSTRUCTIONS
A terminal for handling data in a live streaming platform, including one or a plurality of processors, wherein the one or plurality of processors execute a machine- readable instruction to perform: transmitting a request on a portion of data; receiving a response of the request; setting a retry count in response to the response being failed and the portion of data being not the first portion; determining retry time according to the set retry count; and transmitting a next request on the portion of data after the retry time. According to the present disclosure, the requested data, such as the leaderboard data, may be displayed smoothly to the user terminal regardless of the network condition, rather than showing a blank screen. Therefore, the user experience may be improved.
1 . A terminal for handling data in a live streaming platform, comprising one or a plurality of processors, wherein the one or plurality of processors execute a machine-readable instruction to perform:
transmitting a request on a portion of data;
receiving a response of the request;
setting a retry count in response to the response being failed and the portion of data being not the first portion;
determining retry time according to the set retry count; and
transmitting a next request on the portion of data after the retry time.
2 . The terminal according to claim 1 , wherein
the retry time is either a fixed value or increases with the increase in retry count.
3 . The terminal according to claim 1 , further comprising:
retrieving cache data of the portion of data and the rest portions of data in response to the request being failed and the portion of data being the first portion; and
displaying the cache data on the terminal.
4 . The terminal according to claim 1 , further comprising:
storing last response time from a server in response to the response being success; and
determining a refresh time according to the last response time; and
refreshing the portion of data after the refresh time.
5 . The terminal according to claim 1 , wherein
the refresh time is either a fixed value or increases with the increase in last response time.
6 . The terminal according to claim 1 , further comprising:
determining whether to refresh the portion of data in response to the response being success;
displaying the portion of data in response to not refreshing the portion of data; and
transmitting a request on a next portion of data in response to there being a cursor in the response.
7 . The terminal according to claim 1 , further comprising:
determining whether to refresh the portion of data in response to the response being success;
determining whether all portions of data being acquired in response to refreshing the portion of data;
displaying the portion of data in response to not all portions of data being acquired; and
transmitting a request on a next portion of data in response to there being a cursor in the response.
8 . The terminal according to claim 1 , further comprising:
determining whether to refresh the portion of data in response to the response being success;
determining whether all portions of data being acquired in response to refreshing the portion of data;
displaying all portions of data in response to all portions of data being acquired and there being no cursor in the response.
9 . A method for handling data in a live streaming platform, comprising:
transmitting a request on a portion of data;
receiving a response of the request;
setting a retry count in response to the response being failed and the portion of data being not the first portion;
determining retry time according to the set retry count; and
transmitting a next request on the portion of data after the retry time.
10 . A non-transitory computer-readable medium including program instructions, that when executed by one or more processors, cause the one or more processors to execute:
transmitting a request on a portion of data;
receiving a response of the request;
setting a retry count in response to the response being failed and the portion of data being not the first portion;
determining retry time according to the set retry count; and
transmitting a next request on the portion of data after the retry time.