Skip to content
Snippets Groups Projects
  1. Apr 28, 2010
  2. Apr 23, 2010
    • vandebo@chromium.org's avatar
      Add net log entries that summarize transmit and receive byte counts. · a2006ece
      vandebo@chromium.org authored
      Tx/Rx summaries are integrated into the net log at the last point that bytes were transmitted or received.
      
      Hopefully this will help resolve http://crbug.com/37729 by showing if we've received bytes over the network when we hit the "Waiting for cache" bug.
      
      This change also modernizes the use of NetLog:
       - ClientSocket now has a net_log() accessor
       - ClientSocket::Connect no longer takes a NetLog, instead the TCPClientSocket constructor takes one, others use their transport socket's NetLog
       - TCPClientSocket creates a new source id with source type SOCKET
      
      Also updates PassiveLogCollector infrastructure:
       - The LiveRequestsObserver lets a RequestTracker update a RequestInfo just before it is displayed.  This allows ConnectJobs to be associated with URLRequests while connecting and then reassociated if they are late-bound to a different request.
      
      BUG=37729
      TEST=tx/rx lines show up in chrome://net-internals/
      
      Review URL: http://codereview.chromium.org/1696005
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45449 0039d316-1c4b-4281-b951-d872f2087c98
      a2006ece
  3. Mar 16, 2010
  4. Feb 09, 2010
  5. Feb 05, 2010
  6. Feb 02, 2010
  7. Jan 29, 2010
  8. Jan 07, 2010
  9. Nov 11, 2009
  10. Nov 06, 2009
  11. Nov 02, 2009
  12. Aug 12, 2009
  13. Jul 18, 2009
  14. Jul 15, 2009
    • ericroman@google.com's avatar
      Refactorings surrounding HostResolver: · b59ff376
      ericroman@google.com authored
      (1) Extract HostResolver to an interface.
      
      The existing concrete implementation is now named HostResolverImpl. This makes it possible to create mocks with more complex behavior (i.e. choose via rules if response will be sync vs async).
      
      (2) Transform HostMapper into HostResolverProc.
      
      Conceptually HostResolverProc maps a hostname to a socket address, whereas HostMapper mapped a hostname to another hostname (so you were still at the mercy of the system's host resolver). With HostResolverProc you can specify the exact AddressList, making it possible to run tests requiring IPv6 socketaddrs on systems (like WinXP) that don't actually support it.
      
      (3) Add a MockHostResolver implementation of HostResolver.
      
      This replaces the [ScopedHostMapper + RuleBasedHostMapper + HostResolver] combo. It is less clunky and a bit more expressive.
      
      BUG=http://crbug.com/16452
      R=willchan
      TEST=existing
      
      Review URL: http://codereview.chromium.org/149511
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20795 0039d316-1c4b-4281-b951-d872f2087c98
      b59ff376
  15. Jun 28, 2009
  16. Jun 27, 2009
  17. Jun 26, 2009
Loading