Confirmed users
632
edits
Loop/Architecture/Fingerprint Validation: Difference between revisions
Loop/Architecture/Fingerprint Validation (view source)
Revision as of 18:55, 24 September 2015
, 24 September 2015→Client Behavior
| Line 122: | Line 122: | ||
In more detail: when the setLocalDescription shim is called, it extracts the fingerprint attribute from the SDP that was passed to that function, and enqueues it to be sent to the Loop server (e.g., using <tt>setTimeout(...,0)</tt>). The fingerprint is sent using a "POST /rooms/{token}" request, with action=newpc, as described in [#Uploading PeerConnection Fingerprints] | In more detail: when the setLocalDescription shim is called, it extracts the fingerprint attribute from the SDP that was passed to that function, and enqueues it to be sent to the Loop server (e.g., using <tt>setTimeout(...,0)</tt>). The fingerprint is sent using a "POST /rooms/{token}" request, with action=newpc, as described in [#Uploading PeerConnection Fingerprints] | ||
When the setRemoteDescription shim is called, it enqueues a function with a relatively short timeout ( | When the setRemoteDescription shim is called, it enqueues a function with a relatively short timeout (I propose 5 seconds) that performs the following steps: | ||
# Check the list of fingerprints published by other person in the room. | # Check the list of fingerprints published by other person in the room. | ||