trn's threading
Richard <legalize-aS9lmoZGLiVWk0Htik3J/[email protected]> Wed, 03 May 2023 09:24:49 -0600
| Newsgroups | gmane.network.trn.general |
|---|---|
| Organization | multi-cellular, biological |
| Message-ID | <[email protected]> |
Hi Team,
So while doing a little sleuthing last night, I discovered that trn
has a bunch of support for an antiquated threading data mechanism.
rt-mt.cpp: mt_init() has XTHREAD and raw thread file support
<https://github.com/LegalizeAdulthood/trn/blob/cmake/rt-mt.cpp#L117>
They both obtain the same (binary) data, one via NNTP and the other
via a local file. XTHREAD is an old NNTP extension that delivers
threading information in a format specific to trn. The OVER command
obsoletes the XTHREAD and XOVER commands in NNTP as described in RFC
3977 (Oct-2006).
I'm going to drop the code that supports these binary thread files,
whether obtained through NNTP or via local files. My local news
server doesn't support XTHREAD, but I still have threading in trn, so
it must be getting thread information via XOVER in rt-ov.cpp.
I will switch the code to use the standard OVER command at some point.
First I need to add an "NNTP conversation" test harness mechanism to
be able to cover the existing NNTP implementation with tests before
making changes.
Cheers,
-- Richard
--
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
The Terminals Wiki <http://terminals-wiki.org>
The Computer Graphics Museum <http://ComputerGraphicsMuseum.org>
Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>