SUBSCRIBE in an asynchronous context

[nicolasff]

Hello,

I've tried to use the SUBSCRIBE command with an asynchronous adapter, but it doesn't seem to be supported.
The main problem is with the __redisPushCallback, __redisShiftCallback functions: the SUBSCRIBE command first sends a message confirming the subscription to the channel, which consumes the redisCallback object. A write to the channel will try to shift the next redisCallback object, which doesn't exist: this leads to an assertion failure in async.c:217.

I have tried to re-add the redisCallback by making __redisPushCallback public instead of static. This seems to work, but I don't think I should be calling this private function.

What do you think? Is there a better way to do this?

[ghost]

I'm having the same issue with the MONITOR command. I want to asynchronously monitor multiple servers.

[nicolasff]

Oh, I hadn't realised this issue was still open, it has been fixed for about 4 months now. @Tomy you need to open a connection per server, there's no way around it.