From 23314cbc5e4a1fec387cb4c8d133812138ed9a38 Mon Sep 17 00:00:00 2001 From: Cullen Jennings Date: Sat, 6 May 2017 06:43:02 -0600 Subject: [PATCH] revert PR#1108 --- webrtc.html | 63 +++++++++++++++++++++-------------------------------- 1 file changed, 25 insertions(+), 38 deletions(-) diff --git a/webrtc.html b/webrtc.html index dc7debe66..15b2f95cf 100644 --- a/webrtc.html +++ b/webrtc.html @@ -79,13 +79,6 @@

Terminology

handlers and event handler event types are defined in [[!HTML5]].

-

The terms - serializable objects, - serialization steps, and - deserialization steps are defined in [[!HTML]].

The terms MediaStream, MediaStreamTrack, and MediaStreamConstraints are defined in [[!GETUSERMEDIA]].

The term Blob is defined in [[!FILEAPI]].

@@ -4544,8 +4537,7 @@

RTCCertificate Interface

"RTCCertificate-certificate">certificate]]) that RTCPeerConnection uses to authenticate with a peer.

- 
[Serializable]
-interface RTCCertificate {
+          
interface RTCCertificate {
     readonly        attribute DOMTimeStamp expires;
     sequence<RTCDtlsFingerprint> getFingerprints ();
     // At risk due to lack of implementers' interest.
@@ -4608,36 +4600,31 @@ 
Methods

         contains unstructured binary data.

         
Note that a RTCCertificate might not directly hold
         private keying material, this might be stored in a secure module.

-
-        
RTCCertificate objects are serializable objects
-        [[!HTML]]. Their serialization steps, given value and
-        serialized, are:

-
-        
    
-          
  1. Set serialized.[[\expires]] to the value of
-          value's expires attribute.
    2. 
-
-          
  2. Set serialized.[[\certificate]] to
-          a copy of the unstructured binary data in
-          value.[[certificate]].
    3. 
-
-          
  3. Set serialized.[[\handle]] be a serialization of the
-          private keying material represented by
-          value.[[handle]].
    4. 
-        

-
-        
Their deserialization steps, given serialized and
-        value, are:

-
+        
The RTCCertificate object can be stored and retrieved
+        from persistent storage by an application. When a user agent is
+        required to obtain a structured clone [[!HTML5]] of a
+        RTCCertificate object, it performs the following
+        steps:

         
    
-          
  1. Initialize value's expires attribute to
-          contain serialized.[[\expires]].
    2. 
-
-          
  2. Set value.[[certificate]] to
-          serialized.[[\certificate]].
    3. 
-
-          
  3. Set value.[[handle]] to the private key material
-          resulting from deserializing serialized.[[\handle]].
    4. 
+          
  4. Let input and memory be the corresponding
+          inputs defined by the internal structured cloning algorithm, where
+          input represents a RTCCertificate object to
+          be cloned.
    5. 
+          
  5. Let output be a newly constructed
+          RTCCertificate object.
    6. 
+          
  6. Copy the value of the expires attribute from
+          input to output.
    7. 
+          
  7. Let the [[certificate]] internal slot of output
+          be set to the result of invoking the internal structured clone
+          algorithm recursively on the corresponding internal slots of
+          input, with the slot contents as the new
+          "input" argument and memory as the new
+          "memory" argument.
+          
    8. 
+          
  8. Let the [[handle]] internal slot of output
+          refer to the same private keying material represented by the
+          [[handle]] internal slot of input.
+          
    9.