Would it be possible to create a native LabVIEW language version of ZMQ?
This would allow easy portibility between the different real time and win32 based targets that LabVIEW supports.
It would also remove the dependecies of a DLL.
I've only glanced over the ZMQ external communiation specifications, but it seems like with the right dedicated people such an effort would be possible.
Has this been discussed before?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sure it would be possible, it's just a question of how much work it would be. Perhaps LabVIEW's native multithreading would be advantageous even. To be honest, I had not considered reimplementing the protocol at the wire level but the spec for the protocol v3.0 seems pretty well defined actually - if such documentation existed when I started this project 5 years ago I may even have done this from the beginning!
There would definitely be benefits to a native rewrite regarding portability, stability and transparency, but development and testing would require significant devotion of resources that I think would require sponsorship/investment of some kind.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Reading through the RFC https://rfc.zeromq.org/ It seems farily well defined.
I was getting excited till I read spec:23 ZMTP Version Negotiation. Appears there is a version handshake and limited backward support for older versions. Regression testing is a pain.
I wouldn't mind picking one of the more simpler ZMQ features and just see where the project goes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Would it be possible to create a native LabVIEW language version of ZMQ?
This would allow easy portibility between the different real time and win32 based targets that LabVIEW supports.
It would also remove the dependecies of a DLL.
I've only glanced over the ZMQ external communiation specifications, but it seems like with the right dedicated people such an effort would be possible.
Has this been discussed before?
I'm sure it would be possible, it's just a question of how much work it would be. Perhaps LabVIEW's native multithreading would be advantageous even. To be honest, I had not considered reimplementing the protocol at the wire level but the spec for the protocol v3.0 seems pretty well defined actually - if such documentation existed when I started this project 5 years ago I may even have done this from the beginning!
There would definitely be benefits to a native rewrite regarding portability, stability and transparency, but development and testing would require significant devotion of resources that I think would require sponsorship/investment of some kind.
Reading through the RFC https://rfc.zeromq.org/ It seems farily well defined.
I was getting excited till I read spec:23 ZMTP Version Negotiation. Appears there is a version handshake and limited backward support for older versions. Regression testing is a pain.
I wouldn't mind picking one of the more simpler ZMQ features and just see where the project goes.