NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/bbs/waffle/4345

Internet Message Format | 1992-11-20 | 1.9 KB

Path: sparky!uunet!elroy.jpl.nasa.gov!swrinde!emory!uumind!willard!dawson
From: [e-mail]
Newsgroups: comp.bbs.waffle
Subject: Re: News/mail reader
Message-ID: <[e-mail]>
Date: Thu, 19 Nov 92 21:09:46 EST
References: <[e-mail]>
Organization: Willard's House BBS, Atlanta, GA -- [phone]
Lines: 32

[e-mail] (Bill Fenner) writes:

> In article <[e-mail]> [e-mail]
> |The proper solution to the join file reset problem is to fix Waffle!  What
> |ought to occur, on the occasion that a user's join file indicates an article
> |higher than is available, is that Waffle ought to reset the join file line
> |to the highest numbered article in the group, such that that article is
> |lower-numbered than the previous entry in the join file.
>
> So when you delete all the messages in a newsgroup, and 100 articles come
> in, you think that the person who had read up to 1032 should have his JOIN
> pointer set to 100, so that he misses 99 new articles?  Or 0, so he gets to
> read all 100 new messages?...
>
>   Bill

Hmmm.. I must admit, I seem to have leapt in (as fools so often do).

Suppose Waffle/expire were to mark a <status> file indicating the date/time
for which article 1 was written to a directory.  If the newsreader program
were to check the contents of such a file, the reader would know whether to
reset its indicator back to 0 prior to reading... but that's not what rn or
new or nwreader or.. do, is it?  Neither is it what any of the expiration
programs do, is it?  Certainly, it's not what Waffle does... but it might
work, eh?  If that was the method, then resetting back to the highest
numbered message would work, I believe.

--
[e-mail] (Willard Dawson)
gatech!vdbsan!willard!dawson
emory!slammer!willard!dawson
Willard's House BBS, Atlanta, GA -- [phone]