| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Fidonet Technical Guidelines |
-=> Quoting Thomas Seeling to Tom Torfs <=- TS> Hallo Tom, TS> Am 05 Mar 99 um 21:57 schrieb Tom Torfs an Thomas Seeling: TS>> For exchange with other systems you need some well-defined TS>> interfaces, but who cares about the internal storage type of BBS TS>> messages? TT> Other programs that have to share this same messagebase. TS> this is quite a trivial answer. Of course, if you are the developer of TS> a BBS system, you would take care of this issue first of all. TS> You did not get the main point in my article: fts-1 is (has been 15 TS> years ago ...) the basis for Fido, but it goes ways too far in what to TS> define. A communications protocol is needed, obviously :). Not really. FTS-1 *explicitly* states that the MSG format is included only for reference. And it's also in there because the format of a "packed message" in a PKT is derived from the MSG structure. Heck, there are things FTS-1 *isn't* detailed enough about. --- Blue Wave/DOS v2.30* Origin: Shadowshack (1:105/51) SEEN-BY: 201/0 100 200 209 300 400 407 411 505 600 203/600 204/450 700 205/0 SEEN-BY: 206/0 270/101 490/21 633/267 270 @PATH: 105/51 360 138/146 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™.