Conversation
theomonnom
reviewed
Feb 3, 2025
Member
|
How is it working after directly publishing a track? Is there some possible race conditions where someone could have seen/heard 1 second of a track? |
Member
Author
it's possible there's a race.. if permission is strictly desired, then the user could disallow all before publishing the track. I think it would make sense for us to include this option during track publication too. I'll add it to the protocol and we'll get it implemented on the server side first |
theomonnom
approved these changes
Feb 5, 2025
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
depends on livekit/rust-sdks#563