Implement PPB_Flash_TCPSocket.InitiateSSL.

net/socket/client_socket_factory.h

Index: net/socket/client_socket_factory.h
diff --git a/net/socket/client_socket_factory.h b/net/socket/client_socket_factory.h
index c2e03505a7a0b46e366c0d191c4c86ed9e9c43b3..c5e3dda903aaf0a5651ff94c952b94e01ed99bc3 100644
--- a/net/socket/client_socket_factory.h
+++ b/net/socket/client_socket_factory.h
@@ -47,6 +47,9 @@ class NET_API ClientSocketFactory {
       NetLog* net_log,
       const NetLog::Source& source) = 0;
 
+  // It is allowed to pass in a |transport_socket| that is not obtained from a
+  // socket pool. The caller could create a ClientSocketHandle directly and call
+  // set_socket() on it to set a valid StreamSocket instance.

[wtc, 2011/08/09 21:21:29]

It is fine by me to support creating such a ClientSocketHandle.
We should add a unit test to verify this kind of ClientSocketHandle
can be used by SSLClientSocket successfully.

Right now SSLClientSocketNSS calls only the following
two methods on ClientSocketHandle:

ClientSocketHandle::socket()
ClientSocketHandle destructor

So a simple unit test can be used to test this.

[yzshen1, 2011/08/09 23:45:29]

Do you mean I need to add one in this CL?

On 2011/08/09 21:21:29, wtc wrote:

[yzshen1, 2011/08/12 21:31:39]

wtc: the unit test is:

  scoped_ptr<ClientSocketHandle> socket(new ClientSocketHandle);
  socket.set_socket(...);

  scoped_ptr<ClientSocketHandle> transport(socket.release());

  transport->socket()->Read();  // No need to test these

  // Just verify that such a simple ClientSocketHandle,
  // not associated with any client socket pool, can be]
  // destroyed safely.

[yzshen1, 2011/08/13 00:40:34]

Done.

   virtual SSLClientSocket* CreateSSLClientSocket(
       ClientSocketHandle* transport_socket,
       const HostPortPair& host_and_port,