API v2 - set metadata/mtime

Thanks Steve -

Revs are great, but don't really speak to the issue. It's not so much that we're trying to use mtime in order to figure out what needs to be sync'd, but so that we can provide a network filesystem representation of Dropbox. And like the desktop client, we'd like to have the client modified time stay the same on a particular file when they move it into Dropbox via ExpanDrive.

If a user wants to migrate a large tree of info into Dropbox via ExpanDrive, all of metadata gets tossed. Most of that isn't particularly important, but users do notice when the modification times of data change.

Also, the use-case where some automated process [backup app, let's say] wants to sync data into Dropbox via ExpanDrive - those tools [rsync, et al] rely on the mtime as an indication of whether or not something has changed.

Right now the best we can do is keep a local database that maps a particular rev to some metadata, and then potentially sync that out. But given that the Dropbox desktop client can set mtime, it'd be nice to expose that to us [at least as an optional parameter on upload, if not its own metadata update endpoint]. Google Drive and Box already provide fairly robust metadata handling in their APIs, it'd be nice if Dropbox would consider it.