Shared publicly  - 
#driveforlinux #grive I finally figured out how to modify the content of the existing file using the resumeable-edit-media link. The trick is to include a atom/xml content in the first PUT request. This way, the meta data of the file will be updated.

So it's getting close to the next release, in which 2-way sync will be supported. It has some limitation, though. If a file exists in local but not in remote server (or vice versa), much more work needs to be done to determine whether:

- the file is newly created in local, but not in server
- the file was in both local & server, but got deleted in server

If it's the first case, we should upload the file.
If it's the second case, we should delete the file.

I guess version 0.0.3 will just treat everything as case 1. It's safer because we don't destroy user data. Let's think of some way to solve it in 0.0.4.

See the commit in the attached link for details.
Sam Stuewe's profile photoMatchman Green's profile photoGrive's profile photoJohn Donovan's profile photo
I am closely monitoring this page. I doubt I can contribute much, but if I have any ideas, I will shoot them your way. Frankly, if a FLOSS client for Drive can get the syncing functionality down, I wouldn't even care about an official one. #DriveForLinux #Grive
You can help by testing the app and send bug reports. Also spreading the news out to other people is very important to the project.
Add a comment...