digestcache

[Kostas Chatzikokolakis]

Chris Anderson wrote:
> Oh, I forgot to ask the question which made me notice that in the first
> place: Anyone have any thoughts on whether it would be okay/recommended
> to use the same DigestCache for multiple sources? Since the keys are
> prefixed with the source name it doesn't seem there wouldn't be any
> collisions.

It seems harmless to me, as long as you don't change the 'path' of your
sources. On the other hand I don't see any benefit from it.

Btw one of the little annoying things is that brackup by default backs
up the digest db file which wastes space and time. It would be nice to
have ignore=.brackup-digest.db in the default config file.

Kostas



> 
> cva
> 
> On Sun, Jan 17, 2010 at 5:10 PM, Chris Anderson <cva at pobox.com
> <mailto:cva at pobox.com>> wrote:
> 
>     I just noticed that in rev 283, the following was added to the docs
>     for Brackup::DigestCache:
> 
>            Having said that, the digest cache is actually pretty
>     important when
>            using encryption. If you lose the cache all your files will
>     need to be
>            re-read, re-encrypted, and reloaded to the target, and will
>     result in
>            duplicate storage of all your data, as Brackup can't tell if
>     the data
>            already exists, because encryption makes different files each
>     time.  So
>            do look after it. :-)
> 
>     As far as I can tell, this isn't true (though it is for the
>     InventoryDatabase). Am I missing someting?
> 
>     cva
> 
>