Thanks a lot, this is very informative!
In general, the filenames shouldn't be that important though, and should
usually not be shown to a user. They are more of a technical
implementation detail that the app itself takes care of, so the users
don't need to deal with it themselves in the UI. But that always depends
on the app of course.
I'm writing an application where the user handles sqlite databases. I thought the most straightforward way would be to use one remotestorage file for each db and use the file's filename as the name in the UI. This would also increase the likelihood that other applications can work with those files out of the box.
Instead, I could use internal filenames and save a some metadata separately. This could be either as a central json file (less files, less api calls) or as a file per database (less conflicts?). Compared to my previous approach:
- easy atomic rename
- support for more meta data (last modified, number of tables) without loading the complete dbs
- worse interoperability with other programs
Does this reasoning sound correct, or am I missing something? Anything else to add?