Http Cache: Add code for simulating an infinite HTTP cache.

net/http/infinite_cache.h

Index: net/http/infinite_cache.h
===================================================================
--- net/http/infinite_cache.h	(revision 0)
+++ net/http/infinite_cache.h	(revision 0)
@@ -0,0 +1,119 @@
+// 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.
+
+// This is the interface of a simulated infinite cache. The purpose of this
+// code is to evaluate the performance of an HTTP cache that is not constrained
+// to evict resources.
+
+#ifndef NET_HTTP_INFINITE_CACHE_H_
+#define NET_HTTP_INFINITE_CACHE_H_
+
+#include <string>
+
+#include "base/basictypes.h"
+#include "base/memory/scoped_ptr.h"
+#include "base/memory/weak_ptr.h"
+#include "base/timer.h"
+#include "net/base/completion_callback.h"

[gavinp, 2012/09/13 04:45:43]

Can't we drop this include?

[rvargas (doing something else), 2012/09/13 23:50:28]

I cannot forward declare it, because it is a typedef.

+#include "net/base/net_export.h"
+
+class FilePath;
+
+namespace base {
+class SequencedTaskRunner;
+class SequencedWorkerPool;
+}
+
+namespace net {
+
+class HttpCache;
+class HttpResponseInfo;
+class InfiniteCache;
+struct HttpRequestInfo;
+
+// An InfiniteCacheTransaction is paired with an HttpCache::Transaction to track
+// every request that goes through the HttpCache. This object is notified when
+// relevant steps are reached while processing the request.
+class NET_EXPORT_PRIVATE InfiniteCacheTransaction {

[gavinp, 2012/09/13 04:45:43]

A question: Is the NET_EXPORT_PRIVATE required when the unit test is also in
net/ ? Why? Is it because unit_tests use the same libnet.a/.so/.dll that is
built for chrome and content_browser etc...?

[rvargas (doing something else), 2012/09/13 22:44:07]

net_unittests doesn't link in net on the component build, so if it wants to
access this class it has to be exported.

+ public:
+  explicit InfiniteCacheTransaction(InfiniteCache* cache);
+  ~InfiniteCacheTransaction();
+
+  // Called when a new HttpTransaction is started.
+  void OnRequestStart(const HttpRequestInfo* request);
+
+  // Called when the response headers are available.
+  void OnResponseReceived(const HttpResponseInfo* response);
+
+  // Called when the response data is received from the network.
+  void OnDataRead(const char* data, int data_len);
+
+  // Called when the resource is marked as truncated by the HttpCache.
+  void OnTruncatedResponse();
+
+  // Called when the resource is served from the cache, so OnDataRead will not
+  // be called for this request.
+  void OnServedFromCache();
+
+ private:
+  friend class InfiniteCache;
+  struct ResourceData;
+  void Finish();
+
+  base::WeakPtr<InfiniteCache> cache_;
+  scoped_ptr<ResourceData> resource_data_;
+  bool done_;
+  bool doom_method_;

[gavinp, 2012/09/13 04:45:43]

Nit: I don't think this is well named. It stores if the transaction will doom
the entry or not, presuming that our infinite cache doesn't store multiple
entries for the same URL, right? Maybe something like method_will_doom_entry_ ?

[rvargas (doing something else), 2012/09/13 22:44:07]

I don't get the part about multiple entries, but yes, it says that the method
used for the request should result in the entry being doomed.

must_doom_entry_ ?

[gavinp, 2012/09/14 03:27:28]

It's just that GETs replace anything with the same URL, even if the previously
stored GET had different Vary headers. The hit rate of the cache would be higher
if we could keep each version, since a future request might use the same Vary
headers as earlier.

I don't think we need to do this for our first stats gathering.
must_doom_entry_!

+  DISALLOW_COPY_AND_ASSIGN(InfiniteCacheTransaction);
+};
+
+// An InfiniteCache is paired with an HttpCache instance to simulate an infinite
+// backend storage.
+class NET_EXPORT_PRIVATE InfiniteCache
+    : public base::SupportsWeakPtr<InfiniteCache> {
+ public:
+  InfiniteCache();
+  ~InfiniteCache();
+
+  // Initializes this object to start tracking requests. |path| is the location
+  // of the file to use to store data; it can be empty, in which case the data
+  // will not be persisted to disk.
+  void Init(const FilePath& path);
+
+  InfiniteCacheTransaction* CreateInfiniteCacheTransaction();
+
+  // Removes all data for this experiment. Returns a net error code.
+  int DeleteData(const CompletionCallback& callback);
+
+  // Removes requests between |initial_time| and |end_time|.
+  int DeleteDataBetween(base::Time initial_time,
+                        base::Time end_time,
+                        const CompletionCallback& callback);
+
+  // Returns the number of elements currently tracked.
+  int QueryItemsForTest(const CompletionCallback& callback);
+
+  // Flush the data to disk, preventing flushing when the destructor runs.

[gavinp, 2012/09/13 04:45:43]

Document what happens if we add more data after calling this, then call the
destructor.

+  int FlushDataForTest(const CompletionCallback& callback);
+
+ private:
+  class Worker;
+  friend class base::RepeatingTimer<InfiniteCache>;
+  friend class InfiniteCacheTransaction;
+
+  std::string GenerateKey(const HttpRequestInfo* request);
+  void ProcessResource(scoped_ptr<InfiniteCacheTransaction::ResourceData> data);
+  void OnTimer();
+
+  scoped_refptr<Worker> worker_;
+  scoped_refptr<base::SequencedWorkerPool> worker_pool_;
+  scoped_refptr<base::SequencedTaskRunner> task_runner_;
+  base::RepeatingTimer<InfiniteCache> timer_;
+
+  DISALLOW_COPY_AND_ASSIGN(InfiniteCache);
+};
+
+}  // namespace net
+
+#endif  // NET_HTTP_INFINITE_CACHE_H_
Property changes on: net\http\infinite_cache.h
___________________________________________________________________
Added: svn:eol-style
   + LF