Socket.IO a cikin Node.js: yi amfani da wakilin SOCKS don polling da WebSocket

Ka rike URL na uwar garken Socket.IO ba canji, ka duba sake-fassan kowane jigilar idan haɓakawa ya kasa.

import { io } from 'socket.io-client';
import { SocksProxyAgent } from 'socks-proxy-agent';

const agent = new SocksProxyAgent('socks5h://proxy.example:1080');
const socket = io('https://events.example', {
  agent,
  transports: ['polling', 'websocket'],
});

Yi amfani da ainihin sabis ɗin Socket.IO. Wakilin Node yana tattaunawa da SOCKS; socks5h yana ba da DNS na manufa ga wannan proxy. Ɗauki madaidaicin wuri daga jerin proxy na SOCKS5 lokacin da aka yarda da gwajin sabis na jama'a ta hanyar masu shiga tsakani na jama'a.

Polling na iya yin nasara kafin haɓakawar WebSocket ta gaba ta kasa. Duba duka hanyoyin biyu da duk wani transportOptions da ke maye gurbin wakilin matakin sama.

Misalin yana amfani da waɗannan jigilai biyu da gangan. WebTransport yana amfani da wata aiwatarwa, kuma JavaScript da ke cikin burauza yana bin tsarin burauza. Filin WebSocket kawai ma ba uwar garken Socket.IO ba ne.

Ka riƙe dabarun abubuwan da suka faru da sake haɗawa da suke akwai, sannan ka cire abokin ciniki ka saki wakilinsa idan haɗin ya ƙare.

Labarai masu alaƙa