Github user gaborgsomogyi commented on the issue:
    > I don't see an upper bound on the number of consumers per key, nor a way 
of reaping idle consumers. If the SQL equivalent code is likely to be modified 
to use pooling of some kind, seems better to make a consistent decision.
    When do you think the decision will happen?


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to