Ability to persist RTCCertificate in IndexedDB (enables cloning).

Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

This CL is being split up into smaller CLs:
- Pt. 1: https://codereview.chromium.org/1957293002/
- Pt. 3a-b: https://codereview.chromium.org/1962673002/
- Pt. 2+3c: https://codereview.chromium.org/1959333002/

BUG=581354

[hbos_chromium, 2016-05-04 14:05:29]

Patchset #1 (id:1) has been deleted

[hbos_chromium, 2016-05-04 14:36:44]

Description was changed from

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

BUG=581354
==========

to

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

(Based on https://codereview.chromium.org/1909923002/)

BUG=581354
==========

[hbos_chromium, 2016-05-09 14:00:11]

Part 1 CL: https://codereview.chromium.org/1957293002/

[hbos_chromium, 2016-05-09 14:01:16]

Description was changed from

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

(Based on https://codereview.chromium.org/1909923002/)

BUG=581354
==========

to

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

(Based on https://codereview.chromium.org/1909923002/)

This CL is being split up into smaller CLs:
1: https://codereview.chromium.org/1957293002/

BUG=581354
==========

[hbos_chromium, 2016-05-09 14:44:57]

Description was changed from

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

(Based on https://codereview.chromium.org/1909923002/)

This CL is being split up into smaller CLs:
1: https://codereview.chromium.org/1957293002/

BUG=581354
==========

to

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

(Based on https://codereview.chromium.org/1909923002/)

This CL is being split up into smaller CLs:
- Pt. 1: https://codereview.chromium.org/1957293002/
- Pt. 3a-b: https://codereview.chromium.org/1962673002/

BUG=581354
==========

[hbos_chromium, 2016-05-09 14:45:16]

Part 3a,3b CL: https://codereview.chromium.org/1962673002/

[hbos_chromium, 2016-05-09 14:46:33]

Description was changed from

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

(Based on https://codereview.chromium.org/1909923002/)

This CL is being split up into smaller CLs:
- Pt. 1: https://codereview.chromium.org/1957293002/
- Pt. 3a-b: https://codereview.chromium.org/1962673002/

BUG=581354
==========

to

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

This CL is being split up into smaller CLs:
- Pt. 1: https://codereview.chromium.org/1957293002/
- Pt. 3a-b: https://codereview.chromium.org/1962673002/

BUG=581354
==========

[hbos_chromium, 2016-05-16 08:47:24]

Description was changed from

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

This CL is being split up into smaller CLs:
- Pt. 1: https://codereview.chromium.org/1957293002/
- Pt. 3a-b: https://codereview.chromium.org/1962673002/

BUG=581354
==========

to

==========
Ability to persist RTCCertificate in IndexedDB (enables cloning).

The WebRTC spec[1] mandates that RTCCertificates can be persisted to storage by
an application by implementing the structured clone algorithm. This allows it to
be saved and loaded from IndexedDB.

This is achieved with the following changes:

1. RTCCertificate to/from string
   a) The ToPEM and FromPEM serialization functions from the WebRTC layer that
      converts RTCCertificate to- and from string are made visible in the blink
      and content layers.
   b) |WebRTCCertificate::keyParams| is removed so that we don't have to
      serialize this or add getters for obtaining this information from the
      WebRTC layer's RTCCertificate. The getter was never used by anyone.

2. RTCCertificate serialization (structured clone algorithm)
   a) ScriptValueSerializerForModules and friends are updated with write and
      read functions for RTCCertificate (impl using 1.).

3. Unittests making sure RTCCertificate can be saved and loaded from IndexedDB
   a) chrome/test/data/webrtc/indexeddb.js added with functions for managing
      a database and saving and loading (cloning) certificates.
   b) WebRtcTestBase implementing C++ functions for calling the indexeddb.js
      API.
   c) WebRtcBrowserTest tests added which clone certificates and sets up calls
      using the clones.

[1] https://w3c.github.io/webrtc-pc/archives/20160125/webrtc.html#attributes-6

This CL is being split up into smaller CLs:
- Pt. 1: https://codereview.chromium.org/1957293002/
- Pt. 3a-b: https://codereview.chromium.org/1962673002/
- Pt. 2+3c: https://codereview.chromium.org/1959333002/

BUG=581354
==========

[hbos_chromium, 2016-05-16 08:47:43]

Part 2,3c CL: https://codereview.chromium.org/1959333002/