Aging tokens to keep database size within bounds

[Matthias Andree]

Yusuf Goolamabbas <yusufg at outblaze.com> writes:

> Hi, I haven't thought this over fully as yet so be kind if there are
> obvious flaws
>
> For deploying bogofilter into a site-wide mechanism, one has to factor
> in the size of a per-user goodlist/badlist Berkeley DB. Would it make
> sense to incorporate some form of aging to the token/count list so that
> the database size were kept bounded to some configurable limit

Do you think of a LRU (least recently used) expire strategy?

-- 
Matthias Andree