rweilbacher / mqtt.jl Goto Github PK

This means the user wouldn't have to sleep at the end of his file. Also update examples once this is done

Currently there is a general on_msg callback and the user has to parse the topic themselves

Once there is a julia update. It's already broken on nightly

import Base.Dates is now deprecated

Mosquitto responds to the first pingreq packet with a pingresp but then just closes the socket. This also happens on localhost and if pingreq packets get sent more often than one second manually.

Currently it is an array that is slightly non transparent

topic name and qos

Also remember to change documentation.

so Client(on_message, ping_timeout = 60)

Once the new Julia update comes. It's already broken in nightly

It's currently Array::UInt8 which means user has to format payload himself.

Only reconnect if reconnect flag in client is set and it was an ungraceful disconnect. Maybe use exponential backoff.

MQTT fails to build in Julia Version 1.1.0

julia> using MQTT
[ Info: Precompiling MQTT [572a640e-f7b4-11e8-215e-e1fc97963a1b]
WARNING: could not import Base.connect into MQTT
ERROR: LoadError: LoadError: UndefVarError: Nullable not defined
....

on_connect, on_disconnect, on_subscribe, on_unsubscribe

During installation I get the error

WARNING: could not import Base.connect into MQTT
ERROR: LoadError: UndefVarError: Nullable not defined

What to do now?

So publish() with QOS 2 only returns once Pubcomp has been received.

Or use enum instead

Currently its is all manual for each packet there is probably a better solution.

If we keep getting packages from the server and in_flight is never empty we disconnect after a specific timeout

Don't use generic exceptions

Is this project still alive? If not, is there a way to revive it?

Currently it just returns arbitrary data. The connect future for example puts a string into it's future if it failed or the session present int if it succeeded. That makes it pretty hard to check for success and isn't very intuitive. Maybe also put success or failure into the future where currently "nothing" is being returned on success.

The changes made should then also be added to the documentation. under the respective synchronous / asynchronous sections.