Re: async-mqtt5 review

From: Peter Dimov (pdimov_at_[hidden])
Date: 2024-10-25 15:41:37

Christian Mazakas wrote:
> I think in many ways, having a clean sans-I/O layer will probably actually make
> the I/O parts cleaner. It works really well for TLS and HTTP. I don't see why
> MQTT is different.

Assuming that your goal is to get a sans-io MQTT library in Boost, the question
reduces to which path will be more likely to produce this outcome:

1. Accepting an I/O MQTT library first
2. Rejecting the I/O MQTT library

While (under different circumstances) there exist valid arguments in favor
of (2), in this case I think that (1) is a clear winner because the other three
cases we can observe have all taken it.