3 ms·
I find this title rather misleading. There is no node.js HTTP server in your browser. Meaning, you cannot do anything that is part of Node.js in the browser "se
by ericz 14y ago
I find this title rather misleading. There is no node.js HTTP server in your browser. Meaning, you cannot do anything that is part of Node.js in the browser "server"
The browser is still running its original js engine with none of the Node goodies. It merely receives proxied requests, does some stuff to it, then sends it back to the proxy, which returns it to the client.
- arturadib 14y agoThe title might be a little too ambitious, but it is partially justified as the HTTP handler in the client (browser) has a Node-like API, see: https://github.com/jed/browserver-client#example https://github.com/jed/browserver-client#example
- jedschmidt 14y agoIt merely receives proxied requests, does some stuff to it, then sends it back to the proxy, which returns it to the client. You just described the majority of the web servers that we web developers deal with. Sure, it's a proxy, but the fact that the machine responding is connected via WebSocket and not a local network doesn't make it any less of a server, in my opinion.