#6074 closed defect (fixed)
Sync comparison fails
Reported by: | Torcello | Owned by: | dkocher |
---|---|---|---|
Priority: | normal | Milestone: | 4.1.1 |
Component: | googledrive | Version: | 4.1 |
Severity: | normal | Keywords: | |
Cc: | Architecture: | ||
Platform: | Windows 7 |
Description
It seems to me there's a problem with timestamps when syncronizing with Google Docs. It seems like all files and folders are aasigned a new timestamp when uploaded. This means that the sync funktion is useless with google docs, as you either has to download everything or upload everything and not just only the files and folders that were changed. Is tha a bug in the system or is it supposed to be like that?
Change History (6)
comment:1 Changed on Jul 17, 2011 at 4:42:02 PM by dkocher
- Milestone set to 4.1.1
comment:2 Changed on Jul 17, 2011 at 4:53:56 PM by dkocher
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed on Jul 17, 2011 at 9:53:18 PM by dkocher
- Resolution fixed deleted
- Status changed from closed to reopened
- Summary changed from Timestamp problem sync Google Docs to Sync comparison fails
comment:4 Changed on Jul 17, 2011 at 9:53:41 PM by dkocher
Needs further changes.
comment:5 Changed on Jul 21, 2011 at 4:40:56 PM by dkocher
Fix for timestamps in r8932.
comment:6 Changed on Jul 21, 2011 at 4:41:52 PM by dkocher
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
The Google API provides a MD5 checksum for documents which we should use for comparisons. Currently we set compare the ETag which is not the MD5 sum although that is what we wrongly assume.