Single session groups
Learn about single session groups.
읽는 시간 1분최근 업데이트: 10일 전
Use a single session group, rather than several, when you want to manage multiple channels together as a unit, applying requests to the whole group instead of to individual sessions, and benefit from more efficient resource use.
When sessions are all in a single session group you have access to the following functionality:
- Control transmission options: Allow a user to transmit audio into a specific session, into all sessions, or into none.
- Support multi-channel structures: Allow users to be in a proximity-based channel (3D channel) at the same time as non-proximity group channels (2D channels).
- Bandwidth efficiency: Individual audio sessions in a single session group share a capped bandwidth allocation. This limits the maximum local and remote resources required to provide audio in those sessions.
In a case where an application has more than three sessions with voice enabled and you want to transmit voice into more than one but not all of them it's best to use multiple session groups.
You can view example code for these requests and responses in the SDKSampleApp.