> In general, using zero-copy techniques from garbage collected languages > is either impossible (Java?) or problematic (python). > > However, if what you are interested in is C/C++, the idea described > above is doable.
I am coming at it from a C/C++ perspective, but I can see how garbage collected languages complicate / preclude things like this. I would presume that Java/Python would also have issues integrating with the current zmq_msg_init_data's deallocator callback as well. > > zmq_msg_t already allows storing different types of messages (VSM which > is a small message stored directly in the structure vs. dynamically > allocated block of memory). There's no reason why there shouldn't be a > message type with multiple memory blocks. If we were to move forward with this idea, this was my initial take as well. Thanks, Mike _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
