Le 13/01/2014 15:30, Martin Sustrik a écrit :
If you're patch is generic enough we can even merge it to nanomsg to be switched on by a socket option or such. Martin
Nice. To speed-up my understanding please, a few more questions:The REQ/REP end-to-end feature described here (https://raw.github.com/nanomsg/nanomsg/master/rfc/sp-request-reply-01.txt), that enables the answer to go back to the right REQ node works in which additional conditions ?
If I build intermediate REP/REQ nodes with nn_recv and nn_send of the API, that makes use of void* buffers, I understand that from a receive to the send, I loose the message header and then the channel IDs stack ? So here, it does not work ?
Does it work only with nn_sendmsg / nn_recvmsg which manipulate the header ? So device manages it ?
Could you explain struct nn_iovec, struct nn_msghdr and nn_device_mvmsg working ?
Cheers, Laurent