INN -BETA expire vs. traditional spool
kondou at nec.co.jp
Thu Jun 29 16:43:17 UTC 2000
In article <ylg0pxp8ft.fsf at windlord.stanford.edu>,
Russ Allbery <rra at stanford.edu> wrote;
} So what I think should happen here is that the guts of OVgroupbasedexpire
} should become dependent on the storage method, and that the tradspool code
} should look significantly different than the code for the other storage
} methods (namely expiring the article independently out of each of the
} newsgroups to which it was posted, based on the overview information, and
} generating file names for the fastrm file rather than storage API tokens).
This breaks SMretrieve(), since the token of tradspool
represents 1st file in Xref. Imagine a case, an article
is crossposted to test.a and test.b and spooled to
test/a/1 and test/b/1. Its token represents test/a/1.
If test/a/1 is unlink but test/b/1 remains, you will
never read it thru storageapi.
More information about the inn-workers