Skip to content
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

[Feature Request]: Setting for LiveCanvas to prevent local user from sending signals / making ops #721

Open
ryanbliss opened this issue Oct 2, 2023 · 0 comments
Labels
enhancement New feature or request live share canvas work Work related to the live-share-canvas sdk package

Comments

@ryanbliss
Copy link
Contributor

Describe your user scenario

For large meetings / connection volume, it is important to have a small amount of clients that can send outgoing signals when possible. so that developers can implement a "presenter only" state, where only the cursors / strokes of active presenter(s) would be visible.

Describe the solution you'd like

We should follow the pattern from LiveMediaSession and our other open issues to put in a canSendCursorUpdates and canSendInkingUpdates. Since LiveCanvas does not use LiveObjectSynchronizer, these settings likely must be within the DDS itself.

@ryanbliss ryanbliss added enhancement New feature or request new submission Issues that have been filed and not yet processed by DRI live share canvas work Work related to the live-share-canvas sdk package and removed new submission Issues that have been filed and not yet processed by DRI labels Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request live share canvas work Work related to the live-share-canvas sdk package
Projects
None yet
Development

No branches or pull requests

1 participant