🚀 go-pugleaf

In <1990Aug5.075054.11185@zoo.toronto.edu>, I asked about policy relating
to the Lines header field. Fortunately, my question didn't spark a flame
war and the responses (both postings and e-mail) fell into three
categories: policy, personal preference and solutions.

The policy seems to be clear. Lines is an optional field and if it is to
be included, it should be supplied by the posting agent. Henry Spencer
pointed out that B News does this and C News doesn't. He contended that
the field was unnecessarily wasteful. Interestingly, his article had a
Lines field.

On reflection, I believe that Henry's rationale makes sense. Assuming
articles have on average N lines (where 10 < N < 100), the field would
require strlen("Lines: 99\n") (ie 10) characters. Multiply this by the
number of articles received and stored each day and we're looking at a
small but significant volume of data.

As an aside, C News article IDs are more than 10 characters longer than
their B News counterparts (on most installations). Thus, the size of a
C News header is larger than a similar B News header. :-)

Responses in the personal preference category related to the user
interface of the reading agent. Henry Spencer suggested that character
counts were a better article size metric because they could be cheaply
determined by the reading agent. An alternative view was advanced by
Bill Wisner (et al) who suggested that line counts were easier to
comprehend than character counts.

Several people told me how to turn on the Lines computation in C News.
Thanks, but I had already Read The Fine Sources.

From all this I conclude that article size computation (in whatever
form) can be more efficiently determined by the reading agent. I will
modify the nn sources to implement this policy and will post the patches
to Kim Storm for possible inclusion in a future release.

cbp
-- 
cbp@foster.avid.oz - ACSnet
cbp%foster.avid.oz.au@uunet.uu.net - Internet
...!{hplabs,mcvax,nttlab,ukc,uunet}!munnari!foster.avid.oz.au!cbp - UUCP