diff options
| author | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-09-30 01:49:16 +0000 |
|---|---|---|
| committer | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-09-30 01:49:16 +0000 |
| commit | c7b7610da317994ddbf52676be965f9a486f582a (patch) | |
| tree | 6d920eb2024396fcc411de2349e0cc6ddf3c6546 /net/proxy | |
| parent | 96d0436cf47503e14d3e57c681eb2853ba13ce5a (diff) | |
| download | chromium_src-c7b7610da317994ddbf52676be965f9a486f582a.zip chromium_src-c7b7610da317994ddbf52676be965f9a486f582a.tar.gz chromium_src-c7b7610da317994ddbf52676be965f9a486f582a.tar.bz2 | |
This causes the sync notifier in integration tests to broadcast notifications
to all clients, including themselves. The effect of this is that, following a
commit, the client will receive notification that updates are available (even
if those updates are its own) then enter a sync cycle to download them. This
means that their progress markers will be in kept in sync with the servers'
latest.
For an explanation of why this is a good thing, see crbug.com/97780 and read
through the related issues.
There are several unit tests that check if the notification filtering is
working. In order to not break those test, the notifier in the unit tests is
constructed to broadcast notifications to others only.
BUG=97780
TEST=sync_integration_tests,sync_unit_tests
Review URL: http://codereview.chromium.org/8002031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103401 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/proxy')
0 files changed, 0 insertions, 0 deletions