Swee Tat Lim

Use of redis.UniversalClient instead of Client for OpenConnectionWithRedisClient

2

redis-go now provides a UniversalClient for connection. I will suggest removing the dependency on redis.Client, and replace that with redis.UniversalClient which covers the various aspects of client management from rmq.

I want an SSE connection to be established for reading messages from the server, with predefined controls for circuit breaking. Do you have something that can work?

Problem: When I use hystix client, I want an ability to use a framework like `https://github.com/h2non/gock` to mock traffic for my testing purposes. gock provides a means of doing roughly...

This is a bit of mess to try to get M.opts to be the standard across the configurations. I wanted the ability to allow users to specify runner config parameters...

- changing the dockerfile initial image to golang:alpine - Change the workdir to /source and moved the files into /source - Moved the collective starting parameters into /source directory

Allow the building of the application as a static binary