-
The socket option ZMQ_XPUB_NODROP (69) is supposed to toggle the behavior of the socket when SENDHWM is reached. If 0/false (the default), messages are silently dropped. If 1/true, sending a message w…
-
This means that we can share the same configuration object among multiple Subject. It also makes the internal code simpler, as there are less individual parameters to pass around.
-
### Description
I'm encountering random segmentation faults (and sometimes AccessViolationException and NullReferenceException) when running a dotnet 8.0 console app on 32-bit ARM linux. It seems to …
-
### Environment
NetMQ Version: 4.0.1.13
Operating System: Windows 10 IoT Enterprise LTSC
.NET Version: .Net 6.0 (for now)
### Expected behaviour
The server/driver should …
-
### Environment
NetMQ Version: 4.0.0.207
Operating System: *
.NET Version: .NET Core 3.1
### Expected behaviour
Calling `Connect` on a NetMQSocket expects a special-forma…
-
### Environment
NetMQ Version: 4.0.16
### Expected behaviour
Msg will expose `Span Slice()` and `Memory SliceAsMemory();`
### Actual behaviour
`Msg.Data` is marked as `Obsolete `…
-
I tested the performance of the "old" select-based zmq_poller_poll implementation vs. the "new" WSAPoll-based zmq_poller_poll implementation on a Windows 7 x64 machine, and found the "old" select-base…
-
Is there any work in this library to handle message durability?
-
### Environment
NetMQ Version: 4.0.1.6
Operating System: Windows 10 Pro build 18363
.NET Version: .Net 5.0 and .Net Core 3.1
### Context
When receiving messages from a soc…
-
We're building a microservices/distributed system with containers and .NET 6.0 and need a fast/lightweight bus to send messages from physical devices, maybe up to 50.000/s. NetMQ is the candidate for …