[ENet-discuss] enet endianess (byte order)

[Grant Mills]

Hi Oles

I have successfully sent messages over ENET between an x86 target and a MIPs target with no issues. So the ENET headers and internal commands are correctly converted.

To handle the payload message, I have been using Google Protocol Buffers to do the encode/decode into and out of the payload.

I hope this answers your question.

Regards


/grant


On Apr 28, 2012, at 8:56 AM, Oles wrote:

> Hi.
> 
> Documentation mentions that “ENet makes no assumptions about the underlying platform's endianess or word size“.
> Does it mean that I can send messages from big-endian CPU to little-endian and vice-versa?
> I mean, internal message data are correctly converted to little-endian on the app side, but what to do with enet internal headers?
> Or everything should work as expected?
> If it doesn't work - could you suggest places to modify?
> 
> Thanks a lot,
> Oles
> 
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss