LevelDB storage for data reduction proxy to store data usage stats.

components/data_reduction_proxy/proto/store.proto

Index: components/data_reduction_proxy/proto/store.proto
diff --git a/components/data_reduction_proxy/proto/store.proto b/components/data_reduction_proxy/proto/store.proto
new file mode 100644
index 0000000000000000000000000000000000000000..1ac3a98cbab6531dc80cc825dac7d2de1ab81dd4
--- /dev/null
+++ b/components/data_reduction_proxy/proto/store.proto
@@ -0,0 +1,24 @@
+// Copyright 2015 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.
+//
+// Protocol buffer definitions for Data Reduction Proxy data stored in LevelDB.
+
+syntax = "proto2";
+
+option optimize_for = LITE_RUNTIME;
+
+package data_reduction_proxy;
+
+// Contains data usage for an interval of time.

[jeremyim, 2015/06/30 01:59:19]

Does it make sense for a bucket to contain it's time information? That would
allow the values to be changed in the future.

[Not at Google. Contact bengr, 2015/07/01 17:13:49]

You can use last_updated_timestamp to compute the time range.

[jeremyim, 2015/07/01 21:31:01]

The only issue is that a computed time range depends on the computation params
which are hard coded (i.e. if the bucket contained its own time range, the
params in code could change).

[Not at Google. Contact bengr, 2015/07/01 23:17:37]

We spent some time debating the smallest bucket size so don't expect this to
change.

We should be able to fields in case this changes and still be backwards
compatible.

+message DataUsageBucket {

[jeremyim, 2015/06/30 01:59:19]

What happened to tag 1?

[Not at Google. Contact bengr, 2015/07/01 17:13:49]

Fixed.

+  repeated PerSiteDataUsage site_usage = 2;
+  optional int64 last_updated_timestamp = 3;
+}
+
+// Data usage for a specific site.
+message PerSiteDataUsage {
+  required string site_url = 1;
+  required int64 original_content_length = 2;
+  required int64 content_length = 3;
+}