2 ms·
Yeah, I've designed some and seen some designed which are LE. There were mostly newer and all used where latency performance was very important. I saw one work
by rdtsc 10y ago
Yeah, I've designed some and seen some designed which are LE. There were mostly newer and all used where latency performance was very important.
I saw one working group designed a protocol such that the serialiazation format was equivalent to how gcc on 64 bit, intel linux machineas would pack C structures.
This was of course never mentioned in the official description, as it was supposed to be architecture/compiler/machine neutral, but I kept wondering why the odd padding here and there, and then it dawned on me.
So if someone was going to play fast and loose, they could just simply cast packet data directly to a C struct. If anyone happens to have a different, compiler / architecture / etc they'd have to jump through hoops a bit inserting seemingly awkward pad bytes and do le-to-be conversions.