Question

My guess is that data is scattered in physical memory (even the data of a class object is sequential in virtual memory), so in order to send the data correctly it needs to be reassembled, and to be able to send over the network, one additional step is the transformation of host byte order to network byte order. Is it correct?

Answer 1

Proper serialization can be used to send data to arbitrary systems, that might not work under the same architecture as the source host.

---

Even an object that only consist of native types can be troublesome sharing between two systems because of the extra padding that might exists in between and after members, among other things. Sharing raw memory dumps of objects between programs compiled for the same architecture but with different compiler versions can also turn into a big hassle. There is no guarantee how variable type T actually is stored in memory.

---

If you are not working with pointers (references included), and the data is meant to be read by the same binary as it’s dumped from, it’s usually safe just to dump a raw struct to disk, but when sending data to another host.. drum roll serialization is the way to go.

I’ve heard developers talking about ntohl / htonl / ntohl / ntohs as methods of serializing/deserializing integers, and when you think about it saying that isn’t that far from the truth.

---

The word “serialization” is often used to describe this “complicated method of storing data in a generic way“, but then again; your first programming assignment where you were asked to save information about Dogs to file (hopefully^*) made use of serialization, in some way or another.

^* “hopefully” meaning that you didn’t dump the raw memory representation of your Dog object to disk