Skip to content
Snippets Groups Projects
Commit 8a6f7079 authored by Adrien Béraud's avatar Adrien Béraud
Browse files

Update 6.1. Conference Protocol

parent dfd30ff7
Branches
Tags
No related merge requests found
Show whitespace changes
Inline Side-by-side
technical/6.1.-Conference-Protocol.md
+ 2
− 0
View file @ 8a6f7079
...@@ -46,6 +46,8 @@ Note: Actually, the word participant is used for callId mixed in a conference. T ...@@ -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:
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment