@baris Yes I use Redis for NodeBB, so it gets applied to the integrated socket.io. But also it seems like I misinterpreted the problem for some reasons...
Several features are not working with clustering, for example the chat:
I can open it, but...
As you see in this screenshot, sometimes I get the messages and sometimes I don't.
Or the plugins, I can initiate installation and nothing happens but the image changes. Installation through the ACP just don't work with clustering. I haven't tested it yet together with websockets, as I'm a cloudflare customer and haven't got access to the websockets right now.
The downside of the help tab, of course, is that you don't get language translations in this
Yeah we need to look into translation hooks for plugins. Something post-0.4x but open to any smart person who can think of a decent enough system :shipit:
You know (one of) the main difference(s) between TCP and UDP, don't you?
TCP is connection-oriented, UDP isn't. So there is no UDP core-functionality to check whether the receiver is alive (/has the port opened).
You'd either need to create server-side code or know the server-behavior (e.g. responses to specific datagrams) to achieve an UDP port-scanner.
If you're able to write server-side code the best is to ask for UDP port status via TCP since it has reliable data-transfer implemented.