-
Notifications
You must be signed in to change notification settings - Fork 26
Update generateKeyFrame to take single optional rid and remove timestamp #269
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
Conversation
1. Create a pending key frame task called |task| with |task|.`[[rid]]` set to rid and |task|.`[[promise]]`| set to |promise|. | ||
1. If |encoder|.`[[pendingKeyFrameTasks]]` is undefined, initialize |encoder|.`[[pendingKeyFrameTasks]]` to an empty set. | ||
1. Let |shouldTriggerKeyFrame| be <code>false</code> if |encoder|.`[[pendingKeyFrameTasks]]` contains a task whose `[[rid]]` | ||
value is equal to |rid|, and <code>true</code> otherwise. | ||
value is either undefined or equal to |rid|, and <code>true</code> otherwise. |
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.
It makes undefined a special value and coalescing will not happen between undefined and rid1.
It might be better to coalesce and replace the undefined value by the list of all rids.
LGTM in general once we try coalescing calls using undefined and real values. |
this does not sound like the decision had a valid consensus. |
I'll try to split this PR into a couple of pieces to merge the (hopefully) non-controversial parts:
|
Fixes #143 by aligning with previous decision. Getting this ready for Interop 2025.
Preview | Diff