On Fri, Aug 14, 2009 at 8:28 AM, DaveP<pelow...@pelowitz.com> wrote: > > I quickly reviewed the documentation and the faq and found no > reference to the protocol demanding big endian or little endian or > associated byte order conversion. Does the protocol require one or > the other? Alternately, does the compiled have an "endian" switch/ > conversion option in the resulting code? Specifically, I'll be > generating binary data on a big endian and sending to a little endian.
The generated code of protocol buffers guarantee that you get read the data out in the correct byte order for the local machine. The _binary_ encoding of the protocol buffers is independent of the platform it is sent from, so you don't have to care about that. So you're all good ;) -h (the binary format is doing little endian because of slightly better performance on the typical machines Google uses .. but as I said, you don't have to care about that). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
