= Сообщение: 6028 из 7128 ====================================== FTSC_PUBLIC = От : andrew clarke 3:633/267 15 Feb 22 05:35:19 Кому : Tim Schattkowsky 15 Feb 22 05:35:19 Тема : MSGID FGHI : area://FTSC_PUBLIC?msgid=3:633/267+620aa40f На : area://FTSC_PUBLIC?msgid=2:240/1120.29+33dbc312 = Кодировка сообщения определена как: LATIN1 ================================= ============================================================================== On 2022-02-14 19:11:04, Tim Schattkowsky (2:240/1120.29) wrote to Oli:
TS> I am also a bit suprised by this discussion because it appears that TS> somebody has the idea of using the address part of the MSGID for an TS> unintended purpose. From my perspective, the *address part is TS> essantially a unique ID that represents the system generating the MSGID TS> number*. This enables the *two together to form a unique identifier for TS> the message* itself w.r.t the system that has created the original FTN TS> message.
I don't recall the details but in the mid-1990s there were discussions on NET_DEV from devs wanting to parse the MSGID to obtain the address of a message instead of parsing the Origin line. The likely thinking at the time being that parsing the MSGID just after the header meant the software didn't have to waste CPU cycles looping over each line of the message until they got to the Origin line.
But there was never any guarantee in FTS-9 that the MSGID origaddr matched the Origin line's origaddr.
Of course this was back when hard drives were slow and CPU speeds were still measured in megahertz. I remember someone once wrote a FTN packet sorter that sorted by echoarea to supposedly optimise tossing speed. Wild.
--- GoldED+/BSD 1.1.5-b20180707 * Origin: Blizzard of Ozz, Melbourne, Victoria, Australia (3:633/267)
