Re: Endian issues...final chapter
toggle quoted messageShow quoted text
Totally agree when moving data between internet users. The downside is that binary 255 takes one byte but ASCII takes three bytes to push down a com link. If you are doing something computationally intensive, like moving FFT data to an SDR spectrum display, minimizing data transfer time can make a large performance difference. As Hans Summers (designer of the super-cool QCX transceiver from QRP Labs) pointed out, the endian issue must be handled even when writing to EEPROM on the same machine. You could store numeric data in EEPROM as ASCII, but then you need to pass through atoi() going into EEPROM and itoa() coming out. Clearly, Hans is storing his EEPROM data in binary.
CAT protocols like the one Ian Lee has worked on use an ASCII data transfer and it makes it so much easier to debug when something goes south. Even then, however, when commands can be as short as 10 bytes, someone reported a noticeable delay in response time. If you're only tool is a hammer, it should be no surprise that every problem looks like a nail. Binary versus ASCII protocols simply hangs a second tool on your belt. You need to decide which best solves your design problem.
From: Ashhar Farhan <farhanbox@...>
Sent: Sunday, March 11, 2018 12:49 AM
Subject: Re: [BITX20] Endian issues...final chapter
ietf solved this by insisting that internet protocos SHOULD be in plain text. it makes debuggera out our eyeballs and prevents testing of friendships.
On 11 Mar 2018 12:27 am, "Michael Hagen" <motdog@...> wrote: