Marcelo
Marcelo
For background see https://lists.boost.org/Archives/boost/2024/10/258146.php. > Oh cool. I played around with Redis the other day and failed to figure this out. Yes, not-logging by default really hurts adoption, at least...
See https://github.com/boostorg/redis/issues/205#issue-2432081055 for motivation.
While playing with valgrind massif I produced a condition where `async_receive2` completes with zero messages. I noticed this because `flat_tree::get_total_msgs()` was returning `0`. From looking at the code I could...
We currently perform one dynamic allocation for the `notifier` and one for the `multiplexer::elem` https://github.com/boostorg/redis/blob/00f3ec9b78454211c7b8d461b11411c8b1ef1ad3/include/boost/redis/connection.hpp#L193-L194 It looks like it is possible to put these two data structures into a single...
Buffer rotations are unacceptably high at the moment when data read from the socket contain multiple messages. For example, our stress test outputs ``` $ ./test/boost_redis_test_conn_echo_stress Bytes received (response): 3210147...
As I work on the `generic_flat_response` implementation I noticed that `async_receive` and its sync counterpart `receive` are too cumbersome and inefficient to work with. At the moment the general for...
For example ```cpp request req; req.push("ping", "abc"); req.push("ping", "def"); response res; co_await conn.async_exec(req, res); ``` Allowing internal adapter code is wrong, the library should communicate an error with which the...
As described in [this](https://github.com/boostorg/redis/issues/246#issuecomment-2927909878) comment there is an easy way to reduce latency of write operations > We can avoid copying payloads [here](https://github.com/boostorg/redis/blob/0c8c6fcc095ff103e9adda708c1efb06fabfe08d/include/boost/redis/impl/multiplexer.ipp#L158) when the connection has only one ongoing...