-
The internal `Options` class builds up a list of `TcpAcceptFilters` which are never queried.
The `TcpAddressMask.MatchAddress` is also never called.
-
The lazy receive functions described in #64 and implemented in #65 have a potentially surprising pitfall.
Because they yield a sequence of results directly "from the wire", the sequence can only be e…
-
The extension methods for receiving from sockets are not very friendly when starting out with NetMQ. There are several ways to achieve the same thing (`SendReiveOptions.DontWait` vs `bool dontWait`) a…
-
Hi @jkarneges,
Having a lot of fun playing with pushpin! Love the approach, I never realised how much time I was spending solving "socket" problems vs application problems before, and it's so nice to…
-
Hi guys,
we're using NetMQ on Unity (primarily targeting iOS, but also running it on OSX desktop for testing/developing purposes, as it has shorter iteration time). We've encounter Unity crash after …
-
Would this be a useful pattern?
Currently a Proxy produces its own internal poller in `Proxy.Start`. The method could be overloaded to accept an external poller.
`Proxy.Stop` would either throw or n…
-
I was testing the maximum concurrent connections that the netmq can handle:
using System;
using NetMQ;
using System.Numerics;
using System.IO;
using System.Text;
namespace HelloWorld
{
class Pr…
-
Stopping the NetMQMonitor hangs if monitor exited due to an exception.
InternalClose can be called after an exception on MonitoringSocket, and the first call in InternalClose is on MonitoringSocket w…
-
HI,
I found a weird issue and it did not show any exception.
I use PUB/SUB pattern.
The PUB located in Hong Kong, while the SUB located in Bangkok.
The PUB sends netmq message around every minute.
…
-
If there is a better or different forum for asking a question like this, please let me know, it wasn't immediately obvious to me where to ask.
I compiled a version of clrzmq targeting the 3.5 framewo…