[zeromq-dev] Zero-copy message API
Brian Granger
ellisonbg at gmail.com
Sun Apr 3 21:19:51 CEST 2011
Pieter,
In pyzmq, we exploit the non-copying message API in very subtle ways,
so this is something we will have to watch very carefully. Getting
non-copying messages working with a language like Python is very
difficult and subtle and I strongly encourage the zeromq devs to look
at how we handle these things in pyzmq as these changes are made.
Cheers,
Brian
On Sun, Apr 3, 2011 at 2:16 AM, Pieter Hintjens <ph at imatix.com> wrote:
> Hi Martin,
>
> One thing that seems to consistently trip up users is the zero-copy
> message API, and the way it's presented. That is, reading the docs,
> there's no hint that zmq_msg_init_data() is much harder to use
> properly than zmq_msg_init_size().
>
> For the 3.0 API, it could be neat to slice these apart and make it
> clearer that there is a simple way for 90% of apps, and a complex way
> for 10%.
>
> For example, zmq_msg_init() might take a size argument, and merge the
> functionality of zmq_msg_init_size(), and then we could rename
> init_data to zmq_msg_init_zerocopy().
>
> -Pieter
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
--
Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger at calpoly.edu and ellisonbg at gmail.com
More information about the zeromq-dev
mailing list