home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!iadpsa!iowegia!kjhoule
- From: kjhoule@iowegia.uucp (Kevin Houle)
- Newsgroups: comp.bbs.waffle
- Subject: Re: News/mail reader
- Message-ID: <87iNuB4w165w@iowegia.uucp>
- Date: Sun, 22 Nov 92 11:45:54 CST
- References: <aoLiuB6w165w@willard.UUCP>
- Distribution: world
- Organization: Iowegia Public Access Usenet/UUCP, Clive IA USA.
- Lines: 33
-
- dawson@willard.UUCP writes:
-
- > Ok, let's have a counter example. Supposing files are sorted by creation
- > date/time (as would apparently be the case with your technique). Suppose
- > there were no new articles, and one was expired. The users' join files
- > are now out of sync:
- >
- > Before unbatching : 1, 2, 3, 4, 5
- > After unbatching : 1, 2, 3, 4
- >
- No, the expired article would be #1, and no resequencing would
- take place because 2-5 is contiguous.
-
- > Suppose there was one new article, and one was expired. No change to the
- > users' join files, but it now points one too high:
- >
- > Before unbatching : 1, 2, 3, 4, 5
- > After unbatching : 1, 2, 3, 4, 5
- Again, the expired article would be #1, and the new article would
- be #6. 2-6 is contiguous, no resequencing is done.
-
- > Too simple, maybe? I think I'll just avoid re-sequencing my articles.
- > How does re-sequencing enhance the general operation of Waffle?
-
- Too simple for use on a full news spool, most definately. It
- works fine for the purpose I wrote it for, which is to allow
- some network redundancy on two SMALL LOCAL news hierarchies.
- Resequencing simply keeps the article names contiguous, something
- I like to have. Doesn't 'enhance the general operation' of
- anything.
-
- --
- Kevin Houle kjhoule@iowegia.uucp
-