boost/redis
2
0
Fork 0
mirror of https://github.com/boostorg/redis.git synced 2026-01-19 04:42:09 +00:00
Code Issues Projects Releases Wiki Activity

Changes cancel_on_connection_lost default to false and deprecates it (#329)

Browse Source 
* Changes cancel_on_connection_lost default to false
* Deprecates cancel_on_connection_lost and cancel_if_not_connected
* Fixes a TODO in test_conn_exec_cancel

close #323
This commit is contained in:
Anarthal (Rubén Pérez)
2025-10-11 13:30:41 +02:00
committed by GitHub
parent 35fa68b926
commit 28ed27ce72
4 changed files with 19 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/modules/ROOT/pages/cancellation.adoc
View File

@@ -62,8 +62,8 @@ The `SET` command is idempotent, while `INCR` is not.
If you know that a `request` object contains only idempotent commands,
you can instruct Boost.Redis to retry the request on failure, even
if the library is unsure about the server having processed the request or not.
You can do so by setting `cancel_if_unresponded` and
`cancel_on_connection_lost` in xref:reference:boost/redis/request/config.adoc[`request::config`]
You can do so by setting `cancel_if_unresponded`
in xref:reference:boost/redis/request/config.adoc[`request::config`]
to false:
[source,cpp]
@@ -71,7 +71,6 @@ to false:
// Compose a request
request req;
req.push("SET", "my_key", 42); // idempotent
req.get_config().cancel_on_connection_lost = false; // Don't cancel the request if the connection is lost
req.get_config().cancel_if_unresponded = false; // Retry the request even if it was written but not responded
// Makes sure that the key is set, even in the presence of network errors.