Skip to content
This repository has been archived by the owner on Jan 17, 2019. It is now read-only.

topic to keep alive #1

Closed
chinesejie opened this issue Jul 20, 2013 · 3 comments
Closed

topic to keep alive #1

chinesejie opened this issue Jul 20, 2013 · 3 comments

Comments

@chinesejie
Copy link

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

@JesseFarebro
Copy link
Owner

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.

We could send the MqttPingReq bu modify the paho code. See :
https://github.com/chinesejie/paho-for-android


Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

@chinesejie
Copy link
Author

Could you describe what the issue is? I hope to take more test on it.

@JesseFarebro
Copy link
Owner

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants