Timeline for MQTT always connected and 4G data load
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 5, 2018 at 12:31 | vote | accept | Mark | ||
| Jun 5, 2018 at 12:09 | comment | added | hardillb | @Mark The fact that only Ping packets are the only thing sent if no messages are being sent are implied by the sentences after this table: docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/… | |
| Jun 5, 2018 at 8:08 | comment | added | xwoker | Just wanted to point out that the suggestion to introduce a local broker makes even more sense if we are not talking about 2 bytes per message but because of TCP/IP it's more like 42 bytes per message so its 84 for one ping cycle. | |
| Jun 5, 2018 at 8:02 | comment | added | Mark | @xwoker I guess the overhead to send the PINGREQ packets would be small as well. The main point is to prove that only PINGREQ packets are sent when clients are not publishing anything. | |
| Jun 5, 2018 at 7:48 | comment | added | xwoker | Don't we have to consider the underlying protocol that is used to transfer the PINGREQ packets in order to consider the data used on the network? Then we are talking about a little more data that would be used... | |
| Jun 5, 2018 at 6:55 | comment | added | hardillb | The keep-alive timer is reset every time a packet is received, I can't remember where in the spec this is said off the top of my head | |
| Jun 5, 2018 at 6:53 | comment | added | Mark | Anyway, I knew the behavior of PINGREQ/RESP, but what I didn't find is that they are the only packets exchanged when there is no real activity (i.e. initiated by the user applications). I could infer this from your answer, but the docs doesn't seem to explicitly state that. | |
| Jun 5, 2018 at 6:50 | comment | added | Mark | Using an intermediate broker is a good advice, even I'm afraid it doesn't fit in this specific case. Useful to know, though! | |
| Jun 5, 2018 at 6:42 | history | answered | hardillb | CC BY-SA 4.0 |