Actually it works quite fast. faster then a APC cached php cgi page...
At least you can use nodejs.
for People who have a hosting system in place, like DirectAdmin.
It is a vast work to change ports and add reverse proxy...
with very little effort "at least they can listen to radio.."
I think it will be able to handle same load as Apache handles.
because people who have Apache also have a website that Apache can
handle.
maybe it will be able to handle even more load because because
it will not consume 9mb of php+mysql on each connection and will
respond faster
i have started by testing web sockets because i was curious. I have
figured out that mod_rewrite proxy does not support web-sockets,
I have tested there was no sensible difference in response times with
Apache in front 21ms vs node.js in front 18ms. with the example
res.end("hello world"); php did 83ms with just echo "hello world".
I have tested repetitive writes with for(var i=0;i<1000;i+
+)res.write('hello'); Apache did 119ms node.js did 93 ms. so anyway
write it is better to write response in a bulk.
i have tested long pulling and it works fine. setInterval(function()
{res.write('hello'+i+"\r\n");i++;},1000);
happy Ferrari radio listening...
> RewriteRule ^$
http://127.0.0.1:1337/[P,L]
> # see 'proxy|P' (force proxy)
http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html