Re: RFC 1036 Revision: Replaces/Supersedes/Xref Headers

New Message Reply About this list Date view Thread view Subject view Author view

From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Fri Mar 03 2000 - 06:39:58 CST


In <20000302174159.C6930@main.templetons.com> Brad Templeton <brad@templetons.com> writes:

>I was beginning to believe that by defining the xref requirement you even
>wanted to forbid replace-in-place. I'm fine with the system having the
>option of either.

Well you have to be careful that all newsreaders will work with all
servers (or all NNTP servers in practice). I have not thought through
whether your method runs into any problem there.

It is certainly the case, with the system as currently envisaged, that
users will not see the benefit of the new feature until BOTH their local
server and their own newsreader have implemented it. Servers that
implement your form may well enable old newsreaders to see the new
functionality. But yours is a bigger upheaval to the server
implementation.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Email:     chl@clw.cs.man.ac.uk  Web:   http://www.cs.man.ac.uk/~chl
Voice/Fax: +44 161 437 4506      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9     Fingerprint: 73 6D C2 51 93 A0 01 E7  65 E8 64 7E 14 A4 AB A5


New Message Reply About this list Date view Thread view Subject view Author view


This archive was generated by hypermail 2b29.