From 212b8393a5b57d92b04b8c70a4ee8d7eb0dd7482 Mon Sep 17 00:00:00 2001 From: Ruben Perez Date: Sun, 29 Mar 2026 14:56:08 +0200 Subject: [PATCH] Fixes broken links to Redis docs close #398 --- README.md | 6 +++--- doc/modules/ROOT/pages/benchmarks.adoc | 2 +- doc/modules/ROOT/pages/comparison.adoc | 2 +- doc/modules/ROOT/pages/pushes.adoc | 2 +- include/boost/redis/request.hpp | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index dadb563ca..fae5cc684 100644 --- a/README.md +++ b/README.md @@ -82,9 +82,9 @@ The roles played by the `async_run` and `async_exec` functions are: Redis servers can also send a variety of pushes to the client. Some of them are: -* [Pubsub messages](https://redis.io/docs/manual/pubsub/). -* [Keyspace notifications](https://redis.io/docs/manual/keyspace-notifications/). -* [Client-side caching](https://redis.io/docs/manual/client-side-caching/). +* [Pubsub messages](https://redis.io/docs/latest/develop/pubsub/). +* [Keyspace notifications](https://redis.io/docs/latest/develop/pubsub/keyspace-notifications/). +* [Client-side caching](https://redis.io/docs/latest/develop/clients/client-side-caching/). The connection class supports server pushes by means of the `connection::async_receive2` function, which can be diff --git a/doc/modules/ROOT/pages/benchmarks.adoc b/doc/modules/ROOT/pages/benchmarks.adoc index 12ef797c6..28c8a3644 100644 --- a/doc/modules/ROOT/pages/benchmarks.adoc +++ b/doc/modules/ROOT/pages/benchmarks.adoc @@ -74,7 +74,7 @@ in the graph, the reasons are with the other benchmarks without making them look insignificant. I don't know for sure why it is so slow, I suppose it has something to do with its lack of automatic - https://redis.io/docs/manual/pipelining/[pipelining] support. + https://redis.io/docs/latest/develop/using-commands/pipelining/[pipelining] support. In fact, the more TCP connections I launch the worse its performance gets. diff --git a/doc/modules/ROOT/pages/comparison.adoc b/doc/modules/ROOT/pages/comparison.adoc index c8542b591..4e79e2e3d 100644 --- a/doc/modules/ROOT/pages/comparison.adoc +++ b/doc/modules/ROOT/pages/comparison.adoc @@ -14,7 +14,7 @@ compatible with the Asio asynchronous model. As I made progresses I could also address what I considered weaknesses in other libraries. Due to time constraints I won't be able to give a detailed comparison with each client listed in the -https://redis.io/docs/clients/#cpp[official list]. +https://redis.io/docs/latest/develop/clients/[official list]. Instead, I will focus on the most popular pass:[C++] client on github in number of stars, namely: https://github.com/sewenew/redis-plus-plus[] diff --git a/doc/modules/ROOT/pages/pushes.adoc b/doc/modules/ROOT/pages/pushes.adoc index efbe7a4ec..cae1187d6 100644 --- a/doc/modules/ROOT/pages/pushes.adoc +++ b/doc/modules/ROOT/pages/pushes.adoc @@ -178,7 +178,7 @@ of this page. Pub/Sub `message` and `pmessage` pushes. Other push types are skipped, including: * Subscribe/unsubscribe confirmations. -* https://redis.io/docs/latest/develop/reference/client-side-caching/[Client-side caching] +* https://redis.io/docs/latest/develop/clients/client-side-caching/[Client-side caching] invalidation messages. * Output of the `MONITOR` command. diff --git a/include/boost/redis/request.hpp b/include/boost/redis/request.hpp index c6a4ef21b..b1e02a56e 100644 --- a/include/boost/redis/request.hpp +++ b/include/boost/redis/request.hpp @@ -46,7 +46,7 @@ struct pubsub_change { * * A request is composed of one or more Redis commands and is * referred to in the redis documentation as a pipeline. See - * for more info. + * for more info. * * For example: *