home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.gtech.com!noc.near.net!news.Brown.EDU!news.Brown.EDU!news
- From: Andrew Gilmartin <Andrew_Gilmartin@Brown.Edu>
- Newsgroups: comp.infosystems.gopher
- Subject: Re: Expiring information ???
- Date: 20 Nov 1992 17:59:42 GMT
- Organization: Computing & Information Services
- Lines: 30
- Distribution: world
- Message-ID: <1ej92eINN7cr@cat.cis.Brown.EDU>
- References: <1992Nov20.045322.29298@cc.uow.edu.au>
- NNTP-Posting-Host: cis_staff-kntx22.cis.brown.edu
- X-UserAgent: Nuntius v1.1.1d7
- X-XXDate: Fri, 20 Nov 92 18:06:02 GMT
-
- In article <1992Nov20.045322.29298@cc.uow.edu.au> Kirk,
- kirk@cc.uow.edu.au writes:
-
- >When this expiry time is reached the information is removed
- >and the owner of the files is notified by mail although the notification
- is
- >really only the icing on the cake.
-
- We are planning (and currently implementing) this here at Brown
- University. The plan is to extend the number of fields in a document's
- .cap file to include information for expiring. Fields added in part for
- expiration are Creation, Modification, Expiration, and Provider. Each
- night I have code that walks gopher space (from the disk side) looking
- for documents that are about to expire and those that have expired. Mail
- is sent to the document's provider when a document is about to expire or
- is expiring that night. Expired documents are moved to the .expired
- directory, and a stub is left telling the user community who to contact
- for a current version of the document.
-
- When I have a working system I will notify the group.
-
- -- Andrew
-
- --
- Andrew Gilmartin
- Computing & Information Services
- Brown University
-
- Andrew_Gilmartin@Brown.Edu
- (401) 863-7305
-