Remove HTTP pipelining support.

net/base/load_timing_info.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef NET_BASE_LOAD_TIMING_INFO_H_
 #define NET_BASE_LOAD_TIMING_INFO_H_
 
 #include "base/basictypes.h"
 #include "base/time/time.h"
 #include "net/base/net_export.h"
@@ skipping 22 matching lines @@
 // ssl_start
 // ssl_end
 // connect_end
 // send_start
 // send_end
 // receive_headers_end
 //
 // Times represent when a request starts/stops blocking on an event, not the
 // time the events actually occurred.  In particular, in the case of preconnects
 // and socket reuse, no time may be spent blocking on establishing a connection.
-// In the case of SPDY and HTTP pipelining, PAC scripts are only run once for
-// each shared session, so no time may be spent blocking on them.
+// In the case of SPD, PAC scripts are only run once for each shared session, so

[willchan no longer on Chromium, 2014/05/23 20:31:21]

You got overzealous in deleting the 'Y' :)

[mmenke, 2014/05/23 20:36:37]

Done.

+// no time may be spent blocking on them.
 //
 // DNS and SSL times are both times for the host, not the proxy, so DNS times
 // when using proxies are null, and only requests to HTTPS hosts (Not proxies)
 // have SSL times.  One exception to this is when a proxy server itself returns
 // a redirect response.  In this case, the connect times treat the proxy as the
 // host.  The send and receive times will all be null, however.
 // See HttpNetworkTransaction::OnHttpsProxyTunnelResponse.
 // TODO(mmenke):  Is this worth fixing?
 //
 // Note that internal to the network stack, times are when events actually
@@ skipping 77 matching lines @@
   base::TimeTicks send_start;
   base::TimeTicks send_end;
 
   // The time at which the end of the HTTP headers were received.
   base::TimeTicks receive_headers_end;
 };
 
 }  // namespace net
 
 #endif  // NET_BASE_LOAD_TIMING_INFO_H_