-
Notifications
You must be signed in to change notification settings - Fork 9
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
Make use of MQTT Persistent Sessions #4
Comments
First of all 100 MQTT queued/persistent push messages up to 255 bytes are more than sufficient for most use cases. Normally the queued 100 messages are not needed because all push messages (e.g. silent once without a notify popup) are sent to the app, this means only a copy of the last 100 messages are saved on the server. The concept is that our Push Server listens for the app subscribed topics for messages and forwards this messages to the app in the background. The app does not talk to the MQTT server at all. Only the server listens permanent for new messages and forwards this to the mobile app. Only in case where mobile phone is turned off or unavailable for a longer period the last 100 messages are cashed and supplied when the phone is connected to the Internet again. I believe you concept is wrong when you need so many and very large messages. Again, use the short messages only, for large stuff lets the Dash pull the data from somewhere else (not our Push Server) via JavaScript. |
I wish that be true but apparently, it's not. Did you read our conversation in the original issue?
I'm sorry but 100 saved messages apparently are not sufficient either:
Thanks for the clarification. I can argue with such design though:
That seems quite a common case to me. Why would I lose all the data more than 100 messages long then? |
Dear Andrey Butirsky, we have a couple of thousand accounts, and this is how it works and how it is designed, and all users are fine with this. We don't destroy our design for your requests. |
Do you think we could utilize MQTT Persistent Sessions for that?
100 MQTT push messages restriction (and the restriction of 256 bytes per message) is quite a shortcoming. As well as relying on 3rd party server user can't control.
So I would propose communicate with the MQTT push server only when it strictly necessary (for it's purpose - push notifications themselves). In all the other cases, use MQTT broker normally.
The text was updated successfully, but these errors were encountered: