You are obviously just playing silly buggers and doing some
cage rattling, but you get the basics totally screwed.

BL> Why do you need an EOT to define the end of a message
BL> when you have a tear line and origin line *following*
BL> the EOT that are part of the message anyway! The tear
BL> line can define the end... or the origin line.

Very simple really, the SOT and EOT bracket the message text body.
All the stuff outside that is header type stuff, even if it trails.

BL> The way it stands now, if I don't process your packets differently
BL> than the rest, I get annoying SOTs and EOTs in my messages, and if
BL> I do process your SOT and EOT I end up with a non-standard program
BL> that runs slower. Good one, Paul.

If you choose to optimise the alg for the traditional PKT format, coz
no one uses SOT and EOT, all you have to do is check for those AFTER
you have identified the message body and drop them. Dead easy to do.

You really dont have much choice while almost no one uses SOT and EOT.

--- PQWK202