Server-initiated unpublish & permissions #107
Merged
Conversation
This file contains 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
hiroshihorie
approved these changes
Mar 21, 2022
boks1971
approved these changes
Mar 21, 2022
| // allow participant to publish data | ||
| bool can_publish_data = 3; | ||
| // indicates that it's hidden to others | ||
| bool hidden = 7; |
There was a problem hiding this comment.
gaps are due to deprecated stuff in between?
There was a problem hiding this comment.
yup, for backwards compatibility, field numbers cannot change.
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.
Enable server to unpublish tracks. i.e. when a participant's publish permissions are revoked.
Also cleaned up participant permissions, and returning them to clients so each participant is aware of its and others' permissions.