This seems like a great addition, much simpler for db records in our custom apps, BUT
not that useful until itemID can be passed (as an alternative to filepath) to getOptimalUrls, not to mention copy, delete, move, rename functions; also needs to be part of the querystring added to our new callbackURL on uploads.*
I hope we can expect that functionality in the near (!) future.
* I'm imagining a workflow like this:
- get upload token & create a temp record in our app's db ->
- user does browser upload using upload token ->
- nirvanix sends callbackURL + itemID & token-used in querystring ->
- store itemID in our app's db record for that token ->
- later, fetch download URLs by passing itemID in a getOptimalURLs call