API for finer grained control over data source and object naming for uploads

[argl]

What plans do you have for extending the basic API to allow uploading form memory and having a bit more control over the naming of the Azure blob objects? I have an actual use case where the data I want to store is actually a StringIO plus I have to use a naming scheme to simulate "folders" (slashes in object names) on the Azure side.

I can see that you already did the heavy lifting with request signing and concurrently uploading large files in seperate blocks, but its all jailed in a simple file upload function that strips out the file path components for the object name.

I would be glad to help, just show me the direction you want to go with this.