You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/resp2-to-resp3-replies.md
+18-15
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,28 @@
1
1
---
2
-
title: "RESP2 to RESP3 replies migration guide"
2
+
title: "RESP2 to RESP3 reply migration guide"
3
3
linkTitle: "RESP2 to RESP3 migration"
4
4
weight: 4
5
-
description: RESP2 to RESP3 replies reference for clients developers
5
+
description: RESP2 to RESP3 reply reference for client library developers
6
6
aliases:
7
7
- /topics/resp2-to-resp3-replies/
8
8
---
9
9
10
-
In the journey from RESP2 to[RESP3](https://redis.io/docs/reference/protocol-spec/), one of the primary motivations was to streamline the developer experience by simplifying response parsing.
11
-
Over time, it became evident that developers frequently performed specific data transformations on RESP2 replies, which required hardcoded transformations per command.
12
-
Addressing these transformations directly at the protocol level reduces clients' overhead and ensures a more consistent and efficient replies handling process.
13
-
This documentation provides a reference for developers to migrate their clients from RESP2 to RESP3.
10
+
The primary motivation for creating the[RESP3](https://redis.io/docs/reference/protocol-spec/) protocol, the successor to RESP2, was to streamline the developer experience by simplifying response parsing.
11
+
It became evident that developers frequently performed specific data transformations on RESP2 replies, which required hardcoded transformations for each command.
12
+
Addressing these transformations directly at the protocol level reduces client overhead and ensures a more consistent and efficient reply-handling process.
13
+
This documentation provides a reference guide to help developers migrate their clients from RESP2 to RESP3.
14
14
15
-
### Command Replies Comparison
16
-
- RESP3 introduces many new [simple types and aggregates]((https://redis.io/docs/reference/protocol-spec/#resp-protocol-description)).
17
-
The following tables compare only commands with non-trivial changes in replies, primarily for new aggregates introduced in RESP3 that require major changes in the client implementation.
15
+
**Note**:
16
+
> Each of the Redis base command manual pages now includes both RESP2 and RESP3 responses.
17
+
18
+
### Command replies comparison
19
+
- RESP3 introduces many new [simple and aggregate reply types]((https://redis.io/docs/reference/protocol-spec/#resp-protocol-description)).
20
+
The following tables compare only commands with non-trivial changes to their replies, primarily for new aggregates introduced in RESP3 that require major changes in the client implementation.
18
21
- The types are described using [“TypeScript like” syntax](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html):
19
-
-`[a, b]` stands for [a tuple](https://www.typescriptlang.org/docs/handbook/2/objects.html#tuple-types) where we know the exact number of elements and types at specific positions.
20
-
-`Array<a>` stands for [an array](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#arrays) where we know the type of elements but not the number of elements.
22
+
-`[a, b]` stands for [a tuple](https://www.typescriptlang.org/docs/handbook/2/objects.html#tuple-types) where the exact number of elements and types at specific positions are known.
23
+
-`Array<a>` stands for [an array](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#arrays) where the type of elements is known but not the number of elements.
0 commit comments