Confirmed users
632
edits
Loop/Architecture/Fingerprint Validation: Difference between revisions
Loop/Architecture/Fingerprint Validation (view source)
Revision as of 18:05, 24 September 2015
, 24 September 2015→API Changes
No edit summary |
|||
| Line 16: | Line 16: | ||
== API Changes == | == API Changes == | ||
This design proposes minimal changes to the Loop server protocol to allow clients to upload valid fingerprints for the room they are joining. At a high level, we expand the data maintained for a user in a room to include an array of fingerprints. Each fingerprint corresponds to an active PeerConnection associated with the room. | |||
The following examples replace "displayName" with "-", as that is the behavior currently exhibited by the Hello client. | |||
=== Joining a Room === | === Joining a Room === | ||
| Line 47: | Line 51: | ||
* fingerprints: A list of "fingerprint" values associated with all the PeerConnections the client currently has in use. Only included if client included "fingerprint" in features array in "join" | * fingerprints: A list of "fingerprint" values associated with all the PeerConnections the client currently has in use. Only included if client included "fingerprint" in features array in "join" | ||
=== | === Uploading Stream Fingerprints === | ||
[[Loop/Architecture/Rooms#Joining a Room]] | [[Loop/Architecture/Rooms#Joining a Room]] | ||