NsqSharp
NsqSharp copied to clipboard
judwhite
A .NET library for NSQ, a realtime distributed messaging platform
This tiny PR adds the basic support for client certificate authentication.
There is a bug when topic name end with #ephemeral. It occurs when communication with nsqlookupd
I have 1 producer producing ~20k m/s and 1 consumer trying to consumer them all without falling behind. I'm using 16 threads on the handler and I set the max-in-flight...
Certificate collection is empty in code as below ` try { sslStream.AuthenticateAsClient(_hostname, new X509Certificate2Collection(), enabledSslProtocols, tlsConfig.CheckCertificateRevocation); } catch (Exception ex) { throw new Exception(string.Format("{0} - {1}", ex.Message, errorMessage), ex); }...
- Now ``NsqSharp`` targets NET Framework ~4.5~ 4.6.1+ and NET Standard 2.0 - New project ``NsqSharp.WindowService`` targeting NET ~4.5.1~ 4.6.1 to keep the ``BusService`` static class with support for Window...
I am trying to publish message to nsq **My Code:** `var producer = new Producer("xxx:9011", new ConsoleLogger(LogLevel.Debug));` `producer.PublishAsync("DotNetCore", "test");` **Centos** CentOS Linux release 7.2.1511 (Core) **NSQ** nsqd v1.0.0-compat (built w/go1.8)...
The handler interface does not support async implementations. Either add a new async method implementation or replace existing one to return a Task. Add async wherever else it makes sense...
Consumers are slow to receive messages， Article 20 / s，why？ 消费端接收消息很慢，每秒20条，什么原因？
I tried to deploy multiple nsqlookupd. When multiple connections are made, for example: Var consumer = new Consumer ("test-topic-name", "channel-name"); Consumer. AddHandler (new MessageHandler ()); Consumer. Connect ToNsqLookupd ("127.0.0.1:7161", "127.0.0.1:4161");...
