Subject:
|
Re: Message-ID -> Article number
|
Newsgroups:
|
lugnet.admin.nntp
|
Date:
|
Tue, 19 Dec 2000 07:46:06 GMT
|
Viewed:
|
115 times
|
| |
|
|
"Todd Lehman" <lehman@javanet.com> writes:
> I would really hate to see NNTP Message ID's floating around in HTTP URLs.
I wonder why.
> A workaround is simply to use a standardized NNTP URL format -- for example:
>
> news://lugnet.com/qrd1yv57q2n.fsf@eos.uio.no
Great, I'll do that!
> Or, if you want to convert that to an HTTP URL, it's as easy as looking at
> the Xref header on the message served directly from the NNTP server
When I read LUGNET offline at home, the Xref header has the article
number on my local news spool. I don't think that number would be too
interesting for anybody else.
Fredrik
|
|
Message has 1 Reply:
 | | Re: Message-ID -> Article number
|
| (...) 1) They're gunky looking. 2) They contain no useful information to a human. 3) They can be very, very long. I've seen some here bigger than 80 characters in length. That makes them unsuitable for URLs. 4) The thought of putting NNTP ID's in an (...) (24 years ago, 19-Dec-00, to lugnet.admin.nntp)
|
Message is in Reply To:
| | Re: Message-ID -> Article number
|
| [redirecting to .admin.nntp] (...) I would really hate to see NNTP Message ID's floating around in HTTP URLs. A workaround is simply to use a standardized NNTP URL format -- for example: news://lugnet.com/qr...eos.uio.no That's postable as-is. Or, (...) (24 years ago, 18-Dec-00, to lugnet.admin.general, lugnet.admin.nntp)
|
10 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
