OMGeeky/gdriver2
1
0
Fork 0
mirror of https://github.com/OMGeeky/gdriver2.git synced 2025-12-26 16:07:58 +01:00
Code Issues Packages Projects Releases Wiki Activity

update concept

Browse Source
This commit is contained in:
OMGeeky
2024-02-18 11:30:24 +01:00
parent 6a615d8d35
commit f65f0845c1
1 changed files with 15 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
concept.md
View File

@@ -4,7 +4,7 @@
## Service
The service is the one communicating with the google drive API. It will check for updates when it is asked and it will download files when requested.
The service is the one communicating with the google drive API. It will check for updates when it is asked, and it will download files when requested.
It also uploads changes to local files.
It also keeps track of what files should be kept locally and what files only get cached locally when accessed (important for offline access).
@@ -15,12 +15,22 @@ It needs to be able to do the following:
- Upload changes
- Get children of a folder
---
When the service is asked for metadata or content of a file it gets it from the API if it does not have a local copy
already and the local copy is not too old (configurable). It then creates a file in its cache or download folder with
the filename being the file id with no extension. The metadata will be on a file with the extension '.meta' in
the meta folder, this file will always be created (or updated), no matter if only the content or only the metadata was
requested.
When the service is asked for metadata or content of a file it gets it from the API if it does not have a local copy already and the local copy is not too old (configurable).
It then creates a file in its own folder with the filename being the file id with no extension. If only the metadata is requested it will create a file with the extension .meta.
The meta file will be a simple UTF-8 file, containing a number from 0 to 2:
When the user wants to read the file content, it should (first ask the service to check for changes? and then) see if the file in the service folder exists with the id. If it doesn't it should
request the content from the service and wait for its completion.
- 0: only metadata was fetched, no content available
- 1: content was fetched to cache
- 2: content was fetched to downloads
---
When the user wants to read the file content, it should request the file content from the service, which should trigger
an update check on the service side, and then read the meta file to determine if it is in cache or downloads. If it is
neither something really went wrong and the program might not be online or the requested file might not exist anymore.