7 Nov
2011
7 Nov
'11
4:49 a.m.
On Sun, 06 Nov 2011 23:04:44 -0500 "Hugo Duncan" hugo@hugoduncan.org wrote:
Is there a reason to start using a binary encoding of the message length? This makes the messages less easy to inspect, and less easy to write integration tests for.
The playload is an s-exp encoded as UTF8 text.
Normalising on utf-8 and counting bytes sounds like it would solve the original issue without changing to a binary encoding of the message length.
My assumption was that it was meant for performance, as large read syscalls could be used when the message length is known in advance (i.e. READ-SEQUENCE on a bytes stream), but I'm not sure.
--
Matt