AsyncSocket | simple asynchronous Client/Server Socket | Reactive Programming library

I'm trying to convert a synchronous flow in Python code which is based on callbacks to an A-syncronious flow using asyncio. Basically the code interacts a lot with TCP/UNIX sockets. It reads data from the sockets, manipulates it to make decisions and writes stuff back to the other side. This is going on over multiple sockets at once and data is shared between the contexts to make decisions sometimes.

EDIT :: The code currently is mostly based on registering a callback to a central entity for a specific socket, and having that entity run the callback when the relevant socket is readable (something like "call this function when that socket has data to be read"). Once the callback is called - a bunch of stuff happens, and eventually a new callback is registered for when new data is available. The central entity runs a select over all sockets registered to figure out which callbacks should be called.

I'm trying to do this without refactoring my entire code and making this as seamless as possible to the programmer - so I was trying to think about it like so - all code should run the same way as it does today - but whenever the current code does a socket.recv() to get new data - the process would yield execution to other tasks. When the read returns, it should go back to handling the data from the same point using the new data it got.

To do this, I wrote a new class called AsyncSocket - which interacts with the IO streams of asyncIO and placed the Async/await statements almost solely in there - thinking that I would implement the recv method in my class to make it look like a "regular IO socket" to the rest of my code. So far - this is my understanding of what A-sync programming should allow.

Now to the problem :

My code awaits for clients to connect - when it does, each client's context is allowed to read and write from it's own connection. I've simplified to flow to the following to clarify the problem:

Boost Version : 1.68

C++ Standard : C++17

Development Platform : MSVC 2017

Operating System : Windows 10 Professional

PC Architecture : x64

I am using Boost::Asio to create an asynchronous TCP connection. During first successful connection everything works properly. Due to certain problem it socket break it attempts to re-connect and that time I get the run-time error. Even though I get run-time error the program still is able to receive data.

At first I was attempting to reconnect the socket in my main function's while (infinite) loop (main thread), but I was getting the error. I was getting error in

D:\vcpkg\installed\x64-windows\include\boost\asio\detail\impl\win_iocp_io_context.ipp

I write a AsyncSocket that use QTcpSocket to work with some servers. They (servers) were wrote long time ago and I have no ability to change them.

So, the problem is the lack of readyRead signal if server could not recognize the message (because it did nothing with default message type). I think it is the server problem, because it should response anyway... but it is not my own code and I have to use it like it is.

I thought to use QAbstractSocket::waitForReadyRead(int msecs) but found in Qt documentation (the end of the 'details' section):

Note: We discourage the use of the blocking functions together with signals. One of the two possibilities should be used.

So, I am a bit confused why I should not use blocking method like this:

I'm looking through some low-level Objective-C code and I see this:

I've been working on a server that expects data to be received through a buffer. I have an object which is defined like this and some procedures that modify the buffer in it: