Opportunity of connection via unix socket. #95
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
r-kovalenko
force-pushed
the
patch-unix-sockets
branch
from
d234020
to
33ef2f2
Compare
When we have option useSocket, but the value is different from true and we cant get connection class - use default connection class.
r-kovalenko
force-pushed
the
patch-unix-sockets
branch
from
33ef2f2
to
e1be8a0
Compare
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.
Now we have class that we could use for connection to redis via Unix Socket. Its useful when we have local instance of redis (could be slave) for fast data exchanging without newtwork delay.
When we have option useSocket, but the value is different from true we couldn't have got connection class.