As mentioned above, the DropBox Sync API is now available, which I think will do what you talked about (I have not tried it personally, since I integrated Dropbox support in my application using the earlier SDK before this happened), This will probably be enough if you just work with dropbox.
In my case, I started adding support for additional online storage applications (βcloudsβ) for my application, and I find it somewhat more difficult to figure out the differences between them in how they handle different concepts such as authentication, versions, naming and etc. For example, the Dropbox API refers to files by their path, while the Box API refers to files according to their file identifier (which has an associated path, but I believe that this remains unchanged if the file is moved). Then also all the conflict resolution problems (aka merging) that arise when several clients try to synchronize conflicting changes with the server.
Recently, I was considering launching an open source project to develop a library that can connect to all major services, and provide an abstraction layer that describes their differences and also handles the synchronization process for you. I already have the code (which I have not published publicly so far), but could use it to run the project.
Would this be helpful to you? Will you (or any others) participate in such efforts?
(pay attention to the mods: I understand that this may deviate slightly from the topic - sorry. If you can recommend a more suitable forum to discuss this, I would be glad to accept the conversation there).
Peter Kelly
source share