Closed rafaelsales closed 6 years ago
It's possible with
could take a force_new
boolean to override the default reuse logic. Otherwise, since listen
is likely a long-running method, I'd suggest it have its own Redis connection and the message handling use the connection pool as normal.
since listen is likely a long-running method, I'd suggest it have its own Redis connection
That's true. I'll go for this solution
Thanks
Hi,
In the scenario where I need to access redis within a subscribe callback, I need to use nest call of
pool.with
, which doesn't checkout another connection.Example:
The workaround I've thought about was to always use
Redis.new
when using it tosubscribe
.Are there plans to have a nicer usage for this scenario?