Makes waiting SSLConnectJobs use the message loops to resume their connection.

net/socket/ssl_client_socket_openssl.h

Index: net/socket/ssl_client_socket_openssl.h
diff --git a/net/socket/ssl_client_socket_openssl.h b/net/socket/ssl_client_socket_openssl.h
index f18eec5874eb50422b0dd28eec163db85e99eb68..f53f017e9ae280e6eb2b3437d1a170337b35d18f 100644
--- a/net/socket/ssl_client_socket_openssl.h
+++ b/net/socket/ssl_client_socket_openssl.h
@@ -222,6 +222,8 @@ class SSLClientSocketOpenSSL : public SSLClientSocket {
   ServerBoundCertService* server_bound_cert_service_;
 
   // Callback that is invoked when the connection encounters an error.
+  // This callback should be run regardless of whether or not this socket
+  // will still be valid at its runtime.

[Ryan Sleevi, 2014/07/10 20:30:45]

Sorry that it seems like I still wasn't clear.

The caller/user of the SSLClientSocket should never have to read to the data
members - that's documentation for the implementer/coder

What matters is the documentation on the public methods; in particular,
SetSocketFailureCallback (on the base class)

[mshelley, 2014/07/10 22:49:58]

Done.

   base::Closure error_callback_;
 
   // True if there may be pending sockets waiting for this socket to connect.