Repository navigation
A later reader's relative start on a partial lite-07 copy reads only its groups #9198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
596d1fe
9a730ef
8a27b66
20c8b22
14aab9d
43cb405
2f6a252
59fb7a6
6e1c68b
2b599e5
0d3e35c
a00d459
9512f64
529020b
14f763e
1a396d8
34fb1cf
7efd14b
36618c5
59360fc
672ddda
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1538,7 +1538,8 @@ Which fields follow, and what the Anchor names: | |
|
|
||
| Any other value is a PROTOCOL_VIOLATION. | ||
| Both ends include the Group they name, so a Range from Time `a` to Time `b` delivers every Group from the one containing `a` through the one containing `b`. | ||
| The publisher resolves a Relative or Time Anchor against the Track as it holds it. | ||
| The publisher resolves a Relative or Time Anchor against the Track as it holds it, except a Relative `Start` of one or more `Groups Back` on a relay, which never depends on the part of the Track the relay holds. | ||
| A relay resolves one to the `Range Start` its upstream reported for a Range with the same `Start`, counted from the same latest Group or a newer one: when none has, it asks its upstream for such a Range in its SUBSCRIBE or a SUBSCRIBE_UPDATE, or in a SUBSCRIBE of its own once its subscription is over, as when the Track ended, and resolves the Range only once that answer arrives. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Constrain reuse of a report that contains no group. With groups 0–9, Relative(2)..Time(6) reports no group. Relative(2)..Time(8) must still deliver groups 7 and 8. The ranges have the same Permit an empty report to settle another range only when that range's end is no later than the reported boundary. Keep concrete
|
||
| A Range resolves once: an update that leaves it live does not resolve it again. | ||
|
|
||
| A `Start` is a floor, not a request; `Subscriber Max Age` and `Subscriber Min Age` are the only things that ask for data. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Limit the cache-independence claim to relative starts.
Relative ends still count over cached groups. A sparse warm copy can therefore return different groups from a cold copy when a range has a relative end. Replace the same-groups guarantee with a relative-start placement guarantee, and state the relative-end exception.
As per coding guidelines, “State a claim's conditions with it,” including “the paths it does not cover.”
Source: Coding guidelines