Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to assign version folder #167

Closed
ghost opened this issue Sep 8, 2013 · 2 comments
Closed

How to assign version folder #167

ghost opened this issue Sep 8, 2013 · 2 comments
Assignees
Labels
Milestone

Comments

@ghost
Copy link

ghost commented Sep 8, 2013

I just updated my projects to reference the latest library after several weeks and I found some subtle changes were need to adjust to the changed API, but nothing too troublesome.

However, one bit of my code has broken. I used to call AddContainerHeaders with key "x-versions-location" and the name of a container, or blank to remove it. This API doesn't exist any more, so what is the equivalent way of defining and removing a versions container in the latest library?

Greg

@ghost ghost assigned sharwell Sep 8, 2013
@sharwell
Copy link
Contributor

sharwell commented Sep 8, 2013

Thanks for the report. I removed the method because in all the sample code I found it was only used to add/update metadata, and we already have methods for doing that. I'll add a method back to handle versioned containers prior to the 1.2.0.0 release.

For reference:
Object Versioning

@ghost
Copy link
Author

ghost commented Sep 8, 2013

While you're at it, there are a few similar cases to x-versions-location where special headers create special behaviour (x-delete-at, Log-Delivery, etc). Consider if it would be generous to wrap these "special case" headers in specific API methods to hide the implementation details from clients. Directly manipulating headers and metadata is a bit of a bother, so it would be nice to avoid them -- Greg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant