Multiplexed connection with backoff?

[omer-shtivi]

Multiplexed connection with backoff?

[nihohit]

What would backoff mean in the case of a multiplexed connection?

[omer-shtivi]

Consumer: trying to connect and consume messages, fails to connect -> backoff
Producer: try to produce a message, fails to connect -> backoff?

[nihohit]

I'm not sure what does either a producer or a consumer means in this context, since a multiplexed connection is neither, but a reconnect-with-backoff logic can be easily implemented by the user. If the user wants this mechanism from the library, they can use the connection manager. What's the scenario in which a backoff-and-reconnect mechanism is needed, that the connection manager isn't good for?

[omer-shtivi]

Sorry, I had the PubSub in mind.
I will close the issue, thanks

[nihohit]

If you're looking for the RESP3 pubsub, you can use both the multiplexed connection and the connection manager - just note that you'll need to manually reconnect after disconnects.

…

On Sun, 14 Apr 2024, 15:20 omer-shtivi, ***@***.***> wrote: Sorry, I had the PubSub in mind. I will close the issue, thanks — Reply to this email directly, view it on GitHub <#1148 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDEBBSGA6MBFNV6TDZZV7LY5JYAHAVCNFSM6AAAAABGGBABD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUGAZTAOJTG4> . You are receiving this because you commented.Message ID: ***@***.***>

[nihohit]

I missed the fact that the connection manager has no pubsub methods 🤦
#1149 should fix this.