feat: implement the redis features of subscribe, psubscribe, spublish #4746
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.
Issue #4708, #4653.
Why add cmd interface
The reason why I add
Subscribe
andPSubscribe
interface is that every time I need to useSubscribe/PSubscribe
, I have to use switch case to change the type of redis client.Discuss how to encapsulate the subscribe and psubscribe
PubSub
type and user handle with its needsSPublish
SPublish
is the method of sending message to a sharding channel. In the other words,Publish
will broadcast the whole cluster to publish, butSPublish
won't.It cost less network but it only support redis above v7.0. When I test with the miniredis lib, it didn't support it...