| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Fidonet Technical Guidelines |
Thomas Seeling wrote in a message to Tom Torfs:
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.
You lost me there. What do you mean by "a trivial answer" ?
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
TS> to define.
I did get that point. I replied to your statement that the storage format
for messages is of no interest to anyone, which seemed to imply it needn't
be standardized. True, the *.MSG storage format in FTS-1 is outdated, but
that doesn't mean that storage format standardization in general is
useless. I would agree that it should probably be kept separate from the
communication protocols, however.
greetings,
Tom
tomtorfs{at}village.uunet.be
--- timEd/2 1.10.y2k+
* Origin: 80X86 BBS 32-15-24.62.32 V.34/V.FC (24h/24h) (2:292/516)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: 292/516 854 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™.