My thought would be to create a locked folder accessible only by APPX and then if the user decides they don't want to use the service any more and revokes permission to APPX the folder gets deleted.
What are the limit on number of records, number of field (column?) in a table? How many tables can one have?
How often is the commit? Is it commit to local/fs or to the cloud (under what condition)?
How does the datastore sync from different devices works?
As to the sync model, changes are always made locally and then queued for upload. You might want to read Guido's posts about conflict resolution to understand the model:
https://www.dropbox.com/developers/blog/48/how-the-datastore...
https://www.dropbox.com/developers/blog/56/how-the-dropbox-d...
Good info!
10MB database limit is too small - somehow I would image dropbox wants app to create hundreds of MB if not GB of data. :-)
Are there any test code available? Open Source / on github?
It is much easier to understand the flow from the test code than API doc. If test code is available, it is easily to morph that info benchmark type code.
Specifically, it does not spell out any of the imports, and uses very large except clauses.
In general, I based the tutorial on the sample app that ships with the SDK. That app uses Flask and presents some actual UI. If you want full working code, I would suggest taking a look at that sample.
The tutorial is basically fragments from that sample that show the basic concepts, but without some boilerplate, the fragments are not themselves runnable.
(BTW, where are the "very large except clauses?")
The except clause is in the "dropbox_auth_finish" view. That might be personal paranoia, but I'm sure that every single timeI think "It's OK to put a `except:` here", it eventually comes back to bite me (without exception ;) )!
I do understand the motivation to keep it minimal (and I think the Flask boilerplate is indeed well understood), but putting together the sample without the Dropbox SDK imports (specifically without an IDE) might end up being a bit more bothersome than optimal : )
Just personal opinion, of course!
Some apps won't enjoy being open simultaneously, but if you keep this in-mind, this is generally a great solution.
Therefore Dropbox, not a homegrown process, syncs your settings