Hi,
I've looking at the zeroMQ source code a little bit and was surprised that
wire.hpp implements custom endianess converison function to convert 16, 32 and
64 bit values from/to network byte-order. Is there any reason for not using
available functions like hton* or htobe family on Linux? I am
If you can show that it's faster to use the default functions, please make
a pull request, we'll merge it.
On Mon, May 11, 2015 at 10:56 PM, Auer, Jens wrote:
> Hi,
>
> I've looking at the zeroMQ source code a little bit and was surprised that
> wire.hpp implements custom endianess converison f
>
> (but it is on the criticl path for large messages)
If you were using this approach to encode fields in some general
serialization format, maybe it would make a measurable difference, but it
seems unlikely to do so relative to framing ZeroMQ messages. In the "worst"
case the put|get_uint64 (i
