Feature request: resilient connectivity -> enpoind pools

[wellloaded]

I use the WS client to connect to a mixture of VPN providers (including Windscribe). This is a remote VM so, I need this to be connected no mater what.

Currently, if the preferred/selected VPN endpoint experiences any issue, the VPN is found with the spinning (trying to connect) logo on the WS client and no further action is performed.

Could you please think of a solution where a pool of preferred destination can be provided and the WS client attempt a connection to a different endpoint within the pool if any connectivity issue is experienced?

I guess this implies:

• make the WS client a bit more clever in understanding it's not connected for whatever internal/external reason
• allow for a preferred target to be a pool of destination/configurations instead than a single one like it currently does.
• enable the connection attempt to be performed against sequential,random,fastest-ping list of targets in a preferred pool

Thanks

[bernerdad]

This feature was scheduled to be in our 2.10 release, but we hit 'hold' on it while we dig deeper into its implementation details. It may make it into 2.11.