Ports for TLS and non-TLS Interfaces #132
Description
Would you consider adjusting the mqtt section of the configuration file so more than one listener of a type could be requested where any given listener could explicitly use or not use the TLS configuration?
I have a situation where some clients will use TLS but for others, such as embedded devices, it would be nice to point them at an unsecured port.
Currently, if TLS configuration exists it is applied everywhere.
Perhaps instead of mqtt.tcp, mqtt.ws, etc, an array of mqtt.listeners where a listener is a struct that contains type, port, and tls boolean?
Since the project is so well organized and easy to read I was able to add my own quick fix with a few lines of code, but it's not how I would do it in an official capacity.
If there is no objection to adding this I would be happy to implement it as described above and submit a pull request.
Thanks!