<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Dropbox API v2 /delete issue + improvement request in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-delete-issue-improvement-request/m-p/164694#M5870</link>
    <description>&lt;P&gt;Hi Gregory, team&lt;/P&gt;
&lt;P&gt;Just few notes on /delete&amp;nbsp;in Dropbox API v2.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#files-delete" target="_blank" rel="nofollow noreferrer"&gt;https://www.dropbox.com/developers/documentation/http/documentation#files-delete&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Issue:&lt;/P&gt;
&lt;P&gt;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").&lt;/P&gt;
&lt;P&gt;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:&lt;/P&gt;
&lt;P&gt;Improvement:&lt;/P&gt;
&lt;P&gt;Would be great to be able to pass REV on DELETE. This would make file operations secure. Example scenario where we need REV:&lt;/P&gt;
&lt;P&gt;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).&amp;nbsp;Goes online first with device that has the document. App loads the file to dropbox. Goes online with other device (with deleted document). &amp;nbsp;App loads user deletion request and deletes the work (!).&lt;/P&gt;
&lt;P&gt;With REV we could detect&amp;nbsp;these conflicts.&lt;/P&gt;
&lt;P&gt;Yes, I know that I can&amp;nbsp;get metadata just before deletion. But it is not secure. Just helps to minimize the probability of accidental deletion.&lt;/P&gt;
&lt;P&gt;PS: No need to response. Just for you to know.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Antti&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:36:43 GMT</pubDate>
    <dc:creator>Antti R.</dc:creator>
    <dc:date>2019-05-29T09:36:43Z</dc:date>
    <item>
      <title>Dropbox API v2 /delete issue + improvement request</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-delete-issue-improvement-request/m-p/164694#M5870</link>
      <description>&lt;P&gt;Hi Gregory, team&lt;/P&gt;
&lt;P&gt;Just few notes on /delete&amp;nbsp;in Dropbox API v2.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#files-delete" target="_blank" rel="nofollow noreferrer"&gt;https://www.dropbox.com/developers/documentation/http/documentation#files-delete&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Issue:&lt;/P&gt;
&lt;P&gt;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").&lt;/P&gt;
&lt;P&gt;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:&lt;/P&gt;
&lt;P&gt;Improvement:&lt;/P&gt;
&lt;P&gt;Would be great to be able to pass REV on DELETE. This would make file operations secure. Example scenario where we need REV:&lt;/P&gt;
&lt;P&gt;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).&amp;nbsp;Goes online first with device that has the document. App loads the file to dropbox. Goes online with other device (with deleted document). &amp;nbsp;App loads user deletion request and deletes the work (!).&lt;/P&gt;
&lt;P&gt;With REV we could detect&amp;nbsp;these conflicts.&lt;/P&gt;
&lt;P&gt;Yes, I know that I can&amp;nbsp;get metadata just before deletion. But it is not secure. Just helps to minimize the probability of accidental deletion.&lt;/P&gt;
&lt;P&gt;PS: No need to response. Just for you to know.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Antti&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:36:43 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-delete-issue-improvement-request/m-p/164694#M5870</guid>
      <dc:creator>Antti R.</dc:creator>
      <dc:date>2019-05-29T09:36:43Z</dc:date>
    </item>
    <item>
      <title>Re: Dropbox API v2 /delete issue + improvement request</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-delete-issue-improvement-request/m-p/164695#M5871</link>
      <description>&lt;P&gt;Hi Antti, thanks for the detailed feedback! It's very much appreciated. I'm sending it along to the team now.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jan 2016 11:10:07 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-API-v2-delete-issue-improvement-request/m-p/164695#M5871</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2016-01-19T11:10:07Z</dc:date>
    </item>
  </channel>
</rss>

