Log message ID in host byte order
authorDan Mihai <Daniel.Mihai@microsoft.com>
Wed, 22 Feb 2017 22:56:07 +0000 (14:56 -0800)
committerMike Fenelon <mike.fenelon@microsoft.com>
Mon, 6 Mar 2017 17:58:48 +0000 (17:58 +0000)
commit46467a7dd8bae4c3b17519eeee01f2fc80fe3a6b
tree8e7091cd3905a454aa083786e8049392d72e5f60
parent5da3a8013e2309ff222d2e9432dc77c54d7a733e
Log message ID in host byte order

Both libcoap and CTT use the host byte order, so this change helps
correlate their log contents with the IoTivity logs.

Change-Id: If8b91a35017329a1a2a5bbe2770c71122c2f382a
Signed-off-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17455
Reviewed-by: Mike Fenelon <mike.fenelon@microsoft.com>
Tested-by: Mike Fenelon <mike.fenelon@microsoft.com>
resource/csdk/connectivity/src/camessagehandler.c