IgniteClientConfiguration.Host is currently a string property that appears
to accept a single dotted IP address, or single host name.

However, in the event that the single configured host/node goes offline, it
would be useful if the client would attempt to dynamically connect to one
or more additional nodes/hosts. I understand the dotnet redis client
operates in this manner.

Thoughts?

Colin

Reply via email to