All blob lease proxy APIs need to support access conditions #87

jcookems opened this Issue May 24, 2012 · 2 comments

2 participants


All the lease REST APIs support the access conditions (etag and time based), but only the acquireLease proxy API allows the user to specify access conditions.

The fix would be to rename AcquireLeaseOptions to be something more generic, like LeaseOptions, and use that LeaseOptions for all the lease proxy APIs.


This issue can be broken down into several parts.
a. shall we support access conditions now? What is the benefit of it? What if we do not have it?
b. If we want to support it, what is the right design?
c. Does PHP have the same problem?
d. How to test it?

@gcheng gcheng closed this Jun 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment