Takatoshi Kondo
> > @shantanu1singh , could you try #673 ? > > As I commented at [#663 (comment)](https://github.com/redboltz/mqtt_cpp/pull/663#issuecomment-703384855), GnuTLS support is implemented by boost asio and boost beast, not mqtt_cpp. >...
> > > I guess that beast doesn't need to care about TLS because it is hidden underlying layer from the beast. > > > > > > I was...
@shantanu1singh, does #673 work well ?
Could you post a new PR to fix #673 ? The target branch is add_alt_tls_support.
Thank you for reporting the issue. I guess that you mean https://github.com/redboltz/mqtt_cpp/blob/9d078a329f79ccee83a1e1aa7adc8a58af1a9f03/include/mqtt/endpoint.hpp#L6052 The member `session_present` is assigned at https://github.com/redboltz/mqtt_cpp/blob/9d078a329f79ccee83a1e1aa7adc8a58af1a9f03/include/mqtt/endpoint.hpp#L6093 But it is one of case clause. Even if `connack_phase::header` becomes...
I just create #762. Some of invalid combination of flags and properties can be checked without extra checking loop. I didn't design it yes but I guess it works well.
Let me clarify about the completion token. 1. The client codes that call the existing async APIs that have void return type with async_handler_t parameter don't need to update. Is...
One more thing. We need to check Boost.Beast support the completion tokens the same as Boost.Asio.
This PR is NOT ready to merge. Still working.
1st step done. The next step is adding Asio CompletionToken for async_* APIs.