Skip to content

Conversation

danjenkins
Copy link

I was unable to attach an onError handler to the raw redis connection, so when we lost connectivity to redis, the node app would just kick up a fuss, I wanted to be able to deal with that how I wanted. While I was at it, I added the possibility of listening for onReady so that you can also have your own logic for when the connection is ready.

I also made it so that when on error gets called, we pass back the raw connection so that you can say, listen for ready again and know that you've reconnected.

@hongkongkiwi
Copy link

This is fantastic, that was one of my concerns is that if the Redis server went down temporarily it would take our server down with it.

I hope we can merge this into the 0.9 code base !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants