On Friday, 27 October 2017 10:38:13 PDT Nash, George wrote:
> I missed that the UUIDs are doubly encoded. I may add that issue to the
> list. UUID can be send as 128 bytes no need to encode the string when it
> already has a standard encoding. One of the major arguments for CBOR is
> size if we are holding to that argument then we should probably be encoding
> the UUID.
Actually, never mind on the double-encoding. The values threw me off:
31313131-3131-3131-3131-313131313131
But they are of the correct size. There's no double encoding here. Just
storing the UUID as a string form.
Anyway, we've had this discussion before. Whereas we could send UUIDs as 17
bytes on the protocol (16 for the data, 1 for the overhead), we decided that
we would send the string-encoded form of 36 characters (including the dashes),
for a total of 38 bytes over the air (overhead increases to 2). The simplicity
of representing in JSON was the winning argument, over the 123% increase in
payload.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
