Re:Apple not providing LGPL webkit source code for latest iO...
by mentat on Friday May 06, 2011 @06:37PM
(#2522735)
This can easily be automated. You could send a hash of the binary and have a custom patch either pulled from cache or created (the largest "patch" being the whole binary). You'd end up with a fairly complete cache very fast though. Binary diffing is a mostly solved problem. This assumes that there's a list of hashes that correlate to known historical binaries. If the hash doesn't match you fall back to sending the whole thing.
Re:Apple not providing LGPL webkit source code for latest iO...
by ori_b on Friday May 06, 2011 @05:21PM
(#2522530)
we have a way to detect if it's broken.
Do it by checksum. If the checksums don't match, then redownload the changed parts. This is also fully predictable, but it's also far faster.
Re:Apple not providing LGPL webkit source code for latest iO...
by drivebyacct2 on Saturday May 07, 2011 @03:20AM
(#2523354)
> "well if this smaller update didn't work in any of a huge variety of ways, you could optionally try this other update"
Not once has Chrome botched itself during an incremental upgrade of itself.
I suspect Apple prefers the simplicity and explainability of "here's the update, same thing for everyone" to "well if this smaller update didn't work in any of a huge variety of ways, you could optionally try this other update"