The infamous to-do list
rra at stanford.edu
Sun Jun 25 06:57:51 UTC 2000
Don Lewis <Don.Lewis at tsc.tdk.com> writes:
> On Jun 24, 3:09am, Russ Allbery wrote:
> } * When articles expire out of a storage method with self-expire
> } functionality, the overview and history entries for those articles
> } should also be expired immediately. Otherwise, things like the GROUP
> } command don't give the correct results. This will likely require a
> } callback that can be passed to CNFS that is called to do the overview
> } and history cleanup for each article overwritten. It will also require
> } the new history API.
> They shouldn't be totally removed from history, otherwise we might
> accept them again, particularly for groups that rapidly self-expire.
Right, they change state to the trash entry and stick around for the
/remember/ time frame.
> It would be nice to tie the incoming and outcoming feed information.
> Combined with some enhancements to the WIP cache it would allow us to
> avoid offering articles back to feeds that have offered it to us.
> Currently if we get an CHECK from host A, a CHECK from host B, and a
> TAKETHIS from host A we will offer that article to host B.
Hm. Yeah, this has been mentioned before in news.software.nntp
discussions; it's generally agreed to be fairly hard to do this right, but
it's not a bad idea.
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the inn-workers