Slimelite BBS

NET_DEV

Back to FREE25

From David Appleby · 1996-04-07 22:58 · #73095 in FREE25

Leonard Erickson wrote in a message to David Appleby:

 LE> The ability *to* skip that step is the "backwards compatability".
 LE> Tossers/mailers for the new format merely need the ability to generate
 LE> old-style packets on a per system basis and then you have all the
 LE> "support" that's needed for the older systems.

Of course.  What will probably happen as messages are converted backwards and forwards between Type-2 packets and a new packet format is that there will be more kludge lines added to the Type-2 message so that a tosser that handles the new message could easily convert it back.  We are already suffering from kludge line overload, and this is not what we need.

 LE> And when ARCmail came into widespread use, they added the MN flag 
 LE> to the nodelist. 

Which all the major software packages that I'm aware of ignore.

 DA> Your analogy doesn't go all the way.  Even if there was a nodelist
 DA> flag specifying what kind of message packet format a system could
 DA> support, it's still not as simple as leaving a step off the end of the
 DA> tossing process.  To make it worth while implementing a new packed
 DA> message format the information in that format would probably have to
 DA> be greater than the information in a current packed message. 
 DA> Translating from some kind of new format to the current format
 DA> probably would not be that difficult but translating from the current
 DA> format to a new format would be more of a job than executing ARC. 

 LE> I disagree. If the new format has extra info, then translating to the
 LE> *old* format will be easy, because you just leave out the extra info.
 LE> (for instance type 2+ and 2.2 PKT files have info that a type 2 system
 LE> neither needs nor wants). 

And how do you convert the message back?  There's not much point in only being able to convert one way.  If systems that can handle the new type packets are connecting further along the chain they should be able to recreate the new packet from the information in the Type-2 packet.

For example, if the new packet type had the address of the system that created the message in the header, in addition to the address of the system originating the current copy of the message, but did not require an origin line there would have to be some way of putting that information into the Type-2 packet that is created in backwards translation so that it could be recreated when the translation goes forward again.

 LE> We can handle other changes in similar ways. The mailers don't care
 LE> *what* kind of files they transfer. You just need something to process
 LE> them. If nobody writes a handler for your system, you fly a flag saying
 LE> that you can't. And folks who send stuff to you have to honor it.

Which would be another flag for the software authors to ignore.  Not to mention the fact that there is no agreement between zones on what nodelist flags are allowed and disallowed.

 DA> don't know about you, but Squish over here will quite happily send an
 DA> archived message to a node flying the MN flag if I have a default

 LE> I'm sure that you can *override* the default on a system by system
 LE> basis, can't you? If not, then all it takes is an MN system complaining
 LE> and *you* would have to change software.

I can override the default but if the default is set to send ARCMail to all nodes unless their is a specific override in the configuration file the system will send ARCMail bundles to a system that flying the MN flag.  The defaults are changed by discussion between me and my links, not by various flags in the nodelist.

 LE> BTW, the fact that the version 7 nodelist omits info is a problem for
 LE> the software that uses it, not for the rest of the network. 

Does your software recognize the MN flag and refuse to send ARCMail bundles to those sites?  Does your software recognize the Gxxx flags when routing mail to another networks gate?  Does your software handle the ISDN flags when they appear alone in the nodelist without any other modem capability flags and realize that it can't connect there?

Dave. 
--- timEd/2 1.10+
 * Origin: BackTalk : klaTkcaB  (1:153/970.1)