OPTIMISTIC DATA FETCHING AND RENDERING

• US 20170193127A1
• Filed: 12/29/2016
• Published: 07/06/2017
• Est. Priority Date: 12/30/2015
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Yung, Timothy Robert, Roch, IV, Lewis Marshall, Chen, Jing, Zheng, Yuzhi, Kuenzel, Laney Elizabeth
• Granted Patent: US 10,277,362 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/176 Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/9536 Search customisation based on social or collaborative filtering
• CPC Class Codes: G06F 16/9538 Presentation of query results
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 1/08 by repeating transmission, e.g. Verdan system H04L1/1858 and H04L1/189 take precedence
• CPC Class Codes: H04L 1/16 in which the return channel carries supervisory signals, e.g. repetition request signals

Abstract

Embodiments are disclosed for fast data fetching and rendering. In some embodiments, in response to receiving a page display request, a system constructs a static, possibly nested query for retrieving all the data to be rendered for the page and stores the query result in a data store. For a future page display request, the system similarly constructs a query and determines whether the query can be resolved from the data store. If not, the system constructs a “diff query” to fetch only the missing data. In some embodiments, in response to a subsequent page update request, the system retrieves from the server all the data likely to be viewed or updated and renders the data changes corresponding to the requested update. The system then submits the data changes to the server and undoes the rendering of the data changes when the server fails to process the data changes.

Claims

1. A method performed by a client system of managing data for graphical rendering, comprising:

receiving, by a client system, a request for an update to graphical content;

determining one or more data changes resulting from the request;

sending updated graphical content based on the data changes;

after the sending, submitting to a server over a network for storage on the server, the one or more data changes;

receiving a response from the server indicating whether the one or more data changes are successfully stored on the server;

when the response indicates a success, saving the one or more data changes in a local database; and

when the response indicates a failure, resending the graphical content instead of the updated graphical content.

2. The method of claim 1:

wherein the graphical content constitutes a webpage that accepts input; and

wherein the update includes specific data inputted into the webpage.

3. The method of claim 1, further comprising:

before the submitting, identifying a group query for all data that are likely to be requested due to the update;

submitting the group query to the server;

receiving a query result corresponding to the group query from the server; and

saving the query result in the local database.

4. The method of claim 3, further comprising trimming a portion of the group query when a query result corresponding to the portion is available in the local database.

5. The method of claim 3, further comprising:

after the sending, receiving a second request for viewing data that is related to the update and is not visible;

retrieving the certain data from the local database; and

sending additional graphical content based on the certain data.

6. The method of claim 1, wherein the one or more data changes include the update and any data change caused by the update.

7. The method of claim 1, further comprising:

before the sending, adding one or more entries into an action queue different from the local database respectively for the one or more data changes;

wherein each of the one or more entries includes a transaction ID specific to the one or more data changes as a group, information identifying an item affected by the corresponding data change, a current value of the item, and an updated value of the item based on the corresponding data change; and

removing the one or more entries from the action queue before the submitting.

8. The method of claim 7, wherein when the response indicates the failure, removing entries from the action queue that have been added into the action queue after the one or more entries and that include information identifying any of the items included in the one or more entries.

9. The method of claim 7, wherein when the response indicates the failure, adding the one or more entries back into the action queue.

10. The method of claim 1, wherein when the response indicates the failure, re-submitting the one or more data changes to the server up to a specific number of times.

11. The method of claim 1, wherein the resending includes resending an error message together with the graphical content.

12. A system for managing data for graphical rendering, comprising:

a graphical user interface, including an input device and an output device; and

a processor and memory, cooperating to function as;

a first receiving unit configured to receive an input via the input device, wherein the input is related to graphical content that is visible;

a determining unit configured to determine one or more data updates resulting from the input;

a sending unit configured to send updated graphical content based on the data updates via the output device;

a submitting unit configured to submit, after the sending, the one or more data updates to a server over a network for storage on the server;

a second receiving unit configured to receive a reply from the server indicating whether the one or more data updates are successfully stored on the server;

a saving unit configured to save, when the reply indicates a success, the one or more data updates in a local data store; and

a resending unit configured to resend, when the reply indicates a failure, the graphical content instead of the updated graphical content via the output device.

13. The system of claim 12, the processor and memory cooperating to further function as:

an identifying unit configured to identify, before the submitting, a group query for all data that are likely to be requested due to the input;

a transmitting unit configured to transmit the group query to the server;

a third receiving unit configured to receive a query result corresponding to the group query from the server; and

a storing unit configured to store the query result in the local data store.

14. The system of claim 13, the processor and memory cooperating to further function as:

a third receiving unit configured to receive, after the sending, a request for viewing certain data that is related to the input and is not visible;

a retrieving unit configured to retrieve the certain data from the local data store; and

a second sending unit configured to send additional graphical content based on the certain data.

15. The system of claim 12, wherein the one or more data updates include the input and any data update caused by the input.

16. The system of claim 12, the processor and memory cooperating to further function as:

an adding unit configured to add, before the sending, one or more entries into an action queue different from the local data store respectively for the one or more data updates;

wherein each of the one or more entries includes a transaction ID specific to the one or more data updates as a group, information identifying an item affected by the corresponding data update, a current value of the item, and an updated value of the item based on the corresponding data update; and

a removing unit configured to remove the one or more entries from the action queue before the submitting.

17. The system of claim 16, wherein the removing unit removes, when the reply indicates the failure, entries from the action queue that have been added into the action queue after the one or more entries and that include information identifying any of the items included in the one or more entries.

18. The system of claim 12, wherein the processor and memory cooperating to further function as a resubmitting unit configured to resubmit, when the reply indicates the failure, the one or more data updates to the server up to a specific number of times.

19. The system of claim 12, wherein the system is a smart mobile device.

20. A computer-readable storage medium storing computer-executable instructions that, when executed, cause a computer to perform a method of managing data for graphical rendering, comprising:

instructions for receiving a request for an update to graphical content;

instructions for determining one or more data changes resulting from the request;

instructions for sending updated graphical content based on the data changes;

instructions for, after the sending, submitting the one or more data changes to a server over a network for storage on the server;

instructions for receiving a response from the server indicating whether the one or more data changes are successfully stored on the server;

instructions for, when the response indicates a success, saving the one or more data changes in a local database; and

instructions for, when the response indicates a failure, resending the graphical content instead of the updated graphical content.