3 ms·
Not necessarily specific to node.js, but in general, instead of a standard webserver, use netcat, on multiple obscure ports, where each instance of netcat acts
by ThaddeusQuay2 15y ago
Not necessarily specific to node.js, but in general, instead of a standard webserver, use netcat, on multiple obscure ports, where each instance of netcat acts once and is discarded.
http://en.wikipedia.org/wiki/Netcat http://en.wikipedia.org/wiki/Netcat
- pjscott 15y agoThat plan sounds like half-assed voodoo, but it kind of resembles the approach that qmail uses for security, which is actually pretty neat: http://cr.yp.to/qmail/qmailsec-20071101.pdf http://cr.yp.to/qmail/qmailsec-20071101.pdf
- ThaddeusQuay2 15y agoThank you for the link, but my approach is neither "half-assed" nor "voodoo". I've used netcat, as described, for a small project, and it worked well. I'm about to do the same, for a big project, and I expect that it will again work well. Standard webservers are bloated. Speed, security and stability can be enhanced by distributing work across a system of one-shot processes. I take some inspiration from Jef Poskanzer's design decisions in thttpd. http://acme.com/software/thttpd http://acme.com/software/thttpd http://en.wikipedia.org/wiki/Jef_Poskanzer http://en.wikipedia.org/wiki/Jef_Poskanzer NOTE TO DOWNVOTERS: You shouldn't downvote a technical suggestion, no matter how strange, unless you are certain that it won't work.