Open Laurence-yau opened 1 year ago
If you update the options object that gets passed into the multiplexer to connect, then yep we'll respect the value on the next reconnect, whatever the reason is.
Note: this doesn't apply to very old versions, we always advise using latest, but this happened around the ~2.5.x timeframe.
I have a bit of a unique case and looking to get some answers to some questions before go down path. We are looking to use Signal R with a Redis (AWS elastic cache) backplane. It will be authenticated via IAM authentication.
For the request/response use case I just update the ConfigurationOptions and it would use it on the next connect. For the signalr use case would it be possible to use the ConnectionFactory to achieve the same or would i be running into issues because this is a long lived connection?