In the day and age of live streaming, video conferencing, and remote work, one of the primary concerns of any user is latency. A seamless experienc...
For further actions, you may consider blocking this person and/or reporting abuse
Webserver config/support, as well as reverse proxy should have an article of its own.
Nobody hosts a nodejs raw onto the Internet.
Great article, cheers
thanks! appreciate the feedback!
Good
Amazing! I will use this
Glad to hear that! :)
Very useful article. Quick question: where does the 'myWebsocket' in the url ws://localhost:9876/myWebsocket come from? Is this a default path with ws?
umm nope... "myWebsocket" in the url is the route that websocket supported
we have to implement this route by ourselves? or I cant understand how to connect frontend with this route? In node.js code snippet I dont see anything about this route
myWebsocket is a namespace, You can change it for whatever you want to, and in your html you must connect to your namespace. good luck
Why do you reject half of the connection requests?
Great stuff. Thank you very much 🙂
let me know how we see output after coding
This is a great tutorial.