[zeromq-dev] conventions in bindings

[Gary Wright]

On Feb 2, 2012, at 1:50 PM, john skaller wrote:
> On 03/02/2012, at 5:33 AM, MinRK wrote:
>> message-container:
>> a zmq_msg_t object
>> 
>> This I think is exactly the point of confusion I would like to address.  zmq_msg_t *does not* contain a message, it contains a message *fragment*.
> 
> You're right. My bad!
> 
>> A Message is the information contained in a collection of (one or more) zmq_msg_t objects linked by SND/RCV_MORE.  
> 
> It can be. But actually that isn't so in the Felix binding, only one zmq_msg_t object is used 
> at a time, the fragments are lifted out put into a list or array or strings.
> [Not very efficient but it will do for the moment :]

I think it can be confusing to mix layers like this. In this case you are mixing the terminology
of the libzmq library with the terminology for your Felix binding.  There needs to be a mapping between
the two but unless you are discussing the mapping itself, it is clearer to stick to one
context and its associated terminology.

So it sounds like in Felix, a ZMQ message is an array of strings, where each string represents
a ZMQ message fragment.  Talking about zmq_msg_t at this level doesn't make any sense (to me) but
if I specifically asked about how you interface with libzmq then it might make sense to start
talking about zmq_msg_t objects (or is structs? or fragments? or message parts? :-). 

Gary Wright