| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
Sun 2002-11-10 13:22, Rick Van Ruth (3:640/954) wrote to Scott Little:
RR>>> I had a look at the nodelist it generated, but sorry I don't agree
RR>>> with the fields
SL>> Feel free to share specifics..
> I don't understand why some information is given a line for the field
> yet the connection information is still all in one line.
The "Operating Dialup FTS-1 at" was designed to be backward
compatible with the St Louis nodelist, so you could copy anything after
that string back into the St Louis nodelist.
> I figure if you were going to use this type of format there would be
> a greater number of defining lines.
What for? Other connection methods than FTS-1 and BinkP? There is scope
for more if needed, eg. "Operating TCP/IP VMODEM at example.org".
Which reminds me, there's no method to specify an alternate BinkP port
number in my proposal, so I'll have to fix that. Something like
Operating [TCP/IP] [Binkp] [at] [host] [port]
Where [port] is optional, and if unspecified, the default BinkP port will be used.
Regards
Andrew
-- mail{at}ozzmosis.com
--- Msged/NT 6.1.1
* Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267)SEEN-BY: 633/270 @PATH: 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™.