Method and system for synchronizing data between a database system and its client applications
US-2015379037-A1 · Dec 31, 2015 · US
US9501490B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9501490-B2 |
| Application number | US-201113163742-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 20, 2011 |
| Priority date | Jun 20, 2011 |
| Publication date | Nov 22, 2016 |
| Grant date | Nov 22, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A most recently used (MRU) client synchronization engine is provided to synchronize a user's most recently used (MRU) document list associated with a client machine with a file hosting server's MRU document list. The file hosting server's MRU document list contains a list of the user's most recently used documents that are stored on the file hosting server. The user's documents that are stored on the file hosting server are accessible to the user on one or more web-enabled client machines. The MRU client synchronization engine analyzes registry data pertaining to the documents that a user uses on the client machine with the file hosting server's MRU document list to determine the user's most recently used documents.
Opening claim text (preview).
What is claimed: 1. A system comprising: at least one processor; at least one memory connected to the at least one processor; and at least one module that when loaded into the memory causes the at least one processor to: obtain a registry list including configuration data pertaining to a plurality of user documents accessed by a user from a client machine; send a request for a configuration list stored on a remote file hosting server, the configuration list including configuration data pertaining to the user's most recently used (MRU) server documents; in response to sending the request for the configuration list, receive, at the client machine, the configuration list; combine the registry list with the configuration list into a merged list; sort the merged list by an address field of the registry list and an address of the configuration list, wherein the address of the configuration list is a unique identifier on the file hosting server, to create a document entry pair including a document entry from the registry list and a corresponding document entry from the configuration list; for each document entry pair in the sorted merged list, compare a pin state and a pin timestamp of the document entry from the registry list with a pin state and a pin timestamp of the document entry from the configuration list to determine if the pin state of the document entry from the registry list has been modified by the user from the client machine; when it is determined that the pin state of the document entry from the registry list has been modified by the user from the client machine, send a pin state modification notification to the remote file hosting server; and form a MRU-client document list from the sorted merged list, the MRU-client document list comprising a folder of links to the user's most recently used documents. 2. The system of claim 1 , further comprises: a module that when loaded into the memory causes the at least one processor to: prior to updating the MRU-client document list, sort non-pinned entries in the sorted merged list on a last modified timestamp. 3. The system of claim 2 , wherein the module causes the at least one processor to: reduce the sorted merged list to a threshold number of entries. 4. The system of claim 1 , further comprising: a module that when loaded into the memory causes the at least one processor to: notify the remote file hosting server of updates made from the client machine to a user document listed in the configuration list. 5. The system of claim 1 , wherein the at least one module causes the at least one processor to combine the registry list with the configuration into a merged list, further causes the at least one processor to: match an entry in the registry list with a corresponding entry in the configuration list; identify that the entry was deleted from the configuration list and reopened on the client machine; and notify the file hosting server of the user document associated with the entry. 6. The system of claim 1 , wherein the at least one module causes the at least one processor to combine the registry list with the configuration into a merged list, further causes the at least one processor to: match an entry in the registry list with a corresponding entry in the configuration list; determine that the entry was repinned on the client machine; and notify the file hosting server of the user document associated with the entry. 7. The system of claim 1 , wherein the at least one module causes the at least one processor to combine the registry list with the configuration into a merged list, further causes the at least one processor to: match an entry in the registry list with a corresponding entry in the configuration list; determine that the entry was modified on the client machine; and notify the file hosting server of the user document associated with the entry. 8. The system of claim 1 , further comprises: a module that when loaded into the memory causes the at least one processor to: update the MRU-client document list at predetermined time intervals. 9. The system of claim 1 , further comprises: a module that when loaded into the memory causes the at least one processor to: update the MRU-client document list upon receipt of the configuration list from the remote file hosting server. 10. The system of claim 1 , wherein the at least one module causes the at least one processor to combine the registry list with the configuration into a merged list, further causes the at least one processor to: match an entry in the registry list with a corresponding entry in the configuration list; determine that the entry is in the registry list has a more recent timestamp; and notify the file hosting server of the entry having a more recent timestamp. 11. The system of claim 1 , wherein the at least one module causes the at least one processor to combine the registry list with the configuration into a merged list, further causes the at least one processor to: match an entry in the registry list with a corresponding entry in the configuration list; determine that the entry in the registry list has a pin state that differs from the corresponding entry in the configuration list and a more recent pin timestamp than the corresponding entry in the configuration list; and notify the file hosting server of the more recent timestamp and pin state of the entry. 12. A method, comprising: obtaining a registry list including configuration data pertaining to a plurality of user documents accessed by a user from a client machine; sending a request for a configuration list stored on a remote file hosting server, the configuration list including configuration data pertaining to the user's most recently used (MRU) server documents; in response to sending the request for the configuration list, receive, at the client machine, the configuration list; combining the registry list with the configuration list into a merged list; sorting the merged list by an address field of the registry list and an address of the configuration list, wherein the address of the configuration list is a unique identifier on the file hosting server, to create a document entry pair including a document entry from the registry list and a corresponding document entry from the configuration list; for each document entry pair in the sorted merged list, comparing a pin state and a pin timestamp of the document entry from the registry list with a pin state and a pin timestamp of the document entry from the configuration list to determine if the pin state of the document entry from the registry list has been modified by the user from the client machine; when it is determined that the pin state of the document entry from the registry list has been modified by the user from the client machine, sending a pin state modification notification to the remote file hosting server; and forming a most recently used (MRU)-client document list from the sorted merged list, the MRU-client document list including a folder of links to the user's most recently used documents, wherein the folder is part of a file system structure. 13. The method of claim 12 , wherein a first group of entries include a pin state and a second group of entries do not include a pin state. 14. The method of claim 12 , wherein combining the registry list with the configuration into a merged list further comprises: matching a user document in the registry list to a corresponding entry in the configuration list; and notifying the remote file hosting server of updates made to a user document in the registry list that differs from
Physics · mapped topic
Physics · mapped topic
Provision of network file services by network file servers, e.g. by using NFS, CIFS (network file access protocols H04L67/1097) · CPC title
Techniques for file synchronisation in file systems · CPC title
Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs {(coordinating program control therefor G06F9/52; in regulating and control system G05B)} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.