Add emitter #62
Add emitter #62
Conversation
Signed-off-by: Glenn Lewis <6598971+gmlewis@users.noreply.github.com>
Signed-off-by: Glenn Lewis <6598971+gmlewis@users.noreply.github.com>
Signed-off-by: Glenn Lewis <6598971+gmlewis@users.noreply.github.com>
Signed-off-by: Glenn Lewis <6598971+gmlewis@users.noreply.github.com>
Signed-off-by: Glenn Lewis <6598971+gmlewis@users.noreply.github.com>
Signed-off-by: Glenn Lewis <6598971+gmlewis@users.noreply.github.com>
|
friendly ping |
|
@gmlewis thanks a ton for your contribution! Apologies for the delay GitHub didn't push a notification my way when you first opened it and I've been on vacation followed by being swarmed at work and didn't notice it! I'll give it a look over the weekend! |
|
An initial question (and forgive me if it's too obvious but I'm not 100% expert in MQTT + Emitter) but do you think it is necessary to have an explicit version for Emitter as oppose to having a general purpose MQTT driver that can be configured to use Emitter or other MQTT implementations (kinda like an extension to #56) 🤔 |
|
Hmmm... that's an excellent question, @ojizero - and honestly, since I wrote that PR, I've been learning more about nats.io and am wondering if I should change my current systems to start using nats.io and stop using emitter.io. At the time, I thought Emitter provided some really nice features like the securing of channels, but now I'm kinda wondering if there is added benefit. If you come to the same conclusion, then I'm totally fine if you just want to simply close this PR. 😁 |
This PR adds a new underlying queuing technology to "vice" called Emitter which is a high-performance, low-latency, and secure platform based on MQTT. More details can be found at emitter.io.