What about server-side? Either the server or the client needs to do a binary/rpm diff. If it's the client, that really doesn't cut down on bandwidth because the client would have to d/l the new package to diff it against the old one (and if it didn't have the old one, d/l it too). I'm not too familiar with the possibility of a distributed diff, where the server does it's thing and reports back to the client so it can make the final comparison and request the difference. Another possibility is to store the diff between a couple of versions, e.g. from foo-1.0 to foo-1.5, foo-1.1 to foo-1.5...foo-1.4 to foo-1.5. While it would take more HDD space, it is far cheaper (logistically, possibly monetarily) than the bandwidth. -- Timothy Selivanow On 4/4/07, Rahul Sundaram <sundaram@xxxxxxxxxxxxxxxxx> wrote:
Kam Leo wrote: > Good in theory, not so stellar in practice. Delta rpms use less > bandwidth (good for those on slow connections) but require more > processor horsepower (Yast online updater is the metric I'm using for > reference). On my old system which has an AMD K6-2 450 MHz it takes > much longer to update using openSUSE 10.2's Yast. I hope FC7's > implementation is better. You would have to test and report back rather than hope. Yum-presto 0.3.4 uses parallel threads for building the full update from the delta's. Raul -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
