Yini okufanele ikhishwe yifekthri ye-SOCKS socket yakwa-Jedis

JedisSocketFactory.createSocket kufanele kukhishwe i-socket exhunyiwe futhi elungele ukuthwala ithrafikhi ye-Redis. Ku-Jedis 5.2.0, uhlelo lunikeza leyofekthri kanye nokulungiselelwa kwayo kwekhlayenti le-Redis lapha:

var jedis = new Jedis(socksSocketFactory, redisConfig);

socksSocketFactory kusebenzisa i-redis.clients.jedis.JedisSocketFactory, futhi i-redisConfig iyi-JedisClientConfig yohlelo. Hlala ulungele ukuxhuma lapho isakhi sisebenza: singenza ngokushesha ukuqinisekisa kanye nokunye ukulungiselelwa kwe-Redis.

Landelela i-socket eyodwa kusukela ekwakhiweni kuze kube sekunikezelweni

Ngendlela ye-SOCKS5 engenakuqinisekiswa, ifekthri ingakha i-java.net.Socket enomlamuli ocacile we-Proxy.Type.SOCKS, bese ixhuma kumsingathi nechweba le-Redis. Shiya indawo ekuyiwa kuyo ingaxazululwanga uma iseva ye-SOCKS kufanele ixazulule igama lomsingathi.

Khawulela umzamo wokuxhuma futhi usebenzise isikhathi sokufunda esihlosiwe. Uma ukuxhumana kuhluleka, vala leyosocket futhi ubike i-JedisConnectionException; i-interface yefekthri ayimemezeli i-IOException ehloliwe.

Uma i-Redis idinga i-TLS, setha futhi uqinisekise i-TLS ngaphambi kokubuyisela i-socket. Akukwazi ukucatshangelwa ukuthi ifulegi elihlukile lizoguqula noma iyiphi i-socket ebuyiswe yifekthri. Eqoqweni, phinda lo mjikelezo wempilo nge-socket entsha kukho konke ukubizwa kwefekthri, kuhlanganisa nokuxhumana okungena esikhundleni.

Ukukhethwa kwe-HTTP ku-ProxySelector jikelele akukona ukusetshenziswa okunye kwalomsebenzi. I-Redis ithumela i-RESP nge-socket yayo; ayiphenduki ibe yi-HTTP ngenxa yalokho futhi ayixoxisani nge-CONNECT.