Re: Low-latency alternative to Java Object Serialization

On Mon, 3 Oct 2011 19:24:20 +0100, Tom Anderson <twic@xxxxxxxxxxxxxxx>
wrote, quoted or indirectly quoted someone who said :

Specifically, i believe
that: (a) developing an XML-based transfer format using JAXB will take
considerably more effort than using standard serialization

Serialisation handles complex data structures, even loops. XML is
limited to trees.

Serialisation handles any imaginable data type without extra work. XML
requires inventing an external character representation and a way of
converting to chars and back.

Serialisation is hard to upgrade. XML is easy. Serialisation pretty
much requires everyone to stay in sync with identical software. XML
allows clients with out of date software, software in other languages,
or even no software at all.
Roedy Green Canadian Mind Products
It should not be considered an error when the user starts something
already started or stops something already stopped. This applies
to browsers, services, editors... It is inexcusable to
punish the user by requiring some elaborate sequence to atone,
e.g. open the task editor, find and kill some processes.