<?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 Re: Resume upload: what is the current offset? in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Resume-upload-what-is-the-current-offset/m-p/666944#M30185</link>
    <description>&lt;P&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1322303"&gt;@josuegomes&lt;/a&gt; Yes, as Здравко said, either way would work. In general though the expectation is that the app would record the current offset locally.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Mar 2023 16:32:36 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2023-03-10T16:32:36Z</dc:date>
    <item>
      <title>Resume upload: what is the current offset?</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Resume-upload-what-is-the-current-offset/m-p/666878#M30182</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I understand I can use upload sessions to upload large files. That is: call Upload Session Start, then Upload Session Append and finally Upload Session Finish.&lt;/P&gt;
&lt;P&gt;My question: is it possible to query what is the current offset taking only the session id?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The scenario is: application calls Upload Session Start, saves (persists) the session id, calls several times Upload Session Append.&lt;/P&gt;
&lt;P&gt;Then the application exits (either by user request or by a failure).&lt;/P&gt;
&lt;P&gt;The application starts again, takes the saved session id and tries to continue the upload (with Upload Session Append).&lt;/P&gt;
&lt;P&gt;However it seems there is no way to query what is the current offset.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Possible solutions are: persist the current offset together with the serssion id.&lt;/P&gt;
&lt;P&gt;Or call Append with an invalid offset (eg 0), it returns the `&lt;SPAN&gt;UploadSessionOffsetError&lt;/SPAN&gt;` error with the correct offset.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it ok to rely on the&amp;nbsp;UploadSessionOffsetError?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 19:48:27 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Resume-upload-what-is-the-current-offset/m-p/666878#M30182</guid>
      <dc:creator>josuegomes</dc:creator>
      <dc:date>2023-03-10T19:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: Resume upload: what is the current offset?</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Resume-upload-what-is-the-current-offset/m-p/666896#M30183</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1322303"&gt;@josuegomes&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;Possible solutions are: persist the current offset together with the serssion id.&lt;/P&gt;&lt;P&gt;Or call Append with an invalid offset (eg 0), it returns the `&lt;SPAN&gt;UploadSessionOffsetError&lt;/SPAN&gt;` error with the correct offset.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it ok to rely on the&amp;nbsp;UploadSessionOffsetError?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Hi &lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1322303"&gt;@josuegomes&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Yes, that's are the possible ways. Is it Ok or Not - it's your design decision; it would work. I personally prefer the first option (to save current state - both id and offset or set of offsets/pattern when concurrent upload is in use).&lt;/P&gt;&lt;P&gt;Good luck.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 14:17:38 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Resume-upload-what-is-the-current-offset/m-p/666896#M30183</guid>
      <dc:creator>Здравко</dc:creator>
      <dc:date>2023-03-10T14:17:38Z</dc:date>
    </item>
    <item>
      <title>Re: Resume upload: what is the current offset?</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Resume-upload-what-is-the-current-offset/m-p/666944#M30185</link>
      <description>&lt;P&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1322303"&gt;@josuegomes&lt;/a&gt; Yes, as Здравко said, either way would work. In general though the expectation is that the app would record the current offset locally.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 16:32:36 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Resume-upload-what-is-the-current-offset/m-p/666944#M30185</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2023-03-10T16:32:36Z</dc:date>
    </item>
  </channel>
</rss>

