Confirmed users
632
edits
Loop/Architecture/Fingerprint Validation: Difference between revisions
Jump to navigation
Jump to search
Loop/Architecture/Fingerprint Validation (view source)
Revision as of 18:14, 24 September 2015
, 24 September 2015→Joining a Room
| Line 22: | Line 22: | ||
=== Joining a Room === | === Joining a Room === | ||
[[Loop/Architecture/Rooms#Joining a Room]] | |||
For this scheme to work in a backwards-compatible fashion, the participants in a conversation need to know whether to expect their peers to be publishing fingerprints. For this, we add a simple capabilities announcement mechanism when users join a room. This is an additional parameter on the messages described at [[Loop/Architecture/Rooms#Joining a Room]]: | |||
POST /rooms/QzBbvGmIZWU HTTP/1.1 | POST /rooms/QzBbvGmIZWU HTTP/1.1 | ||
| Line 33: | Line 34: | ||
{ | { | ||
"action": "join", | "action": "join", | ||
"displayName": " | "displayName": "-", | ||
"clientMaxSize": 2, | "clientMaxSize": 2, | ||
'''"features": ["fingerprint"]''' | '''"features": ["fingerprint"]''' | ||
} | } | ||
* '''features''': An array of optional client behaviors that depend on the version of the client. Currently, only one value is defined: | |||
** ''fingerprint'': Indicates support of the PeerConnection fingerprint validation mechanism. If this mechanism is present when the user joins a room, then the server must include a "fingerprints" array (which will initially be empty) as part of the user identification information. If absent, the server must not include such an array. | |||
=== User Identification in a Room === | === User Identification in a Room === | ||