4 ms·
I use node.js for long-lived connections (sending/receiving large amounts of data, or long-polling). This is a task to which it is ideally suited. Putting CPU-i
by strags 15y ago
I use node.js for long-lived connections (sending/receiving large amounts of data, or long-polling). This is a task to which it is ideally suited. Putting CPU-intensive operations inside a HTTP handler is something that is obviously not going to work in a single-process, single-threaded event-driven framework. Ted's complaining because node.js is unsuitable for something that it's not intended to be used for.
Defending CGI, in my opinion, also hurts his credibility. The "good old days" weren't so good. Spawning a new process for each request? Re-establishing database connections every time? That shit only worked because there were three people on the internet at the time.
- icebraining 15y ago> Defending CGI, in my opinion, also hurts his credibility. The "good old days" weren't so good. Spawning a new process for each request? Re-establishing database connections every time? That shit only worked because there were three people on the internet at the time. Apparently the server behind SQLite.org and Fossil-scm.org, which gets 250M requests/day, spawns a new HTTP server for each request. There's no database, though. http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg02065.html http://www.mail-archive.com/fossil-users@lists.fossil-scm.or...
- dchest 15y agofossil-scm.org uses SQLite database (in WAL mode), and the website is the repository itself. http://www.fossil-scm.org/index.html/doc/trunk/www/selfhost.wiki http://www.fossil-scm.org/index.html/doc/trunk/www/selfhost....
- icebraining 15y agoOops. Thanks.