RAPPOR implementation

components/rappor/proto/rappor_metric.proto

Index: components/rappor/proto/rappor_metric.proto
diff --git a/chrome/common/metrics/proto/user_action_event.proto b/components/rappor/proto/rappor_metric.proto
similarity index 58%
copy from chrome/common/metrics/proto/user_action_event.proto
copy to components/rappor/proto/rappor_metric.proto
index ff688b67b1b7a7ac9fe3c4c63e65c29acf83fe6b..14a5ac92ad84f8406b63d632c6851ddc82984cab 100644
--- a/chrome/common/metrics/proto/user_action_event.proto
+++ b/components/rappor/proto/rappor_metric.proto
@@ -9,13 +9,15 @@ syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
-package metrics;
+package rappor;
 
-// Next tag: 3
-message UserActionEventProto {
-  // The name of the action, hashed.
-  optional fixed64 name_hash = 1;
+message RapporMetricsProto {
+  message RapporMetric {
+    // The name of the metric, hashed.
+    optional fixed64 name_hash = 1;
 
-  // The timestamp for the event, in seconds since the epoch.
-  optional int64 time = 2;
+    // The reported bits for the event

[Ilya Sherman, 2014/01/10 11:00:32]

nit: This field is going to need considerably more documentation, especially
since it is an abritrarily-sized byte vector, which generally tends to make
people nervous unless they understand exactly what the restrictions on the
possible values for the byte vector are.

[Steven Holte, 2014/01/14 00:47:54]

Renamed messages, expanded the description, and added a link to the design doc.

+    optional bytes bits = 2;
+  }
+  repeated RapporMetric rappor = 1;
 }