Confirmed users
632
edits
Loop/Architecture/Fingerprint Validation: Difference between revisions
Loop/Architecture/Fingerprint Validation (view source)
Revision as of 18:25, 24 September 2015
, 24 September 2015→Uploading Stream Fingerprints
| Line 53: | Line 53: | ||
* 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 | === Uploading PeerConnection Fingerprints === | ||
[[Loop/Architecture/Rooms# | |||
This design adds a new action to the [[Loop/Architecture/Rooms#POST_.2Frooms.2F.7Btoken.7D|POST /rooms/{token}]] endpoint; this action is called "newpc". Clients supporting fingerprint validation will send this information whenever a new PeerConnection begins media negotiation. | |||
POST /rooms/QzBbvGmIZWU HTTP/1.1 | POST /rooms/QzBbvGmIZWU HTTP/1.1 | ||
| Line 68: | Line 69: | ||
} | } | ||
* '''action''' - For sending a new PeerConnection fingerprint, this will be "newpc". | |||
* '''fingerprint''' - The new PeerConnection fingerprint. The server will store this fingerprint as part of the user's identity in the room. Fingerprint values should be de-duplicated by the server, and uploading the same fingerprint multiple times shall not be an error. | |||
=== Retrieving Room Information === | === Retrieving Room Information === | ||