| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | sot/eot |
In a message to Andrew Clarke Rod Speed wrote: AC> Instead of designing a new header, why not remove the header AC> completely and replace it with a set of kludge lines? RS> The main argument against doing that is that its a lot RS> quicker with decent code to process the fixed header stuff RS> for the fields that are appropriate in a fixed header. RS> Basically those that are used in almost every message. The "mandatory" fields. Now, what is required, and what is not? RS> Kludge lines are better for the stuff which is only used RS> occasionally, optional fields like say the character set RS> used in the message body and the variable length stuff where RS> you may want repeated use of a particular one. If there is a need to design something that is to replace the existing system, I would prefer all fields to be optional. This might seem unusual, but could prove quite useful in my opinion. I don't necessarily mean eliminating redunancy, either. ZeeYa... Andrew. ---* Origin: Blizzard of Ozz, Melbourne, Australia (3:635/727.4) SEEN-BY: 50/99 54/54 632/348 998 633/371 634/384 635/502 503 544 727 638/100 SEEN-BY: 640/230 690/718 711/401 410 430 807 808 809 934 942 713/888 800/1 SEEN-BY: 7877/2809 @PATH: 635/727 632/348 635/503 50/99 711/808 809 934 |
|
| 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™.