Thijs Schreijer

I also added logging (using LuaLogging), not required for library use, but is required when running the tests on this branch. (actually had to write a [new LuaLogging appender](https://github.com/lunarmodules/lualogging/pull/14) to...

yes, a bit more than anticipated 😄 anyway, I don't expect it to be fully functional yet. Just starting to implement some devices, that will probably be the proof-of-the-pudding. (it...

🎉 all green now 😄

@xHasKx some review comments would be nice if you can spare some time. I need to review the nginx examples, as they probably suffer from the same problems as the...

> Sync loop can be used in the simplest mqtt case - connect, subscribe, publish command, receive answer, disconnect. This zero-depenndence scenario have to be preserved. The differences between the...

not sure where this should go, it's now in `init.lua`. Should it go into `client.lua` maybe? possibly every subscription could be parsed by the client, and the parsed results passed...

> Actually I'm not sure these validation functions is required at all. agreed they are not, and I would not implement them in the client itself. They are just convenience...

> `client:add_msg_handler(topic_mask, callback)` similar to the client:subscribe() method, adding not a SUBACK callback, but a PUBLISH handler called only for messages with matching topic. yeah, I was thinking along the...

exactly, but then you'd always need 2 handlers, a generic one that does the ACK, and another one matching a specific topic mask. Still learning on the MQTT stuff; why...

> For example, MQTT can be used to distribute some tasks between workers, and if worker can't handle some task - it may not send ack to indicate failure (in...