I notice that after entering redisWorker and registerDoRedis, there is a redisConnect. However, before there is a redisClose before leaving redisWorker, but no redisClose before redisConnect.
Since rredis manages connection globally, I suggest to open an API to control whether managing the connection by redisWorker and redisDoRedis or not.
That is to say, if these function call redisConnect at the beginning, then it should call redisClose before leaving. Also, the user should have an option to control whether the redisConnect is called or not.
I'm not sure that it matters. It's safe to call redisConnect multiple times. It sems like this change would just introduce an unneccesary complciation? Am I misinterpreting your idea?
Hi,
I notice that after entering
redisWorker
andregisterDoRedis
, there is aredisConnect
. However, before there is aredisClose
before leavingredisWorker
, but noredisClose
beforeredisConnect
.Since
rredis
manages connection globally, I suggest to open an API to control whether managing the connection byredisWorker
andredisDoRedis
or not.That is to say, if these function call
redisConnect
at the beginning, then it should callredisClose
before leaving. Also, the user should have an option to control whether theredisConnect
is called or not.