Showing content from https://github.com/StackExchange/StackExchange.Redis/issues/945 below:
Track and reflect nomenclature changes re replication (master/slave) · Issue #945 · StackExchange/StackExchange.Redis · GitHub
Potential server-side changes re terminology of master/slave.
As those changes become more concrete:
- client lib MUST: be aware of (i.e. work correctly with) any server-side changes to commands and return values, including any version-specific semantics
- client lib SHOULD: use preferred nomenclature where possible - happy to add new methods/enums etc and add
[Obsolete(..., false)] to the old
- documentation SHOULD: use preferred nomenclature throughout (perhaps with "replica (historically: 'slave')" clarifications)
see https://github.com/antirez/redis/issues/5335
open question: does this impact the "no more 1.* builds" decision?
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4