Open MaZZly opened 10 months ago
Hi @MaZZly ,
For old stream-base conferencing, there is an application setting acceptOnlyRoomsInDataStore
for that. If you set it you can join only the room that is created in advance.
For the multitrack conference, after version 2.8.0 server don't use room structure anymore. Instead, a broadcast object as a main track will have the participants as subtracks. So you can prevent server with acceptOnlyStreamsInDataStore
setting. So that, new broadcast object (main track) can only be created by REST API.
Is your feature request related to a problem? Please describe.
When we do a
DELETE /v2/broadcasts/conference-rooms/{room_id}
the Javascript SDK can still recreate and start publishing to the sameroom_id
(effectively recreating it)Describe the solution you'd like
Possibility to prevent the same room_id from being recreated after deletion (for some time), this could be an option param for the call, or maybe a server setting?
Describe alternatives you've considered
Somehow limiting that rooms can only be created by server through the REST API before JS API can publish to it. But not sure if this is supported or not? docs are not helpful sadly..
Additional context
The docs are not helpful