Back to results
US 11,470,178 B2Granted
System and method for robust local cache handling
AssigneeShinydocs Corporation
InventorsPeter Vanleeuwen, Robert Haskett, Jason Cassidy, Ben Barth, Khalid Merhi
Life of this patent
Estimating the term…
Abstract
A local cache content management is configured to improve the speed and reliability of access of the content management system across poor or intermittent connections. Additional techniques are used to allow document use and storage when the content management system is unavailable, and to maintain synchronization between the local cache and the content management system.
Claims20
A content management system, the content management system comprising:
- a server configured to store a plurality of files of the content management system;
- and
- a local device comprising a processor configured, by a set of executable instructions storable in a nontransient memory device, to:
- receive a request to save a file in the server;
- register the request and a request state in a pending actions queue;
- track progress of the save in the pending actions queue;
- display a pending actions indicator pop-up in a task bar;
- determine whether the file is successfully saved in the server;
- if the file is successfully saved in the server, update the file in the server;
- if the file is not successfully saved in the server:
- update the request state in the pending actions queue and retry saving the file in the server up to three times;
- determine whether the file is successfully saved in the server;
- if the file is successfully saved in the server, update the file in the server;
- if the file is not successfully saved in the server, initiate an alternate save procedure, the alternate save procedure comprising:
- prompting a user to select one of retrying saving the file in the server later and saving the file in the local device, the prompting comprising prompting selecting every 30 seconds until a selection is made;
- if saving the file in the local device is selected, prompting the user for a local location on the local device for saving the file, saving the file in the local location on the local device, and removing the request from the pending actions queue;
- and
- if retrying saving the file in the server later is selected, retrying saving the file in the server every hour or when a trigger event occurs, until a maximum number of retries has been attempted.
15 more elements
A method of providing a content management system, the method comprising:
- providing a server configured to store a plurality of files of the content management system;
- providing a local device comprising a processor configured, by a set of executable instructions storable in a nontransient memory device, to:
- receive a request to save a file in the server;
- register the request and a request state in a pending actions queue;
- track progress of the save in the pending actions queue;
- display a pending actions indicator pop-up in a task bar;
- determine whether the file is successfully saved in the server;
- if the file is successfully saved in the server, update the file in the server;
- if the file is not successfully saved in the server:
- update the request state in the pending actions queue and retry saving the file in the server up to three times;
- determine whether the file is successfully saved in the server;
- if the file is successfully saved in the server, update the file in the server;
- if the file is not successfully saved in the server, initiate an alternate save procedure, the alternate save procedure comprising:
- prompting a user to select one of retrying saving the file in the server later and saving the file in the local device, the prompting comprising prompting selecting every 30 seconds until a selection is made;
- if saving the file in the local device is selected, prompting the user for a local location on the local device for saving the file, saving the file in the local location on the local device, and removing the request from the pending actions queue;
- and
- if retrying saving the file in the server later is selected, retrying saving the file in the server every hour or when a trigger event occurs, until a maximum number of retries has been attempted.
14 more elements
Dependencies are inferred from the claim text.