Change WebRTC SslCipher to be exposed as number only.

webrtc/p2p/base/p2ptransportchannel.h

Index: webrtc/p2p/base/p2ptransportchannel.h
diff --git a/webrtc/p2p/base/p2ptransportchannel.h b/webrtc/p2p/base/p2ptransportchannel.h
index 92969c8b7e0436b798af444bb229ce678809a30e..a2e29af7d94da9016309039eae62fc9bef76cb96 100644
--- a/webrtc/p2p/base/p2ptransportchannel.h
+++ b/webrtc/p2p/base/p2ptransportchannel.h
@@ -114,7 +114,7 @@ class P2PTransportChannel : public TransportChannelImpl,
   bool GetSrtpCipher(std::string* cipher) override { return false; }

[pthatcher1, 2015/09/29 22:25:17]

If we're going to change the SslCipher to an int rather than a string, we should
probably do the same for SrtpCipher.

If it's not critical for the DTLS 1.2 work you're trying to land, can you put a
TODO and then have a follow-up CL after you land this one?

[guoweis_webrtc, 2015/09/30 04:09:47]

Changing srtp is probably more work. GetSrtpCipher is used in for example
talk/session/media/channel.h as string already.

BoringSSL defines these integers already so it's easy for us to reuse instead of
redefining our own. I don't know if it's the case for SRTP. I could be wrong but
I don't think it's the case. It's just where we want the integer version
ourselves internally. I agree this is more consistent but not sure how much it
buys for us.

 
   // Find out which DTLS cipher was negotiated.
-  bool GetSslCipher(std::string* cipher) override { return false; }
+  bool GetSslCipher(uint16_t* cipher) override { return false; }
 
   // Returns null because the channel is not encrypted by default.
   rtc::scoped_refptr<rtc::RTCCertificate> GetLocalCertificate() const override {