To offer a chance to get response headers from once-off Download/Upload API call #129
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to reduce the API call times between Joss and back-end storage service, Joss should offer the chance to get all response headers from Object Download and Upload operation. E.g. Client wants to download an Object and get its 'Content-Length' header as well. That's easy to do with with just one time call of Swift or Ceph Radosgw download API. However, Joss has to call Swift or Radosgw twice, one is GET and the other is HEAD. That's not so pretty in the case of high concurrency of requests.
The commit offers the chance to Get/Put object and retrieve some headers from one time API call.