| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
Sat 2002-11-02 07:35, Jasen Betts (3:640/531.42) wrote to andrew clarke:
>>> Human-readable (HR) distribution nodelist
ac>> I'm not much of a documentation-writer, but I've tried to describe
ac>> the format I'm proposing. If people think they can rewrite a
ac>> paragraph here and there so it makes more sense, or some changes
ac>> in the file format, do so and send me the changes.
> did you see what I was proposing a few months back.
I'm afraid I wasn't in FidoNet a few months back. I left in January 1999
and have only returned in the last couple of weeks. So if you want to
repost your proposal, I'll have a look.
> Mainly leting a node have multiple addresses (since many do) and thus
> saving repeating the same node with the same connection info and thus
> make the nodelist easier to maintain?
I don't see any reason why a single node shouldn't be able to have multiple
connection methods listed in a new format nodelist. I don't see how the
alternative could be easier to maintain. Sounds like it could only add
more complexity to people's routing and system configs.
> also a way is needed to translate thesenew lists to old-style (possibly
> by reformatting and selectively dropping information) for se with
> existing software...
The program I wrote, rnlcvt, does just that.
-- mail{at}ozzmosis.com
--- Msged/NT 6.1.1
* Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267)SEEN-BY: 106/2000 201/100 148 209 329 505 204/450 206/0 490/21 633/267 270 @PATH: 633/267 285 260 774/605 123/500 106/2000 201/505 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.