Re: OneDrive backend
- From: Vilém Hořínek <vilem horinek hotmail com>
- To: Ondrej Holy <oholy redhat com>, "awilliam whitemice org" <awilliam whitemice org>
- Cc: "gvfs-list gnome org" <gvfs-list gnome org>, Debarshi Ray <dray redhat com>
- Subject: Re: OneDrive backend
- Date: Tue, 22 May 2018 13:33:01 +0000
Ondrej Holy píše v Út 22. 05. 2018 v 14:09 +0200:
Hi,
in that
case, the new backend is a
definitely good way. I don't know much about OneDrive, but hope that the handling will be a little bit easier than in google case... Rishi, don't you have any comments apart from the one on that bug report?
See what problems are with path handling in google backend:
I looked into that and if I understand it correctly the whole problem is the possibility of having two files with the same name in one folder. On OneDrive, though this wouldn't be a problem, since OneDrive doesn't allow this, so the backend wouldn't need
to expose path composed from ID, but it could be the actual path in the storage.
Be aware of the following issue with google backend. Caching the whole drive metadata wasn't really the best idea:
Don't know what's the best solution, but I thought about downloading the metadata for each folder on demand and later probably modify the libzapojit to support the webhook interface if it's possible to track the changes in real time.
Also, other links on the following page may be useful for you:
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]