Allow unknown ranges in a FETCH response #1331
Open
Conversation
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
This is a proposal to address several open FETCH issues. Replace UNKNOWN_STATUS_IN_RANGE with a data-stream encoding of an UNKNOWN range. This requires leaving DOES_NOT_EXIST serializations in fetch, so a omitted range can be split between DNE and UNKNOWN. But that seems OK to me. I'm unsure if it addresses #945 completely, but it gives a bandwidth constrained publisher another option that doesn't completely fail the fetch. Fixes: #1265 Fixes: #1057 Maybe addresses: #945
afrind
added
Design
Co-authored-by: ianswett <[email protected]>
ianswett
approved these changes
Nov 4, 2025
ianswett
added
the
Merge Ready
afrind
removed
the
Merge Ready
afrind
changed the title
Collaborator
Author
|
@vasilvv would you like to propose alternate spelling? |
Collaborator
Author
|
Discussed in 11/17 Interim: The wg liked this general functionality but would like a richer set of "UNKNOWN" reasons like "publisher unavailable", etc. and agree #1342 should go first. |
Collaborator
|
I've complained about the proposed syntax in this PR, so I am proposing the alternative: If the highest bit in serialization flags is set, the following message is not an object, but some fetch-related metadata. The remaining 7 bits denote the type of the metadata in question. The first byte immediately after that indicates metadata length. We define Flags = 0x80 to mean "range of objects with unknown status". It has the following syntax: Not sure if the range end should be inclusive or not, probably not. |
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.
This is a proposal to address several open FETCH issues.
Replace UNKNOWN_STATUS_IN_RANGE with a data-stream encoding of an UNKNOWN range. This requires leaving DOES_NOT_EXIST serializations in fetch, so a omitted range can be split between DNE and UNKNOWN. But that seems OK to me.
I'm unsure if it addresses #945 completely, but it gives a bandwidth constrained publisher another option that doesn't completely fail the fetch. (Ian believes it does resolve #945, unless others object)
Fixes: #1265
Fixes: #1057
Fixes: #945