Re: [mosquitto-dev] connect_async problem and advice publish/dedconnect

[Mikkel Kirkgaard Nielsen <miki@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

On 2015-04-29 18:09, Roger Light wrote:
> I think it could read more clearly, I'll update it.

If your are messing about in mosquitto.h documentation language
anyway could you please also consider fixing the misrepresented
meaning of the keepalive argument on the mosquitto_connect_*
functions?

"keepalive - the number of seconds after which the broker should
send a PING message to the client if no other messages have been
exchanged in that time."

This wording shifts the keep alive responsibility and reverses the
PINGREQ/PINGRESP direction, refer to [MQTT-3.1.2-23] and [MQTT-3.1.2-24].

This puzzled somebody I know before they got on to reading the
specification and code ;).

It might also be beneficial for library users to mention that the
keepalive value (of type int in the C API) is actually limited by
the protocol to 16 bit when communicated to the broker
(internally represented as uint16_t in struct mosquitto).


I got some other minor documentation diffs stashed away, I'll try
to clean them up and contribute.

- -- 
    Mikkel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJVQfMLAAoJEJ2luFWzaTSatw4H/0tW7hX/RL9jL7CHFbzQFi7f
LvHnlmfBtCLEy1OYVnjBtAG1A/pkBwWhQL5sYruiq88liQvwnUMbRv3/slYlKMDR
exlj0fyNxAZbOYqD54aPmUPpQTXHTvXh1jRLJc8wh28BTgV0/x6DnW1LAHypj/72
XmgmVPH38LiLfsRxXvWDvHIxhVX4JB4SrHvbO1/8g2gLx7+hsUK9xt8IgdmxisNt
gC1SsvLyckEgRMVNUAslT/hWpinJfrLjZnJYIoKCtuGxL9YJgT3DsC/QDVcuPbmy
LTABHOKoEt0xqbLlaUxsqOx68fsqWTfnx35aukkQ2Hsn21IsnnBqQRVnTQ1WK58=
=9rul
-----END PGP SIGNATURE-----