You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2019. It is now read-only.
Sir. I donot think it a good idea to kepp alive by publishing a topic. As I have tested your code, to publish a topic needs sending at lease 7 or 8 bytes. while the mqtt heartbeat is only 2 bytes. That means the best advantage of mqtt is not longer existed.
We could send the MqttPingReq by modify the paho code. See : https://github.com/chinesejie/paho-for-android
The text was updated successfully, but these errors were encountered:
I will definitely take a look at that project. That was always the one
issue with the Paho client and Android. I will update this when I make the
changes.
On Jul 20, 2013 1:08 AM, "Bryant Liang" notifications@github.com wrote:
Sir. I donot think it a good idea to kepp alive by publishing a topic. As
I have tested your code, to publish a topic needs sending at lease 7 or 8
bytes. while the mqtt heartbeat is only 2 bytes. That means the best
advantage of mqtt is not longer existed.
This will be changed in my newest release in a couple days. There is an easy work around to access the ping request in the Paho library without changing the source.
Sir. I donot think it a good idea to kepp alive by publishing a topic. As I have tested your code, to publish a topic needs sending at lease 7 or 8 bytes. while the mqtt heartbeat is only 2 bytes. That means the best advantage of mqtt is not longer existed.
We could send the MqttPingReq by modify the paho code. See : https://github.com/chinesejie/paho-for-android
The text was updated successfully, but these errors were encountered: