5 ms·
Why? If I'm designing my own protocol I could use middle-endian EBCDIC encoded octal and it shouldn't make any difference to anything else.
by AnIdiotOnTheNet 5y ago
Why? If I'm designing my own protocol I could use middle-endian EBCDIC encoded octal and it shouldn't make any difference to anything else.
- rkangel 5y agoAre you building every implementation of the protocol? Or are you publishing a communications standard for people to implement? If I'm building a network stack and at every layer I'm pulling values out of the header in network byte order, except in one special case where I have to pull them the other way (for no good reason) then that's the protocol author's fault. If there is a good reason for using middle-Endian EBCDIC (compatibility or technical) then fine. If not, then please use the thing that's the strong convention and therefore simplest to work with.
- dahfizz 5y agoAs long as you don't want anyone to adopt the protocol, then go ahead.