All Versions
11
Latest Version
Avg Release Cycle
124 days
Latest Release
1323 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v0.11 Changes
September 04, 2020- [feature, possible breakage] add BOOST_ASIO_NO_DEPRECATED definition for better support boost v1.74 and modernize boost API usage
-
v0.10 Changes
May 13, 2020- 🛠 [bugfix] avoid access to protected destructor (c++17 compatibility)
-
v0.09 Changes
December 07, 2019- 🛠 [bugfix] critical bug in protcol serialization on empty values
-
v0.08 Changes
August 10, 2019- 😌 relaxed c++ compiler requirements: c++11 can be used instead of c++14
-
v0.07 Changes
April 27, 2019- ✅ minor parsing speed improvements (upto 10% in synthetic tests)
- 🛠 fix compilation issues on boost::asio 1.70
- make it possible to use
DynamicBuffer_v2
(dynamic_string_buffer, dynamic_vector_buffer)
from boost::asio 1.70 in addition tostreambuf
.DynamicBuffer_v1
was actually never
👌 supported bybredis
- [API breakage]
boos::asio::use_future
cannot be used withbredis
andboost::asio
👀 priorv1.70
(see issue). If you need
⬆️use_future
then either upgrade boost::asio or use previousbredis
version.
-
v0.06 Changes
April 14, 2019- the
parsing_policy::drop_result
was documented and made applicable in client code - ⚡️ updated preformance results
- 🛠 fixed compliation warnings (
-Wall -Wextra -pedantic -Werror
) - ➕ added shortcut header
include/bredis.hpp
- ➕ added redis-streams usage example
- ➕ added multi-thread example
- the
-
v0.05 Changes
January 28, 2019- 🛠 fixed level 4 warning in MSVC
- 🛠 fixed compilation issues on archlinux
- 👌 improved documentation (numerous typos etc.)
-
v0.04 Changes
January 25, 2018- [bugfix] removed unneeded
tx_buff.commit()
onasync_write
which corrupted buffer
- [bugfix] removed unneeded
-
v0.03 Changes
July 30, 2017- 👌 improved protocol parser (no memory allocations during input stream validity check)
- more detailed information in
protocol_error_t
- ➕ added async
incr
speed test example 📜 [small API breakage]
positive_parse_result_t
was enriched with parcing policy;
📜 now instead ofpositive_parse_result_t<Iterator>
should be written:using Policy = r::parsing_policy::keep_result;using result_t = r::parse_result_mapper_t<Iterator, Policy>;
[small API breakage]
protocol_error_t
instead ofstd::string what
member
now containsboost::system::error_code code
-
v0.02 Changes
June 24, 2017- ➕ added windows support
- ➕ added coroutines & futures support
- 👍 generalised (templated) buffer support
- 🔄 changed return type: instead of result of parsing just result markers are returned, extraction of result can be done as separate step
- ⬇️ dropped queing support (queuing policy should be implemented at more higher levels)
- ⬇️ dropped subscription support (can be implemented at higher levels)
- ⬇️ dropped internal buffers (can be implemented at higher levels)
- ⬇️ dropped explicit cancellation (socket reference can be passed to connector, and cancellation
can be done on the socket object outside of the connector)