Reserving field names in the uri specification grammar #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@redis/client-developers I know you're interested. |
This was referenced Feb 9, 2023
itamarhaber
approved these changes
Feb 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change aims to help solidify the URI grammar used in communicating redis connection URLs. Specifically, this covers reserving fields, creating the first reserved field protocol.
The purpose of this change is to make it possible for Redis clients to align on how they might configure themselves, to request a specific version of the RESP protocol. This encourages no server-side change of behaviour, and serves only to ensure that Redis client configurations can begin to standardize on common field names.