You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modern libzmq contains long-waited support of IPC protocol for Windows.
It would be very convenient for your users to make a fresh release with libzmq v4.3.4 included.
Thank you very much in advance!
PS I was lucky enough to update native libzmq under ClrZmq4 , but it was REALLY a headache.
The text was updated successfully, but these errors were encountered:
Just passing along my experience, since I'm just testing this for potential use in a project. There's presently a bug in 4.3.4 that breaks debugging in VS (OpenCppCoverage/OpenCppCoverage#141), so my thought is you probably want 4.3.5 (whenever that is released) before using this for testing Windows IPC (which is my use case as well). In the meantime, below is a recipe that got things working for me. Not saying this is the right long-term solution, but it solved my problem.
Pull and build the active libzmq repo, which incorporates the bug fix for the VS debug issue.
Pull the clrzmq4 repo, and add the following snippet to line 61 of zmq.cs. This fixes the message size changing from 32 to 64 at some point in the evolution of new libzmq versions.
if (minor >= 3)
{
var ctx = new ZContext();
sizeof_zmq_msg_t = zmq_ctx_get(ctx.ContextPtr, 6);
ctx.Terminate();
}
so my thought is you probably want 4.3.5 (whenever that is released)
I'm waiting official release of native libzmq v4.3.5 very much for a very long time.
I'm expecting IPC protocol to be about 10 times faster than TCP.
=) And I expect it will work in new release.
At the moment my experiments with Windows 2019 shows, that IPC doesn't work.
Modern libzmq contains long-waited support of IPC protocol for Windows.
It would be very convenient for your users to make a fresh release with libzmq v4.3.4 included.
Thank you very much in advance!
PS I was lucky enough to update native libzmq under ClrZmq4 , but it was REALLY a headache.
The text was updated successfully, but these errors were encountered: