mqtt_cpp
mqtt_cpp copied to clipboard
redboltz
I think that mqtt_cpp should document (with the noexcept keyword) the parts of the mqtt_cpp code that are exception safe. For example, most of the member functions in property.hpp, and...
I discussed offline message storing before. I searched issues but not found. Maybe the discussion is held at the comment on the some PR. So let me explain what is...
Brief description of features: 1) Ability to call async_client::async_subscribe() before async_client::async_connect(). 2) Ability for mqtt_cpp to automatically register Subscription Identifier numbers with the broker, and manage the use of them...
client runtime checking of clientID value is done after establishing a socket with TLS or WebSockets
Instead, the client ID should be checked (if enabled) before the socket is established. This way, if the client is aware that it's going to use an invalid ID, it...
Hi @redboltz, I read the issue #338 In your explanation, you mention that life_keeper is move captured, which is a good idea and lets suggest me that I could put...
Have you considered adding integration tests on continuous integration (travis CI, etc) that has mqtt_cpp connect with other implementations like mosquitto?
I think it would be an improvement to write a short paragraph explaining why mqtt_cpp is for C++14, instead of either C++11, or C++17 (or whatever other version someone may...
E.g., in my situation, I'm not interested in MQTTv3 compatibility. As a result, it would be convenient for me to be able to turn off v3 compatibility at compile time....
Right now we have a very large amount of functionality bundled into the same class, and I think we could enhance understandability by breaking this class into two parts. EndpointBase
Currently endpoint uses a mutex and a monotonic increasing packet id. There are other possible packet id strategies. For example: An implementation with a known-ahead-of-time number of threads, might want...