Add a mechanism to scramble Mojo message IDs.

For example, chrome/common/renderer_configuration.mojom defines:

interface RendererConfiguration {
  SetInitialConfiguration(etc);
  SetContentSettingRules(etc);
  SetFieldTrialGroup(etc);
};

The generated IDs in
gen/chrome/common/renderer_configuration.mojom-shared-internal.h, prior
to this CL, and also after this CL with an empty seed, are:

constexpr uint32_t kRendererConfiguration_SetInitialConfiguration_Name = 0;
constexpr uint32_t kRendererConfiguration_SetContentSettingRules_Name = 1;
constexpr uint32_t kRendererConfiguration_SetFieldTrialGroup_Name = 2;

After this CL, with a "foo" seed, the IDs are:

constexpr uint32_t kRendererConfiguration_SetInitialConfiguration_Name = 1257880741;
constexpr uint32_t kRendererConfiguration_SetContentSettingRules_Name = 631133653;
constexpr uint32_t kRendererConfiguration_SetFieldTrialGroup_Name = 549336076;

BUG=673417

Review-Url: https://codereview.chromium.org/2794743002
Cr-Commit-Position: refs/heads/master@{#467573}


CrOS-Libchrome-Original-Commit: 9c12ed217b0f67085d1ec83ab3eabdabe72c40da
3 files changed
tree: 8fee51415a68b87d2284f36aa1129ac02dac1ccf
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/