Don't cancel outstanding connect jobs when "flushing" socket pool.

net/socket/client_socket_pool_base.cc

Index: net/socket/client_socket_pool_base.cc
===================================================================
--- net/socket/client_socket_pool_base.cc	(revision 54089)
+++ net/socket/client_socket_pool_base.cc	(working copy)
@@ -653,7 +653,6 @@
 
 void ClientSocketPoolBaseHelper::Flush() {
   pool_generation_number_++;
-  CancelAllConnectJobs();

[Mike Belshe, 2010/07/29 09:18:42]

This might not be the best fix.

Another way to go would be to add code to do the notifications.

I believe it would go into CancelAllConnectJobs and look like this:

  while (group.pending_requests.size()) {
    scoped_ptr<const Request> request(
        RemoveRequestFromQueue(
          group.pending_requests.begin(),
          &group.pending_requests));
    InvokeUserCallbackLater(r->handle(), r->callback(), ERR_ABORTED);
  }


If you don't do it this way, then we're not being 100% clean on our flushing,
which effects benchmarks and such.

   CloseIdleSockets();
 }