Re: [Gnu-arch-users] Re: [BUG] FEATURE PLANS: "perfect" summary deltas

[Tom Lord]

    > From: Aaron Bentley <address@hidden>

    > Okay, I underspecified.  I meant that LIST-DELTAS would have two 
    > arguments: FROM and TO.  A bushy-tailed smart server would offer reply 
    > that it would provide delta-FROM-TO.  An overloaded one might return a 
    > series of deltas that were related to TO.  A dumb server would just 
    > return a directory listing of the delta dircectory for the TO version.

And if FROM is not listed in that directory but many others
are... what then?   Give up?  Search?

A deterministic summary policy (the summary trees are just one
possible policy) answers that question.


    > To go all the way, you might specify that the FROM field should be every 
    > revision of every version in the library.  The smart server could then 
    > determine which delta would serve the greatest number.

    > For a smart server that only generates the deltas sometimes, the
    > caching should be fairly simple: for those deltas that it
    > generates, retain the most popular in cache, and dump the
    > unpopular.

which is fine but has nothing to do with the topic at hand.

Your caching ideas apply to many different ways of handling summary
deltas (including mine), not just the one you advocate for.

-t