RAPPOR implementation

components/rappor/rappor_pref_names.h

Index: components/rappor/rappor_pref_names.h
diff --git a/components/rappor/rappor_pref_names.h b/components/rappor/rappor_pref_names.h
new file mode 100644
index 0000000000000000000000000000000000000000..5129f5787ce29f0ca1f1b03a52c2e8f4f2f85046
--- /dev/null
+++ b/components/rappor/rappor_pref_names.h
@@ -0,0 +1,18 @@
+// Copyright 2013 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.
+
+#ifndef COMPONENTS_RAPPOR_RAPPOR_PREF_NAMES_H_
+#define COMPONENTS_RAPPOR_RAPPOR_PREF_NAMES_H_
+
+namespace rappor {
+namespace prefs {
+
+// Alphabetical list of preference names specific to the Rappor
+// component. Keep alphabetized, and document each in the .cc file.
+extern const char kRapporSecret[];

[Alexei Svitkine (slow), 2013/12/19 19:47:02]

I'm not sure there's precedent for having prefs inside components.

If there isn't, these can still be in chrome/ and passed as parameters to the
ctor of the RapporService.

[Steven Holte, 2013/12/20 03:03:55]

See ./autofill/core/common/autofill_pref_names.h and
./policy/core/common/policy_pref_names.h.  It seems like a pretty reasonable
convention.

+
+}  // namespace prefs
+}  // namespace rappor
+
+#endif  // COMPONENTS_RAPPOR_RAPPOR_PREF_NAMES_H_