This repository was archived by the owner on Dec 24, 2022. It is now read-only.
Made private send methods in RedisNativeClient protected#115
Merged
Conversation
Making certain methods protected allows access to low level IO of redis client for fine-tuned extension of client via inheriting RedisClient class.
mythz
added a commit
that referenced
this pull request
Dec 13, 2012
Made private send methods in RedisNativeClient protected
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Making certain methods protected allows access to low level IO of redis client for fine-tuned extension of client via inheriting RedisClient class. I think it would be better to set these methods as protected instead of private so that people who need more low level communication with Redis database have a chance to implement them by inheriting RedisClient class.