diff options
| author | paulg@google.com <paulg@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-10-09 21:31:57 +0000 |
|---|---|---|
| committer | paulg@google.com <paulg@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-10-09 21:31:57 +0000 |
| commit | 445d4cc80e88320e4bd86068c100520c9025fc63 (patch) | |
| tree | 3d4fc71e16627dbd23be957651d5bb412b4440cc /webkit/glue/webcursor.cc | |
| parent | 28f180ecca4fda508a0f7b6c512051012d2036df (diff) | |
| download | chromium_src-445d4cc80e88320e4bd86068c100520c9025fc63.zip chromium_src-445d4cc80e88320e4bd86068c100520c9025fc63.tar.gz chromium_src-445d4cc80e88320e4bd86068c100520c9025fc63.tar.bz2 | |
Support zero size chunks in the current implementation.
This allows the SafeBrowsing servers to send us Add and Sub
chunks with no content so that when we report our update
status, the request size is decreased.
Our update status request contains a list of all chunks that
we have received from the service, and this can get fragmented
over time. For example, the part of the request containing our
phishing chunks might look like this:
goog-phish-shavar:a:1,3,5,7,9,11,13,15,17
By sending zero size chunks for the chunk numbers missing from
the above example, the report will now look like:
goog-phish-shavar:a:1-17
Given the large number of chunks and the rate of chunk expiry,
this change will reduce the client request size.
BUG= http://code.google.com/p/chromium/issues/detail?id=3262
Review URL: http://codereview.chromium.org/6369
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@3131 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/glue/webcursor.cc')
0 files changed, 0 insertions, 0 deletions