Matrix/element-call-Github
1
0
Fork 0
mirror of https://github.com/vector-im/element-call.git synced 2026-03-28 06:50:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify implementation suggestions.

Browse Source
This commit is contained in:
David Baker
2023-03-08 11:21:23 +00:00
parent 6a76873cee
commit c06d3d494d
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/mid-based-signalling.md
View File

@@ -150,10 +150,12 @@ list of tracks. It would be more duplication but maybe less effort to read.
The expected behaviour here would be for foci to essentially maintain a structure with all
tracks being pushed to it. This structure would probably have call IDs as a top level index,
then look very similar to the structure of the `m.call.advertise` event. It could either keep
then look very similar to the structure of the `m.call.advertise` event. It could keep
a reference to the transceiver it was receiving media on in the structure itself alongside
the media UUID, or maintain a separate map of media UUID to transceiver / peer connection such
that the first structure could be marshalled to JSON and sent to clients as-is.
that the first structure could be marshalled to JSON and sent to clients as-is. These are just
potential implementations though, all that is important is that the focus maintains sufficient
information about each track being sent to each client.
On the client side, the client will essentially take the `m.call.advertise` data and save it
almost as-is. It would probably cross-reference it against the call member state events to