Update 6.1. Conference Protocol
This commit is contained in:
parent
dfd30ff794
commit
8a6f707909
|
@ -46,6 +46,8 @@ Note: Actually, the word participant is used for callId mixed in a conference. T
|
||||||
|
|
||||||
The goal is to notify all participants of the metadata of the rendered video. This means what participant is in the conference and where the video is located.
|
The goal is to notify all participants of the metadata of the rendered video. This means what participant is in the conference and where the video is located.
|
||||||
|
|
||||||
|
If a participant is itself a conference, its incoming layout info should be merged when sent to other participants. Layout info must not be merged when sent back to a conference.
|
||||||
|
|
||||||
### Layout Info
|
### Layout Info
|
||||||
|
|
||||||
The Layout is stored as a VectorMapStringString for clients and internally with a vector<ParticipantInfo> with the following format:
|
The Layout is stored as a VectorMapStringString for clients and internally with a vector<ParticipantInfo> with the following format:
|
||||||
|
|
Loading…
Reference in New Issue