Re: Simple Data Endianness

[Optikos <ZUERCHER_Andreas@outlook.com>]

On Friday, February 14, 2020 at 2:22:23 PM UTC-6, Dmitry A. Kazakov wrote:
> On 2020-02-14 18:25, Optikos wrote:
> > On Friday, February 14, 2020 at 2:20:40 AM UTC-6, Dmitry A. Kazakov wrote:
> >> On 2020-02-13 21:36, Optikos wrote:
> >>> On Thursday, February 13, 2020 at 11:29:46 AM UTC-6, Dmitry A. Kazakov wrote:
> >>>> On 2020-02-13 17:47, Optikos wrote:
> >>>>> On Thursday, February 13, 2020 at 9:28:16 AM UTC-6, Dmitry A. Kazakov wrote:
> >>>>>> On 2020-02-13 16:12, Optikos wrote:
> >>>>>>> On Thursday, February 13, 2020 at 5:10:44 AM UTC-6, Dmitry A. Kazakov wrote:
> >>>>>>>> On 2020-02-13 10:42, guijarrockGuijarro wrote:
> >>>>>>>>
> >>>>>>>>> The problem I present today is related to the coexistence between big-endian and little-endian
> >>>>>>>>> application data.
> >>>>>>>>
> >>>>>>>> How low-level representation aspect might be relevant to application data?
> >>>>>>>
> >>>>>>> If the exchange of app data between 2 or more computers is word-wise binary instead of byte-wise
> >>>>>>> textual, such as via binary-formatted files or via binary-formatted datagrams/byte-streams as
> >>>>>>> payload of networking protocols.
> >>>>>>
> >>>>>> And how whatever protocol encoding format is could to "coexist" (?) with
> >>>>>> another itself (?)
> >>>>>>
> >>>>>> In any case it has nothing to do with application data as kept in the
> >>>>>> memory.
> >>>>>
> >>>>> Even your facetious example of app-data exchanged in Mayan numerals stored in GIF images needs to
> >>>>> be in DRAM for encoding and decoding the app-data to other modules of software elsewhere in the
> >>>>> app.
> >>>>
> >>>> Nope.
> >>>
> >>> I reiterate:  Even your facetious example of app-data exchanged in Mayan numerals stored in GIF images needs to be in DRAM •••at some point, even if for a passing transient momentary instant (e.g., local to a procedure or function; or in a I/O buffer; or in preparation to conform to the GUI API's expectations)••• for encoding and decoding the app-data to other modules of software elsewhere in the app.
> >>
> >> No. That is technically wrong. A communication artifact does not need to
> >> be in the memory in order to be encoded or decoded. In fact it is rather
> >> an exception, even for integers. E.g. when an integer is encoded using a
> >> chained code. So, if GIFs were used for the purpose they would be
> >> encoded/decoded incrementally.
> > 
> > No, you are factually incorrect in the technical domain.  Even if streaming binary app-data piecemeal to evermore-accumulated content of a transient buffer,
> 
> [...]
> 
> I don't know what you mean.

Now there is a correct statement.