Linked by Thom Holwerda on Thu 16th Jul 2009 21:44 UTC
One of the more controversial features of Google's Chrome/Chromium web browser is the way it handles updates. Contrary to other browsers, updates on Chrome are installed silently and automatically, without asking for the user's consent. While convenient and effective, it was also a security risk and sometimes it slowed people's machines down. Google now proposes a fix called Courgette.
Permalink for comment 373830
To read all comments associated with this story, please click here.
From what I understand, this isn't particularly new - Linux and Windows have delta updates which are binary diffs; I remember Microsoft before Microsoft developed a technology to reduce the size of updates; where a 1MB update might have a 500K file which is only around 30K difference between the old and new file.
Here's the relevant info from MS' Binary Delta Compression reference:
The Delta Compression API offers special handling for certain types of executable files (PE files, such as EXE or DLL files.) In particular, executables designed to run on the 32-bit Intel i386 family get special treatment. When the basis and target files are similar executables, this feature can reduce the size of the delta significantly—typically 50-70% further.
To get the maximum benefit from this feature, symbol files from the LINK process can be supplied during delta creation. This will help the creation process recognize the nature of the changes between the files. Richer symbol info, such as private symbols, will help make smaller deltas. Figure 3 illustrates this process.
Figure 3. Delta compression using symbol files
None of the symbol data is passed in the delta, and the symbol files are not needed during the delta apply process.
See Optional Data for Delta Create for more information on how symbols can be provided.
Member since:
2005-07-06
Here's the relevant info from MS' Binary Delta Compression reference:
To get the maximum benefit from this feature, symbol files from the LINK process can be supplied during delta creation. This will help the creation process recognize the nature of the changes between the files. Richer symbol info, such as private symbols, will help make smaller deltas. Figure 3 illustrates this process.
Figure 3. Delta compression using symbol files
None of the symbol data is passed in the delta, and the symbol files are not needed during the delta apply process.
See Optional Data for Delta Create for more information on how symbols can be provided.
http://msdn.microsoft.com/en-us/library/ms811406.aspx