diff options
| author | Maurice Kalinowski <maurice.kalinowski@qt.io> | 2019-07-02 12:46:38 +0200 |
|---|---|---|
| committer | Maurice Kalinowski <maurice.kalinowski@qt.io> | 2019-07-02 16:01:57 +0200 |
| commit | edb2ca969c53d580d1f853709278d15f1774da70 (patch) | |
| tree | fd64ef4da5af4aa791b81100c2c663161a51828d | |
| parent | d25a0abe78648b0e2fbf4ac6d4e3b325e88dfb42 (diff) | |
Fix documentation about keepAlive
Initially the keepAlive was considered to be specified in ms to more
match the Qt API. However, no server allows this granularity and the
specs also state seconds. Internally it was using this pattern already.
Change-Id: I0a25d1ef636c2b909997223c631dc248b613536c
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
| -rw-r--r-- | src/mqtt/qmqttclient.cpp | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/src/mqtt/qmqttclient.cpp b/src/mqtt/qmqttclient.cpp index 0ea0f1e..39f3701 100644 --- a/src/mqtt/qmqttclient.cpp +++ b/src/mqtt/qmqttclient.cpp @@ -90,9 +90,7 @@ Q_LOGGING_CATEGORY(lcMqttClient, "qt.mqtt.client") frequent updates to propagate it can still be reached. The interval between those updates is specified by this property. - The interval is specified in milliseconds. However, most brokers are not - capable of using such a high granularity and will fall back to an interval - specified in seconds. + The interval is specified in seconds. */ /*! |