Remove the disposeMessage parameter from HttpApiCall<T> for now. Sending the request with .NET disposes the HttpContent so setting disposeMessage to false is misleading; it would still not be possible to use the object to send multiple messages.
Throw ObjectDisposedException if HttpApiCall<T> is used after it is disposed
Expanded extensibility for HttpApiCall<T>
Improved extensibility of HttpApiCall<T> by adding interfaces and a DelegatingHttpApiCall<T>
Define specific classes for each of the core Object Storage API calls
Support specifying a RangeHeaderValue for GetObjectAsync
Update ObjectVersioningExtensions to use the new API call types
Fixup RangeHeaderValue support
Add ContainerQuotaExtensions
Extract top-level class OpenStack.IO.ProgressStream
Add ExtractArchiveExtensions
Remove old copies of the Extract Archive object model classes