Takatoshi Kondo
Now I've learned how to add mqtt_cpp to vcpkg. Currently, mqtt_cpp contains boost/beast as the submodule. boost.beast will be merged the next release of the boost libraries. I think that...
I will take a look this. Please wait a moment.
I think that it is nice to have. Avoiding parse conditionally is valuable. I'm not sure how this mechanism work with buffer life time management. Packet format is like as...
I think that there are three cases: |Case|Condition|Property Cursor Friendly| |---|---|---| |1|Read whole packet all at once|yes| |2|Read all properties all at once|yes| |3|Read individual property step by step|no| I...
I'm not sure where is the goal of your idea. But I want to keep the mechanism `v5::property_variant`. I think that your idea is NOT removing it. > 1) No...
I'd like to know the impact of existing APIs. e.g. `publish()` family, handlers.
Indeed, I understand your approach. Keeping the interface of existing APIs is nice. And breaking change of handlers is acceptable. > If the entire packet is so small that it...
I think that separating PacketId management mechanism is a good idea :)
mqtt_cpp is originally focused on C++11. C++14 includes some kind of bug fix of C++11. The position of C++14 is minor fixed version of C++11. I migrate to C++14. C++17...
In addition mqtt_cpp has https://github.com/redboltz/mqtt_cpp/wiki/Persistence functionality. If the publish message should be stored, then call persistent handler. This functionality should be integrated well with offline message storing.