Making RTCCertificate cloneable (WIP).

Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPEM() function.
- WebRTCCertificateGenerator and implementation gets a fromPEM() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPEM/fromPEM steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPEM factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

Depends on CLs (now landed):
- third_party/webrtc CL https://codereview.webrtc.org/1898383003/
  which adds ToPEM/FromPEM to rtc::RTCCertificate.
- chromium CL https://codereview.chromium.org/1917133002/
  which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354

[hbos_chromium, 2016-04-21 12:48:31]

Patchset #1 (id:1) has been deleted

[hbos_chromium, 2016-04-21 13:13:06]

Patchset #1 (id:20001) has been deleted

[hbos_chromium, 2016-04-21 13:53:23]

Description was changed from

==========
Making RTCCertificate cloneable.

WIP with third_party/webrtc patch applied locally:
https://codereview.webrtc.org/1898383003/

BUG=
==========

to

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

CL is using third_party/webrtc patch https://codereview.webrtc.org/1898383003/
which adds ToPem/FromPem to rtc::RTCCertificate.

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

BUG=chromium:581354
==========

[hbos_chromium, 2016-04-26 10:19:05]

Description was changed from

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

CL is using third_party/webrtc patch https://codereview.webrtc.org/1898383003/
which adds ToPem/FromPem to rtc::RTCCertificate.

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

BUG=chromium:581354
==========

to

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

CL is using third_party/webrtc patch https://codereview.webrtc.org/1898383003/
which adds ToPem/FromPem to rtc::RTCCertificate.
And chromium patch https://codereview.chromium.org/1917133002/
which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

[hbos_chromium, 2016-04-28 13:34:59]

Description was changed from

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

CL is using third_party/webrtc patch https://codereview.webrtc.org/1898383003/
which adds ToPem/FromPem to rtc::RTCCertificate.
And chromium patch https://codereview.chromium.org/1917133002/
which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

to

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates *currently saves
  and loads a string, not an RTCCertificate, will update*.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

CL is using third_party/webrtc patch https://codereview.webrtc.org/1898383003/
which adds ToPem/FromPem to rtc::RTCCertificate.
And chromium patch https://codereview.chromium.org/1917133002/
which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

[hbos_chromium, 2016-04-29 13:39:19]

Description was changed from

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates *currently saves
  and loads a string, not an RTCCertificate, will update*.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

CL is using third_party/webrtc patch https://codereview.webrtc.org/1898383003/
which adds ToPem/FromPem to rtc::RTCCertificate.
And chromium patch https://codereview.chromium.org/1917133002/
which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

to

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates *currently saves
  and loads a string, not an RTCCertificate, will update*.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

Depends on CLs (now landed):
- third_party/webrtc CL https://codereview.webrtc.org/1898383003/
  which adds ToPem/FromPem to rtc::RTCCertificate.
- chromium CL https://codereview.chromium.org/1917133002/
  which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

[hbos_chromium, 2016-04-29 13:40:11]

Description was changed from

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPem() function.
- WebRTCCertificateGenerator and implementation gets a fromPem() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPem/fromPem steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates *currently saves
  and loads a string, not an RTCCertificate, will update*.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPem factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

Depends on CLs (now landed):
- third_party/webrtc CL https://codereview.webrtc.org/1898383003/
  which adds ToPem/FromPem to rtc::RTCCertificate.
- chromium CL https://codereview.chromium.org/1917133002/
  which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

to

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPEM() function.
- WebRTCCertificateGenerator and implementation gets a fromPEM() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPEM/fromPEM steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates *currently saves
  and loads a string, not an RTCCertificate, will update*.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPEM factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

Depends on CLs (now landed):
- third_party/webrtc CL https://codereview.webrtc.org/1898383003/
  which adds ToPEM/FromPEM to rtc::RTCCertificate.
- chromium CL https://codereview.chromium.org/1917133002/
  which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

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

Description was changed from

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPEM() function.
- WebRTCCertificateGenerator and implementation gets a fromPEM() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPEM/fromPEM steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates *currently saves
  and loads a string, not an RTCCertificate, will update*.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPEM factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

Depends on CLs (now landed):
- third_party/webrtc CL https://codereview.webrtc.org/1898383003/
  which adds ToPEM/FromPEM to rtc::RTCCertificate.
- chromium CL https://codereview.chromium.org/1917133002/
  which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

to

==========
Making RTCCertificate cloneable.

This CL makes RTCCertificate JavaScript objects cloneable according to the
structured clone algorithm as ordered by the WebRTC spec[1]. This makes it
possible to store and retrieve certificates persistently with IndexedDB.

Changes - RTCCertificate:
- WebRTCCertificate and implementation gets a toPEM() function.
- WebRTCCertificateGenerator and implementation gets a fromPEM() function.
- WebRTCCertificate no longer has keyParams(), this function was not used and
  rtc::RTCCertificate currently has no function to retrieve the key params so
  this information would be lost in the toPEM/fromPEM steps.
- ScriptValueSerializerForModules is updated to be able to write and read
  RTCCertificate (using the PEM functions).
Changes - IndexedDB:
- indexeddb.js added with functions to manage a IndexedDB database for WebRTC
  browser tests.
- WebRtcTestBase updated to call indexeddb.js functions from C++ test code.
- WebRtcBrowserTest: New test that saves and loads certificates.

Overview of certificate-related classes this CL touches (to aid reviewers):
- JavaScript RTCCertificate, internally contains a C++ version of certificate:
  blink::RTCCertificate
- C++ versions of RTCCertificate (blink, content and webrtc layers):
  blink::WebRTCCertificate < content::RTCCertificate > rtc::RTCCertificate
- Certificate generator & fromPEM factory (blink and content layers):
  blink::WebRTCCertificateGenerator < content::RTCCertificateGenerator
(The abstractions (blink interface/content impl) are necessary to avoid illegal
dependencies.)

Depends on CLs (now landed):
- third_party/webrtc CL https://codereview.webrtc.org/1898383003/
  which adds ToPEM/FromPEM to rtc::RTCCertificate.
- chromium CL https://codereview.chromium.org/1917133002/
  which adds choosing certificates in WebRtcTestBase for WebRtcBrowserTest.

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

BUG=chromium:581354
==========

[hbos_chromium, 2016-05-04 14:37:27]

Replaced by https://codereview.chromium.org/1949033002/