I think there's no doubt about the algorithm to be used -- vdelta, all
the way. The question was more what format to encode the algorithm's
results in (but that seems to be settled too, now).
-K
Brian Behlendorf <brian@collab.net> writes:
> I sent a message Sept. 19th about the HTTP delta-encoding mechanism being
> a draft standard at the IETF:
>
> http://www.ietf.org/internet-drafts/draft-mogul-http-delta-06.txt
>
> there's a paper written by three of the authors of the draft at
>
> http://www.research.digital.com/wrl/techreports/abstracts/97.4.html
>
> In it they cite some pretty impressive numbers for the savings that the
> vdelta algorithm can provide, even above compressed diff-e. Since it
> looks like they had to implement some vdelta-generating code to do so,
> anyone want to write the authors of the paper (or perhaps some of those
> thanked in the paper for their help on vdelta) to see if the code they
> wrote could be liberated?
>
> Brian
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> CollabNet | open source | do what's right | now hiring
Received on Sat Oct 21 14:36:10 2006