Marcelo
Marcelo
Sorry for opening an issue for this, I did not find any better means of contacting you. I would like to invite your community to write a review for a...
Since reconnection has been disabled and the acl prohibits selecting a database index, we should not have to call `cancel` on `async_exec` completion.
The example below will crash with Boost.Async ```cpp #include #include #include #include #include namespace async = boost::async; namespace asio = boost::asio; using boost::redis::request; using boost::redis::response; using boost::redis::config; using boost::redis::connection; async::detached...
No elements of the adapter module appears in the public API so it should be moved in the detail namespace and directories. Some parts of it belong into `redis/detail` while...
The `generic_response` adapter should not set an error in the `result` but let the caller check in each `node` whether an error occurred. Otherwise we cannot process responses to more...
At the moment if the response to a health-check does not come under the time specified by the user, the connection will timeout. This is not flexible enough to deal...
At the moment Aedis expects response for commands except those listed in `has_push_response`. This function must be extended.
A coroutine based implementation of `asio::async_read_until` should be more efficient than the Asio version since it can use symmetric-transfer to avoid a reschedule operation when the buffer already contain the...
Async could provide a health check as an example since it is simple enough to implement and useful in general. Constraints * Ping the server periodically (can be a http...