You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to suggest we add compatibility with NodeRedis w.r.t. the serverInfo object. NodeRedis updates the serverInfo object any time its client issues an INFO command to redis (and receives usable response) - see here. While it may incur extra overhead to do this every time if the resulting object is never read, it would be useful to provide an opt-in mechanism to allow updates to that metadata. In particular, this would allow other libraries that interoperate with NodeRedis to re-use the existing INFO parsing code without having to depend on another external library or embed INFO-parsing code in their internals for one supported library.
I'd like to suggest we add compatibility with NodeRedis w.r.t. the
serverInfo
object. NodeRedis updates theserverInfo
object any time its client issues anINFO
command to redis (and receives usable response) - see here. While it may incur extra overhead to do this every time if the resulting object is never read, it would be useful to provide an opt-in mechanism to allow updates to that metadata. In particular, this would allow other libraries that interoperate with NodeRedis to re-use the existing INFO parsing code without having to depend on another external library or embed INFO-parsing code in their internals for one supported library.See also: bee-queue/arena#219
The text was updated successfully, but these errors were encountered: