So you are right, all bindings that are using hard coded sizes need to change the size, according to the libzmq version.
maybe we can make zmq_msg_type_size method for future versions. On Thu, Jan 28, 2016 at 7:35 PM, Brian T. Carcich <[email protected]> wrote: > anyone who has written an interface who has hardcoded that size might > object ... > > On Thu, Jan 28, 2016 at 11:44 AM, Doron Somech <[email protected]> wrote: > >> Hi All, >> >> I working on a new socket pattern, called radio-dish, the thread safe >> simplified version of pub-sub. >> >> As part of the work I need to add 32 bytes to the msg class, so I want to >> increase the size to 128 bytes. >> >> We will also benefit from less allocation, as the bigger size allow more >> messages to be inlined in the struct. The downside of this is slower copy >> operation (copying 128 bytes instead of 64), more memory used and require >> recompiling for anyone using dynamic linking (I think). >> >> I want to know if anyone have any objection to do so? >> What problem do you see this can cause? >> Of course it is only relevant to version 4.2. >> >> Regards, >> >> Doron >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
