Hi August,
On 2021-04-14 18:18:00, you wrote to me:
MK>>> @MSGID: 1:153/7001 tmCYOYVw
MK>>> Please note the MSGID of this reply.
WvV>> Besides not conforming to the standard, and maybe cosing
WvV>> problems in software down the line...
AA> It seems to be a problem for WinPoint when building a reply
AA> message. The REPLYID seems to result in 00000000.
So that is the first discovered problem. There are probably more. And probably
harder to discover...
WvV>> Because it doesn't conform to the standard (not strictly
WvV>> hex chars),
AA> You are adding words to the spec. "strictly" does not appear.
AA> ;) However, "may" is very clear. :D
I beg to differ...
WvV>> my tosser uses a different method for calculating a hash
WvV>> for this message (for dupe detection), which uses more cpu
WvV>> cycles. And thus heating up the planet more than a
WvV>> standard conforming MSGID. :-(
AA> They're all just a bunch of 1's and 0's in the end. It's all
AA> the same stuff. :D
But how we get there isn't...
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
|
