Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!tektronix!uw-beaver!cornell!vax135!ariel!houti!hogpc!houxm!ihnp4!ixn5c!inuxc!pur-ee!uiucdcs!uiuccsb!essick
From: essick@uiuccsb.UUCP
Newsgroups: net.news
Subject: Re: How to stop a followup - (nf)
Message-ID: <2769@uiucdcs.UUCP>
Date: Fri, 9-Sep-83 22:34:36 EDT
Article-I.D.: uiucdcs.2769
Posted: Fri Sep  9 22:34:36 1983
Date-Received: Wed, 14-Sep-83 21:33:07 EDT
Lines: 23

#R:utcsrgv:-219000:uiuccsb:3400002:000:944
uiuccsb!essick    Sep  9 10:10:00 1983

	One way to solve the problem of aborting followups
(and articles in general) is to not queue them for submission
to remote sites immediately.  When combined with the ability
for a user to delete his notes (on the local machine, not
necessarily remote copies) it handles 99% or better of the
cases where people want to delete something.

	Now that batching articles to send to a remote site
is vogue, a scheme similar to what I use for notesfiles can
be used quite effectively.

	Here at Illinois, a user is allowed to edit and/or delete
his articles any time before they are queued for transmission.
The queueing daemon runs every other hour. This leaves an
average of 1 hour for a user to discover that he didn't
really want to post something, he misspelled words in his article
or that he forgot to sign the article.  This catches a large
percentage of the cases where people want to delete something.

-- Ray Essick, University of Illinois