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.
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
LiveMediaSessionand our other open issues to put in acanSendCursorUpdatesandcanSendInkingUpdates. SinceLiveCanvasdoes not useLiveObjectSynchronizer, these settings likely must be within the DDS itself.