Hi Gregory, team
Just few notes on /delete in Dropbox API v2.
https://www.dropbox.com/developers/documentation/http/documentation#files-delete
Issue:
The return codes for DELETE are not very clear. One can get a path_write (WriteError) with "conflict" (documented as "Couldn't write to the target path because there was something in the way").
This would made sense IF we can pass REV in delete request but not otherwise. But we cannot pass REV, which leads to main point:
Improvement:
Would be great to be able to pass REV on DELETE. This would make file operations secure. Example scenario where we need REV:
User has two devices and our app. Goes offline with both devices. Works on same document on both devices but deletes document in one device (while offline). Goes online first with device that has the document. App loads the file to dropbox. Goes online with other device (with deleted document). App loads user deletion request and deletes the work (!).
With REV we could detect these conflicts.
Yes, I know that I can get metadata just before deletion. But it is not secure. Just helps to minimize the probability of accidental deletion.
PS: No need to response. Just for you to know.
Regards,
Antti
