Endianness & Network Byte Order
Endianness determines byte ordering in memory. x86/ARM processors are Little-Endian, but internet networking mandates Big-Endian (`!` or `>` in `struct`) ðŸ§.
import struct, sys
val = 1 # 16-bit integer
little = struct.pack("<H", val) # b'\x01\x00' (Least significant byte first)
big = struct.pack(">H", val) # b'\x00\x01' (Most significant byte first)
print(f"Little-endian: {little} | Big-endian (Network): {big} ðŸ§")
print(f"Native system endianness: {sys.byteorder} 💻")
# 80. Endianness & Network Byte Order Endianness determines byte ordering in memory. x86/ARM processors are Little-Endian, but internet networking mandates Big-Endian (`!` or `>` in `struct`) ðŸ§. ```python import struct, sys val = 1 # 16-bit integer little = struct.pack("<H", val) # b'\x01\x00' (Least significant byte first) big = struct.pack(">H", val) # b'\x00\x01' (Most significant byte first) print(f"Little-endian: {little} | Big-endian (Network): {big} ðŸ§") print(f"Native system endianness: {sys.byteorder} 💻") ``` Always use `!` or `>` when writing socket protocols or reading binary file formats. Never rely on the host machine's native endianness! 🧠--- ### Question What standard byte order is required by internet network protocols? 🧠- [ ] a. Big-Endian (Network Byte Order, specified by `>` or `!`) 🧠- [ ] b. Little-Endian (specified by `<`) - [ ] c. Middle-Endian - [ ] d. Randomized per packet --- ### Challenge Import `struct`. Pack integer `256` as big-endian 16-bit (`'>H'`) and print the resulting raw bytes. 🎯 <details> <summary>Solution</summary> ```python import struct print(struct.pack(">H", 256)) ``` </details>