Skip to content

Clarify how Latest Object works when the Largest Object is incomplete #937

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

afrind
Copy link
Collaborator

@afrind afrind commented Apr 21, 2025

Fixes: #592

@afrind afrind added the Design Issues or PRs that change how MoQ works including the wire format. label Apr 21, 2025
@afrind afrind requested a review from wilaw April 21, 2025 21:44
@afrind afrind changed the title Clarify how Latest Object works the the Largest Object is incomplete Clarify how Latest Object works when the Largest Object is incomplete Apr 24, 2025
these Objects do not pass the Latest Object filter.
{0, 0}. There is no End Group - the subscription is open ended. If an
implementation has published or received the beginning of a new `Largest Object`
but not the end, it can choose either this "current" Object or the previous
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it really smart to have an either or definition here. Isn't it better to have a single definition. I understand that there are a timing aspect here. But, wouldn't it be clearer to define this to be either largest fully received object, or largest that has started to be received, and not make it either or.

@ianswett
Copy link
Collaborator

At the virtual interim, there was interest in increasing the largest Object value as soon as the beginning of that Object arrives and not giving publishers the option of whether to deliver an in progress Object.

Also, there was interest in making sure all the cases largest Object is used in the draft are clear and more of them may need updating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design Issues or PRs that change how MoQ works including the wire format.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarification on what current object means in SUBSCRIBE, SUBSCRIBE_OK and FETCH
3 participants