Marcelo

> as long as we provide a way to type-erase the adapter type. The internal connection type (`connection_base`) uses a ```cpp std::function; ``` to type-erase it. > Moving forward with...

A simpler overview about how the parser works can be seem [here](https://github.com/boostorg/redis/blob/a4d2bb983dba0aac546a41d04f6af94568e817fc/include/boost/redis/resp3/serialization.hpp#L112) (which is only suitable for whole messages) and it usage is shown [here](https://github.com/boostorg/redis/blob/a4d2bb983dba0aac546a41d04f6af94568e817fc/test/test_low_level_sync_sans_io.cpp#L28).

I can reproduce and will investigate soon. As a workaround, instead of using `boost::redis::connection` you can use an executor other that the default, for example ```cpp using executor_type = net::io_context::executor_type;...

By the way, boost has a MySql connector: https://www.boost.org/doc/libs/1_82_0/libs/mysql/doc/html/index.html which might be useful if you would like to avoid OZO.

Hi, I am aware of this problem but still don't have a solution. It first appeared when Boost.Redis was integrated into boost and that boost header got automatically added to...

This could be fixed after my last merge on develop where I remove the use of associated allocator.

Reconnection is unfinished for ssl. I am think about adding a callback that will be called after [this](https://github.com/boostorg/redis/blob/7caea928affde85146b738eb456d4772a410f721/include/boost/redis/connection.hpp#L55). Until there you can disable reconnection by setting the [this](https://github.com/boostorg/redis/blob/7caea928affde85146b738eb456d4772a410f721/include/boost/redis/config.hpp#L80) to zero...

I have opened a PR with the fix. Please have a look.

@anarthal pointed out that if you set your options on the `ssl::context`, all subsequent connections created from it will use the new configuration. That would make my PR above unnecessary....

Yeah it is missing. I will add one.