Bug 674769 - New backend: Google Drive
New backend: Google Drive
Status: RESOLVED DUPLICATE of bug 739008
Product: gvfs
Classification: Core
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: gvfs-maint
gvfs-maint
:
: 719894 (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2012-04-25 06:12 UTC by Baptiste Mille-Mathias
Modified: 2014-10-22 14:07 UTC (History)
13 users (show)

See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Baptiste Mille-Mathias 2012-04-25 06:12:00 UTC 
Hi,

now that google has launched its remote filesystem, would it be possible to implement a google drive backend?

API Reference: https://developers.google.com/drive/v1/reference/
Comment 1 Felix Möller 2012-08-01 23:03:19 UTC 
I asked the upstream developers at https://github.com/Grive/grive/issues/111

I am not sure how bug #594423 is related to this.
Comment 2 Peter Robinson 2012-09-06 12:52:37 UTC 
Sample implementation here http://www.lbreda.com/grive/
Comment 3 Ross Lagerwall 2013-12-05 22:17:11 UTC 
*** Bug 719894 has been marked as a duplicate of this bug. ***
Comment 4 Debarshi Ray 2013-12-11 15:50:09 UTC 
There is this unfinished attempt at writing a Google backend for GVfs:
https://github.com/thiblahute/gvfs/tree/googledocuments
Comment 5 Ross Lagerwall 2013-12-11 17:09:18 UTC 
Yep, there's a tracker bug for that at bug 594423, as noted in comment 1.

I'm not sure how much overlap there is between GDrive and a Google Docs backend, though.
Comment 6 Debarshi Ray 2013-12-11 22:47:05 UTC 
The way I understand it, Google Drive is just the next generation Google Documents. eg., libgdata only implements the Google Documents API but you can use it to access drive.google.com. Similarly, docs.google.com redirects to drive.google.com these days.
Comment 7 Ross Lagerwall 2013-12-20 05:51:54 UTC 
It seems to be slightly more than that. There are two different APIs, both of which can be used to access drive.google.com. The old API, the docs one, has been deprecated [1]. So if we were to do a backend, we should use the GDrive API since it is not deprecated.

Do you know if there are any plans to support the GDrive API in libgdata? I had a look a Grive but it doesn't seem to have a public C API.


[1] https://developers.google.com/google-apps/documents-list/
Comment 8 Debarshi Ray 2013-12-20 11:25:53 UTC 
(In reply to comment #7)
> It seems to be slightly more than that. There are two different APIs, both of
> which can be used to access drive.google.com. The old API, the docs one, has
> been deprecated [1].

Yes, that is what I meant by "next generation".

> So if we were to do a backend, we should use the GDrive
> API since it is not deprecated.

I think we should just use whatever libgdata implements. Currently it only implements the older API, but when in future it moves to the newer API we would profit from that.

libgdata is widely used in GNOME (gnome-documents, evolution), has a test suite based on uhttpmock, which is why I recommend it.

> Do you know if there are any plans to support the GDrive API in libgdata? I had
> a look a Grive but it doesn't seem to have a public C API.

There are plans, but someone needs to turn it into reality. :-)
Comment 9 Debarshi Ray 2014-10-22 14:07:22 UTC 

*** This bug has been marked as a duplicate of bug 739008 ***
Note You need to log in before you can comment on or make changes to this bug.