[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lines count in USEFOR
Hi Russ,
NNTP as presently written cannot transfer an article that does not end in
a CRLF. In practice, clients will just add a CRLF to any article that
doesn't already end in one, since otherwise they can't POST.
Ah yes, that final CRLF is not added by me but by my posting agent.
The Lines header field indicates the number of lines in the <body>
(as defined in [RFC5322]) of the article.
body = (*(*998text CRLF) *998text) / obs-body
Then USEFOR uses a subset of the e-mail body. And the definition of
the Lines: header is right for that subset but wrong in the general case
(which may be possible in an NNTP extension).
The second part of the paragraph seems unclear. I am under the
impression that RFC 3977 says we can use Lines: in the overview but
USEFOR -- posterior to RFC 3977 -- deprecates that use. This header
field is not used by OVER in RFC 3977.
RFC 3977 says that you can *call* the :lines metadata element Lines:, but
it's still the metadata element. Per RFC 3977, the Lines header is no
longer used to provide the basic overview information. I think that's
what's referred to here.
The impression I said I had was when I read "Historically, this header
field was used by the NNTP [RFC3977] overview facility, but its use for
this purpose is now deprecated.".
It looked to me, when reading that sentence, that this header could still
be stored in the overview defined by RFC 3977. Which is not the case
in OVER answers.
As you explained, the sentence hints at LIST OVERVIEW.FMT.
Yet, something seems to be wrong: "this header field"? Shouldn't it
be "this header name"? Because the value is never used. (Otherwise,
its use for this purpose cannot be "deprecated" because we can no longer
retrieve the value -- it would be an unsupported feature, which is
different than deprecated.)
--
Julien ÉLIE
« There's a way of transferring funds that is even faster
than electronic banking. It's called marriage. » (Sam Kinison)