2 ms·
So I wonder if the author read the XDR code. XDR, which is a lame acronym for eXternal Data Representation was what Sun's remote procedure call library used to
by ChuckMcM 13y ago
So I wonder if the author read the XDR code. XDR, which is a lame acronym for eXternal Data Representation was what Sun's remote procedure call library used to encode (or 'marshall' in the vernacular) arbitrary data into something you could send over a network and reliably unmarshal on the other side and get back the same data structure.
The positives (like tny) were that the code was very straightforward and easy to use. And one of the negatives were that it wasn't "self describing" (which JSON is to some extent).
Of course the ultimate in binary self describing data is ASN.1 syntax :-) but lets not go there.
- huhtenberg 13y agoSerialization formats are dime a dozen. Cooking up your own variation of TLV (+ TV for fixed-size T's) is dead easy and can typically be done a spot by anyone without any prior experience. As such I doubt "the author read the XDR code", though perhaps you weren't wondering that at all, but rather wanted to mention XDR and ASN.1, in which case you should've really just done that. As it's written, it makes "the author" look like either an ignorant imbecile who doesn't know such basics as XDR or as someone who piggy-backed on XDR without acknowledging it.