On Wed, 23 Aug 2017 10:51:25 +0200 Christian von Kietzell <chris...@vonkietzell.de> wrote:
> [*1] The data comes from a web browser extension using the native > messaging API, which specifies that messages sent to external programs > are prefixed with the 32-bit length of the message in native byte order. I understand that 'native bo' in this context means 'remote client side endianess'. If so the safest way is to parse incoming request headers, guess byte order from that and tag data as appropriate. If it meant just local2local (local browser talking over lo/pipe) may simply compile endianess variants according to GOARCH. https://godoc.org/go/build#hdr-Build_Constraints -- Wojciech S. Czarnecki << ^oo^ >> OHIR-RIPE -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
