Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!hp4nl!philapd!ssp15!jos
From: jos@idca.tds.PHILIPS.nl (Jos Vos)
Newsgroups: comp.sources.d
Subject: Re: A few questions/comments on Rkive
Keywords: long rkive archive sources USENET
Message-ID: <1141@ssp15.idca.tds.philips.nl>
Date: 12 Jul 89 11:53:36 GMT
References: <1123@ssp15.idca.tds.philips.nl> <520@ssbell.UUCP> <1129@ssp15.idca.tds.philips.nl> <521@ssbell.UUCP>
Organization: Philips Telecommunication and Data Systems, The Netherlands
Lines: 28

In article <521@ssbell.UUCP> kent@ssbell.UUCP (ssbell Admin) writes:

>The problem does not occur with the Chronological archiving. As for the
>.archived file, it is used to indicate what the status is of the articles
>currently on the system waiting to be expired. ...

A more general way of registrating the archived articles is the
combination of the Message-Id and the Posting-Date.
That's quite unique *forever*, I hope :-)
(Any other suggestions are welcome, but I couldn't find something else).

Then crosspostings, feeding via stdin etc. are then quite easy to
handle. If you divide your databases into parts (e.g. a file
89 for a full year's database, or 8901, 8902, ... for monthly databases)
according to the posting dates you can easy check whether an article
is already archived in the stone age (i.e. before 1-1-1970 :-) ).

At expire time, it's still possible (if you want that) to 
minimize the database file(s) according to the expired articles.
If you don't want it, you'll get a real usefull history.

I'll work in out in more detail (I think I need it anyway and I
probably will implement it for my own private use) and post it.
Then you and The NET can decide what to do with it.

-- 
-- ######   Jos Vos   ######   Internet   jos@idca.tds.philips.nl   ######
-- ######             ######   UUCP         ...!mcvax!philapd!jos   ######