aedes

aedes copied to clipboard

fix: send LWT on broker restart

25

This will require companion fixes on persistences, see aedes-persistence-redis #104 for example. The core issue is that clients state is not stored in any way, so these wills get orphaned...

friesendrywall

[question] Question on cleaning up write callbacks in case of error

4

For `write()`, we could potentially get stuck at line 11 if the stream is destroyed before the `drain` is emitted: https://github.com/moscajs/aedes/blob/e3e50ded602e7d69bdf8ba15ee07ce3527e004f1/lib/write.js#L5-L22 To solve this problem there is this hack in...

vishnureddy17

feat: preUnsubscribe handler

11

Invoked then a client unsubscribes from topics. Just like authorizeSubscribe, this function allows modifying the topics before executing the unsubscribe. This is needed in cases where topics are modified in...

chfritz

clean = false subscriber offline messages not sent in order

13

I hosted 2 aedes brokers connected to mongodb as a cluster. I was trying to publish messages continuously (20 messages per second) and receive them in subscriber side. I noticed...

CWilliamL

[feat] Mqtt v5 support

34

Hi I am wondering if anybody has started taking a look at MQTT v5 specs. Is there someone working on that or would like to work on the implementation? Here...

muka

Subscriptions not effective on first connection

14

Hi everybody, I'm new to mqtt so I'm sorry if the question is silly. Broker settings (over TLS): Concurrency: 100 Emitter: redis emitter Persistence: mongo Client (mqtt.js) Clean session: false...

albertocaponedev

WIP: Shared subscriptions

8

Based on discussion: https://github.com/moscajs/aedes/pull/437#issuecomment-589549551

robertsLando

[bug] Publishing through AedesServer works, but messageId is always undefined

5

**System Information** - Aedes: 0.46.1 - websocket-stream: 5.5.2 - aedes-persistence-redis 8.0.1 - mqemitter-redis: 4.1.0 - NodeJS: 14.17.5 **Describe the bug** Currently in the process of replacing our old Mosca MQTT...

jemd93

Add username from CONNECT to client after authenticate succes

3

Re issue https://github.com/moscajs/aedes/issues/147, the basic requirement in any authentication scheme is knowing the username specified during the CONNECT phase. So I think this really should be in the core API,...

faceless2

[feat] New example showing websocket authentication via HTTP form

3

Not exactly a feature request, but: the supplied examples are very simple and didn't cover a use case I wanted, which was to allow a WebSocket connection to pre-log-in with...

faceless2