New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
createRetainedStream is per topic #122
Comments
How big is This would need to be changed in aedes-persistence, and then downstream to all implementors. I'm 👍 if you want to tackle this one. |
and please clarify something for me, I had checked mqtt spec some time ago, but can't remember if we should sendRetained both on CONNECT/SUBSCRIBE, or only as a response to a SUBSCRIBE command? I mean when a client SUBSCRIBEs with qos=1 and clean=false, should we send retained on each subsequent feature connects only? |
@behrad the retained check is part of the mqtt implementation decisions :(. Mosquitto implements it the same way we do, resending the retained message on connect. However, the spec is unclear to me. @behrad go ahead and start making the changes. However, I would implement it in as a non-breaking changes. Adding a new |
handled in #121 |
createRetainedStream
is called per subscription topic, for client's with multiple subscriptions it looks weird. e.g. redis persistence currently runshget retained
n
times for a client connecting withn
offline subscriptions.Can we
createRetainedStream(topic)
tocreateRetainedStream(topics)
in persistence api.packet.subscriptions.map(s=>s.topic)
The text was updated successfully, but these errors were encountered: