I agree with you… this can cause problems on some target architectures. Anyway, I’m fine with that as I’m not writing machine independent code so assume the target machine to be Big Endian looks like a sound assumption.
Btw, there are cross machine ways of representing data (eg: http://tools.ietf.org/html/rfc4506) so once the Big Endian assumption breaks it will be time to move to something more powerful.
Meanwhile, I updated my blog post on the topic. I found out that the raw encoding was quite difficult to decode when used for real data (the details on my blog post)…
So I improved the method sending the bytes HEX encoded. This way everything looks more polished and easier to process and debug. This comes with bandwidth costs of course.