On Mon, Oct 28, 2024 at 8:13 AM Darryl Green via Boost < boost@lists.boost.org> wrote:
A high level library that can do all this needs a tunable "QoS" in the general sense (not just the selection of one of 3 values for an MQTT parameter). A low level library can legitimately claim its out of scope. This library has high level features but appears to lack some tunability (but that could be user ignorance on my part) and also access to low level features to allow the user to take responsibility for these issues. That needs addressing.
I think this frames it quite well. In the wild, there's a lot of different requirements and there's even more approaches one can take. I think a well-coded low-level interface gives users the flexibility they need and I think the way you described it, Darryl, is perfect. - Christian