No reason someone uploading a 1GB file in 10MB hunks should have to cost a company 1000 api calls (4% of their entire total combined API limit for every person). I really think the limit should be a total size limit or # of files updated limit to avoid this weird pressure on people making apps. Uploading in hunks is much nicer on phones that have bad connections that come in and out but this pressues us not to use it. Don't understand why this is an API call limit and not a size limit. Is it then good advice to upload all files smaller than 100MB with the one shot uploader, and use the piece by piece uploader for larger files? smaller hunk sizes are nicer for reliability, so it bad I have to give up relability for this API limit. That means uploading 12500 files in hunks that'll take up at least entire 25000 api call limit? Even more if the hunk size is smaller. Reading around the Dropbox website says that apps that connect to free or indivudal users have no API limit, but apps that connect to business have a 25k limit for file upload calls? Is this right? business users pay the most so would think it's the other way around?Īlso since it's an API limit and not a byte limit, that means when uploading files in hunks I want to use the biggest hunk size possible to reduce the API calls? Also since the piece meal upload has a complete step, it'll always take at least 2 calls to upload a file with that. We're adding dropbox upload/download to our app.I don't really use dropbox myself so help me figure all of this out.
0 kommentar(er)
