diff options
| author | petewil@chromium.org <petewil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-06 01:18:41 +0000 |
|---|---|---|
| committer | petewil@chromium.org <petewil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-06 01:18:41 +0000 |
| commit | c2676078e784f94efbca4442928450108d592f42 (patch) | |
| tree | 3a76d99e94fd3d3becc7eccef748cf02be38e6fa /tools/code_coverage/coverage_posix.py | |
| parent | 1cd427c1a462ceebc270583c8c5dbd51dca25a73 (diff) | |
| download | chromium_src-c2676078e784f94efbca4442928450108d592f42.zip chromium_src-c2676078e784f94efbca4442928450108d592f42.tar.gz chromium_src-c2676078e784f94efbca4442928450108d592f42.tar.bz2 | |
Turn off Synced Notifications at display level instead of network level.
To allow load testing of Synced Notifications as we ramp up, clients must
actually ask for the synced datatype even before we turn the feature on.
This change allows the network traffic of Synced Notifications even to machines
where the user has not yet turned on Synced Notifications. The notifications
are discarded before displaying them, so there is no user-visible impact to
this change. This change does mean that the Synced Notifications code will be
exercised even when it has not been enabled specifically by the user.
The intent here is to allow this to be in the code for one milestone so that we
can slowly ramp up the white list before enabling the feature in the following
milestone. When we enable the feature, we will remove the switch or undo this
change list.
Without this feature, we have no way to load test until the feature ships in the
wild, and we would just have to hope that we had fixed all the bugs and have the
capacity for launch.
BUG=267782
Review URL: https://chromiumcodereview.appspot.com/21950006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215754 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/code_coverage/coverage_posix.py')
0 files changed, 0 insertions, 0 deletions