Shunta Roy

Hi Christopher, To answer your questions as far as I have experienced with Push Pull sockets: 1) It is right that it will block unless you start the 'Pull' socket and process the data. As per documentation states, in this mode i.e; Pipeline (Push-Pull), no data is lost or dropped if the relevant ends are not present. And that the Push -Pull type socket would go into mute state when it reaches its HWM (sndHWM and rcvHWM). 2) One option could be is that you open a parallel req-rep socket and forward...

Hi Martin, Thanks for your reply. I would like to access the information on the total number of messages without removing them from the socket itself, something similar to 'Preview Queue Element and Get Queue Status' from the Queue palette in LabVIEW. I guess the functions in the zmq_msg family would be the ones which I would like access to via the LabVIEW library. If there is another way to achieve it, can you also share more regarding this! Thanks, Shunta

I would like to access the msg API over LabVIEW (reference: Working with Messages section in Chapter2: Sockets and Patterns) and have found that the wrapper code 'zmq_labview.c' does not comprise of the relevant functions present in the 'libzmq64.dll'. Is there a way to extend the code or can be incorporated in the upcoming releases?

The lates version for download is ' 3.3.1.102.vip', however the current modified packet has the version '3.5.1.109.vip'. Can you please define what are the differences amongst them. Moreover after downloading the 3.3.1.102 and running the 'Get Version.vi', it delivers the version number as 4.0.4. How do we differentiate between the different versions and what does it comprise of?