feat: Simplify Store protocol to only define length#12
Merged
kylebarron merged 2 commits intomainfrom Feb 10, 2026
Merged
Conversation
kylebarron
changed the title
lengthlength
This file contains hidden or 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
1 participant
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.
We previously vendored the exact obspec
GetRangeAsynchere in #8. But since we internally only callget_range_asyncwithstartandlength, we can restrict the protocol further.Since this is "strictly more restricted" than obspec, this is still compatible with obspec and obstore, as shown by type checkers.
This also adds an example in the README of using a custom client.