Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: news.software.b
Subject: Re: Dynamic "smart" expiration?
Keywords: expire,C news
Message-ID: <1989Dec28.171830.13130@smsc.sony.com>
Date: 28 Dec 89 17:18:30 GMT
References: <1989Dec27.033817.9953@smsc.sony.com> <1989Dec28.063932.13720@robohack.UUCP>
Reply-To: dce@Sony.COM (David Elliott)
Organization: Sony Microsystems Corp.
Lines: 23

In article <1989Dec28.063932.13720@robohack.UUCP> woods@robohack.UUCP (Greg A. Woods) writes:
>I would rather still have expire do the expiring, rather than rnews.
>This allows more flexibility, not to mention archive support, etc.  I
>would definitely not want relaynews to do expiring too!

Actually, I was thinking more in terms of having newsrun doing the
expiring as part of its loop.

The big problem as I see it is that expire is slow (at least the B
news version was), especially if you start adding special heuristics
based on usefulness and group size and file age and number of
subscribers and so forth.

If expire generated a list of files to expire once a day, you could
still archive the files, and maintain flexibility, but when it's time
for them to go to make room for other files, it's easy and fast,
and until that time comes, they're still available.

-- 
David Elliott
dce@smsc.sony.com | ...!{uunet,mips}!sonyusa!dce
(408)944-4073
"But Pee Wee... I don't wanna be the baby!"