Re: [PATCH] Two issues with the gnus-registry

[Ted Zlatanov <tzz@lifelogs.com>]

On Sat, 08 Nov 2014 16:39:48 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote: 

EA> So unless I'm really missing something, my proposal is:

EA> 1. Only provide one limit: max-size.
EA> 2. Allow customization of prune-factor.

EA> That seems like all the customization you'd need. Cap the size, and
EA> provide a reasonable control of how often the registry gets pruned.

OK. I am afraid I made the whole thing too complicated and it took
another set of eyes to recognize it.  Thanks for that, and the fixes.

Please go ahead and apply any changes you have in mind. I am sure no one
is tuning soft/hard pruning. Simpler is definitely better.

EA> That would require a change in the object signature, which would mean
EA> some extra handling code for "upgrading". But once we're doing that, we
EA> could also take the opportunity to add :prune-function and
EA> :sort-function slots on the base registry object, which would be
EA> nice. We could even change the default store filename from its "eioio"
EA> extension to "eieio". :)

Yeah, I remember that bug report about the extension of the database
file, if we're upgrading anyway... It's a good chance to batch these
changes.

Ted