Re: ietf-nntp Issue: number range rollover
Jack De Winter <jack@wildbear.on.ca> Tue, 31 December 1996 21:17 UTC
Received: from cnri by ietf.org id aa17930; 31 Dec 96 16:17 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa18531;
31 Dec 96 16:17 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.4/8.7.3) id
PAA06398 for ietf-nntp-outgoing; Tue, 31 Dec 1996 15:10:29 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to
owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by
academ2.academ.com (8.8.4/8.7.3) with ESMTP id PAA06393 for
<ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 31 Dec 1996 15:10:26 -0600 (CST)
Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca
[199.246.132.198]) by academ.com (8.8.4/8.7.1) with ESMTP id PAA04730 for
<ietf-nntp@academ.com>; Tue, 31 Dec 1996 15:10:15 -0600 (CST)
Received: by lacroix.wildbear.on.ca from localhost
(router,SLMailNT V3.0); Tue, 31 Dec 1996 16:03:10 -0500
Received: by lacroix.wildbear.on.ca from wildside.wildbear.on.ca
(199.246.132.193::mail daemon,SLMailNT V3.0); Tue, 31 Dec 1996 16:03:09 -0500
Message-Id: <3.0.32.19961231160815.00d30c34@lacroix>
X-Sender: "Jack De Winter" <jack@wildbear.on.ca>
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 31 Dec 1996 16:08:17 -0500
To: chrisy@easynet.net, USENET news manager <newsmaster@ucs.cam.ac.uk>
From: Jack De Winter <jack@wildbear.on.ca>
Subject: Re: ietf-nntp Issue: number range rollover
Cc: clive@demon.net, ietf-nntp@academ.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
At 05:24 PM 12/31/96 GMT, chrisy@easynet.net wrote: >On Sat, 28 Dec 1996 22:49:00 +0000 (GMT), USENET news manager ><newsmaster@ucs.cam.ac.uk> wrote: > >>(1) If anyone's reading news via NFS or direct local spool access on the >>server (yes, it still happens!), the news server has no way of knowing >>when clients have stopped using the old numbers. >[etc] > >You should probably stipulate that "this is bad", or have some other >mechanism for indicating to file-based clients that the numbering has >changed. Readers are going to have to be adapted anyway... > >...so why not rewrite all the readers with an agreed maximum HWM and >rollover to 0 like a FIFO buffer. It's obvious when this is the case - >the HWM is less than the LWM. If IBM could code it into a 16kb PC BIOS >ROM for 16-byte buffered keyboard handling I'm sure you can implement >it with 32-bit numbers in a news system. No renumbering required [tm]. >It's all a question of the maximum HWM being agreed on. > >This then requires little other adaption of the existing systems, >server and client. This system would work if we went with the article numbering system of empty groups being first <= last, count = 0 approach. In that case, rollover could be detected as a special case and handled separately. It would work with the first = last + 1 approach, but possibly not as cleanly. regards, Jack ------------------------------------------------- Jack De Winter - Wildbear Consulting, Inc. (519) 576-3873 http://www.wildbear.on.ca/ Author of SLMail(95/NT) (http://www.seattlelab.com/) and other great products.
- Re: ietf-nntp Issue: number range rollover Jack De Winter