<?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 Concurrency issue - failed to grab locks in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Concurrency-issue-failed-to-grab-locks/m-p/132270#M3902</link>
    <description>&lt;P&gt;We did see the previous answer&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropboxforum.com/hc/en-us/community/posts/204555365-Failed-to-grab-locks" rel="nofollow noreferrer" target="_blank"&gt;https://www.dropboxforum.com/hc/en-us/community/posts/204555365-Failed-to-grab-locks&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;about the concurrency limitation. But wanted to find out more information,&lt;/P&gt;
&lt;P&gt;- Is this limitation because of using the API&lt;/P&gt;
&lt;P&gt;- Is the limitation because the same OAuth token is used by concurrent requests?&lt;/P&gt;
&lt;P&gt;- Is the limitation because of concurrent access to the same user's folders (Would concurrent access to different users have the same problem?)&lt;/P&gt;
&lt;P&gt;Any more information on this limitation will be useful, we are trying to see what is the maximum concurrency we can get when working across multiple users and teams.&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:36:09 GMT</pubDate>
    <dc:creator>Info V.1</dc:creator>
    <dc:date>2019-05-29T09:36:09Z</dc:date>
    <item>
      <title>Concurrency issue - failed to grab locks</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Concurrency-issue-failed-to-grab-locks/m-p/132270#M3902</link>
      <description>&lt;P&gt;We did see the previous answer&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropboxforum.com/hc/en-us/community/posts/204555365-Failed-to-grab-locks" rel="nofollow noreferrer" target="_blank"&gt;https://www.dropboxforum.com/hc/en-us/community/posts/204555365-Failed-to-grab-locks&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;about the concurrency limitation. But wanted to find out more information,&lt;/P&gt;
&lt;P&gt;- Is this limitation because of using the API&lt;/P&gt;
&lt;P&gt;- Is the limitation because the same OAuth token is used by concurrent requests?&lt;/P&gt;
&lt;P&gt;- Is the limitation because of concurrent access to the same user's folders (Would concurrent access to different users have the same problem?)&lt;/P&gt;
&lt;P&gt;Any more information on this limitation will be useful, we are trying to see what is the maximum concurrency we can get when working across multiple users and teams.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:36:09 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Concurrency-issue-failed-to-grab-locks/m-p/132270#M3902</guid>
      <dc:creator>Info V.1</dc:creator>
      <dc:date>2019-05-29T09:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Concurrency issue - failed to grab locks</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Concurrency-issue-failed-to-grab-locks/m-p/132271#M3903</link>
      <description>&lt;P&gt;This issue is not specific to using the API, nor is it related to using the same access token specifically. Changes made via the web or desktop, for example, can cause this to be seen via the API, and vice versa.&lt;/P&gt;
&lt;P&gt;It is related to making concurrent changes to a single user account, and so making changes in different accounts won't affect each other, unless the changes happen to be in a shared folder between the accounts.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2016 09:12:12 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Concurrency-issue-failed-to-grab-locks/m-p/132271#M3903</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2016-02-04T09:12:12Z</dc:date>
    </item>
  </channel>
</rss>

