Closed cartertinney closed 1 year ago
It's ok to start, but I was expecting to see the code splitted into three layers:
- Common. Helper funcions using in all samples, such as connecting with settings
- Binders. Encapsulate topics and serialization formats
- Clients. Just using the binders without any mqtt concepts
This kind of division is not very viable in Python due to the structure of this repository, and limitations of the Paho library. As a result we have elected to implement samples directly with raw Paho instead. I can explain the technical details in depth if you wish, please just reach out.
However, I can assure you that the pattern you desire will be reflected in the real SDK lite implementation, which we have already begun work on. It just is hard to backport that solution to these samples.
Raw Paho MQTT implementation of command with minimalist infrastructure