Is there any special reason why the Aerospike java client is using NIO for Java-Sockets?
We would like to access our Aerospike-Cluster from our Home-Office and normally we using a SSH-Tunnel (SOCKS) for Monitoring/Accessing our Data/Administrate our Servers. This approach has several advantages, for example we need dont need any additional Firewall-Rules / its encrypted and its faster then VPN and we dont need to install a VPN-Server/Client on all our Servers.
Java NIO forbidds using a SOCKS-Proxy, instead its using ‘native’-Sockets which skips the SOCKS-Server.
Would be awesome to have this Option, maybe just as a fall-back/client-policy?