forked from sreeix/redis-proxy
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implementing the streaming response back to client
Instead of using a redis client wrapped with the raw protocol, we now just use a simple tcp connection for handling request/response. There is one extra status check redis connection that is used to track the redis status and issue info/slave of etc commands This means * that Large responses are handled correctly * There is no conversion from one socket to another. Thus a performance boost esp for large responses. * Large number of events hooked up have been removed. There is still some cruft remaining with the read part of the protocol. Where a stream would help as well.
- Loading branch information
Showing
3 changed files
with
15 additions
and
18 deletions.
There are no files selected for viewing
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
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
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