From: Russ Allbery (rra@stanford.edu)
Date: Thu Mar 02 2000 - 17:15:34 CST
Charles Lindsey <chl@clw.cs.man.ac.uk> writes:
> The intended implementation is that you leave the old one in the history
> file (Expires will eventually remove it) and add a new one at the
> end. You then ensure that dbz always gives you the latest one. I looked
> at the dbz in CNEWS, and that seemed easily implementable, so I suppose
> the same would go for INN. We discussed this at length some months
> ago. Is there any real problem there?
It's certainly not simple. In INN, like most current news servers, the
keys to the history database are not message IDs; they're hashed forms of
message IDs. The actual message ID isn't stored anywhere in history in
current INN. So you'd need to use an extra external database to do the
version number mappings for Replaces.
I'm not saying it's not doable; it's just rather ugly.
-- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>