[zeromq-dev] 3.x zmq_msg_t change proposal

[Chuck Remes]

On Oct 27, 2011, at 3:58 PM, Pieter Hintjens wrote:

> On Fri, Oct 28, 2011 at 2:58 AM, Chuck Remes <cremes.devlist at mac.com> wrote:
> 
>> And looking at ZMQ_RCVMORE and how it is used, I'm not convinced this should be a property of the socket either.
> 
> Indeed. This was one of my change proposals for 3.x. It's how CZMQ
> does it on zframe.
> 
>> I looked back through all of the message threads from the past 1+ years where RCVMORE was discussed (it was introduced around April 2010). I could not see any reason given for why it had to be a socket property.
> 
> It was historically meant to simplify the API afair.
> 
> Your proposal is great, yes.

I will await some more feedback.

However, in the meantime, I will fork the repository and add these new functions. The nice thing about them is that they do *not* break backward compatibility. If the community agrees, we could deprecate the use of zmq_getsockopt() for RCVMORE, RCVLABEL and whatever else and then in 4.0 release that old functionality would be removed. It would also be nice to see the patch applied to 3.0.

I'm going to follow the instructions as given here [1].

cr

[1] http://www.zeromq.org/docs:contributing