RAPPOR implementation

components/rappor/proto/rappor_metric.proto

 // 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.
 //
 // Stores information about an event that occurs in response to a user action,
 // e.g. an interaction with a browser UI element.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
-package metrics;
+package rappor;
 
 // Next tag: 3

[jwd, 2013/12/17 23:00:25]

Update next tag, maybe drop it.

[Steven Holte, 2013/12/18 23:38:49]

Done.

-message UserActionEventProto {
-  // The name of the action, hashed.
+message RapporMetricsProto {
+message RapporMetricProto {

[jwd, 2013/12/17 23:00:25]

indent inner message.

Do these have to be named *Proto? Is there a naming convention for this? At
least the inner one could drop it.

[Steven Holte, 2013/12/18 02:06:12]

I had included it in the name because UserActionEventProto did.  I don't know if
there are better conventions to follow.  I've dropped it from the inner message,
and I'm open to suggestions for message names.

+  // 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
+  optional bytes bits = 2;
 }
+  repeated RapporMetricProto rappor = 1;
+}