| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Nodelist-Flags |
GE> As I see it, the original use of [the "baud rate"] field
in the days
GE> when modems usually did not have speed buffering was to adjust the
GE> DCE-DTE speed to the expected DCE-DCE speed.
GE>
GE> If you expected a 300 bps connection you set your serial port to 300
GE> bps. If you expected a 1,200 bps connection you set your serial port
GE> to 1,200 bps. If you expected a 2,400 bps connection you set your
GE> serial port to 2,400 bps.
If it's any help, your view is borne out by the text of FTS 0005 version 3:
This baud rate is indicative only of the maximum baud rate that
may be expected when connecting to a node and is generally of use
only where a calling node needs to adjust the baud rate used to
dial to the caller's modem speed in order to achieve a
connection, a requirement that with modem technology available in
1996 is rarely if ever needed. This information is largely
superseded by modem protocol flags (see next section) where any
two nodes using a common protocol may have other expectations
with regards to actual transfer rates. Use of the baud rate field
alone is therefore depreciated.
GE> Are there any nodelist processing programmes (besides the InterMail
GE> nodelist compiler and old versions of the FrontDoor nodelist
GE> compiler) which will refuse to process a nodelist with speeds above
GE> 9,600 bps or act up in other ways?
If they cannot handle values up to 38400, they are not following the text
of FTS 0005 version 3, which also states:
Field 7: Baud rate
This field contains one of the values: 300, 1200, 2400, 9600,
19200, or 38400.
Don't mistake me for an FTS 000x supporter merely because I quote it, by
the way. I happen to think that the "official" technical
standards should have been scrapped and replaced by properly written,
clear, detailed, unambiguous, and well thought out technical standards
years ago.
¯ JdeBP ®
--- FleetStreet 1.22 NR
* Origin: JdeBP's point, using Squish (2:257/609.3)SEEN-BY: 201/0 200 209 300 329 400 407 411 505 600 203/600 204/450 700 205/0 SEEN-BY: 206/0 270/101 490/21 633/267 270 @PATH: 257/609 71 255/1 251/25 396/1 270/101 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™.