Synchronization of automation scripts among different computing systems
US-2024054025-A1 · Feb 15, 2024 · US
US9529818B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9529818-B2 |
| Application number | US-201213453909-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 23, 2012 |
| Priority date | Apr 23, 2012 |
| Publication date | Dec 27, 2016 |
| Grant date | Dec 27, 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.
Aspects of the present disclosure are directed to architectures, methods and systems and structures that facilitate the sharing and synchronization of electronically stored files among and between cloud entities and a number of computers, systems, devices and/or users. One particular exemplary architectural aspect includes the concurrent determination of file system changes within a cloud file system and a client file system, the serial ordering of necessary file system operations in response to the determined file system changes, and the concurrent execution of file system operations such that the cloud file system and the client computer file system are synchronized.
Opening claim text (preview).
The invention claimed is: 1. A computer implemented method of transferring files and providing access to files stored in a cloud comprising the steps of: detecting at a client computer system a relevant change made to a file residing in a cloud file system; determining by the client computer system whether the file originated via cloud computing services, wherein the file originated via cloud computing services when the file was not obtained or derived from content stored on the client computer system; determining whether the file has a file type that is associated with a cloud application; if the file originated via cloud computing services and was not obtained or derived from the client computer system, and if the file has a file type that is associated with a cloud application, then storing in the client computer's local file system a linking file comprising a link to the file residing in the cloud file system and not storing a copy of the file residing in the cloud system in the client computer's local file system; wherein the linking file appears as a file having a file type that is associated with said cloud application; and wherein the link within the linking file operates such that attempting to open said linking file causes the file residing in the cloud file system to be opened by said cloud application from the cloud file system; and otherwise, storing in a local file system of the client computer system a copy of the file residing in the cloud file system. 2. The computer implemented method of claim 1 wherein the link comprises a uniform resource locator (URL) and is usable by a browser to access the file residing in the cloud file system, and wherein the linking file does not include the contents of the file residing in the cloud file system. 3. The computer implemented method of claim 1 wherein the link comprises a resourceID of the file electronically stored in the cloud file system, wherein the resourceID uniquely identifies the file residing in the cloud file system. 4. The computer implemented method of claim 3 wherein said file residing in the cloud file system exhibits a type selected from the group consisting of: documents, spreadsheets, presentations, drawings, forms and cloud sites. 5. The computer implemented method of claim 4 wherein said cloud computing services include applications selected from the group consisting of: word processing, spreadsheet, graphics, and calendar. 6. The computer implemented method of claim 1 , wherein the file type is associated with a file extension .gdoc. 7. The computer implemented method of claim 1 , wherein if the file did not originate via cloud computing services, the file was obtained or derived from the client computer system and was uploaded to the cloud file system via a drag-and-drop operation performed on the client computer system. 8. The computer implemented method of claim 1 , wherein the file type that is associated with said cloud application is indicative that the file originated via cloud computing services and was not obtained or derived from the client computer system. 9. The computer implemented method of claim 1 , wherein when the file residing in the cloud file system is opened by said cloud application from the cloud file system, the file is not downloaded to the client computer system. 10. A system for transferring files and providing access to files electronically stored in a cloud storage system comprising a client computer system including a processor and a memory coupled to said processor said memory having stored thereon computer executable instructions that upon execution by the processor cause the system to: detect a relevant change made to a first file residing in a cloud file system; determine whether the first file originated via cloud computing services, wherein the file originated via cloud computing services when the file was not obtained or derived from content stored on the client computer system; determine whether the first file has a file type that is associated with a cloud application; if the first file originated via cloud computing services and was not obtained or derived from the client computer system, and if the first file has a file type that is associated with a cloud application, then store in the client computer's local file system a linking file comprising a link to the first file, wherein the linking file appears as a second file having a file type that is associated with said cloud application and the link within the linking file operates such that attempting to open said linking file causes the first file to be opened by said cloud application from the cloud file system; otherwise store a copy of the first file to the client computer system. 11. The system of claim 10 wherein the link comprises a uniform resource locator (URL) and is usable by a browser to access the first file residing in the cloud file system, and wherein the linking file does not include the contents of the first file residing in the cloud file system. 12. The system of claim 10 wherein the link comprises a resourceID of the first file, wherein the resourceID uniquely identifies the first file residing in the cloud file system. 13. The system of claim 12 wherein said first file exhibits a type selected from the group consisting of: documents, spreadsheets, presentations, drawings, forms and cloud sites. 14. The system of claim 13 wherein said cloud computing services include applications selected from the group consisting of: word processing, spreadsheet, graphics, calendar, and cloud site applications. 15. The system of claim 10 wherein said first file exhibits a type indicative of generation by a third-party application in conjunction with cloud computing services, and is indicative that the first file was not obtained or derived from content stored on the client file system. 16. The system of claim 10 , wherein the file type is associated with a file extension .gdoc. 17. The system of claim 10 , wherein if the first file did not originate via cloud computing services, the first file was obtained or derived from the client computer system and was uploaded to the cloud file system via a drag-and-drop operation performed on the client computer system. 18. The system of claim 10 , wherein when the first file residing in the cloud file system is opened by said cloud application from the cloud file system, the first file is not downloaded to the client computer system.
Distributed file systems · CPC title
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Techniques for file synchronisation in file systems · CPC title
Management specifically adapted to replicated file systems · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.