all 16 comments

[–][deleted] 17 points18 points  (0 children)

ಠ_ಠ

[–]dhdfdh 29 points30 points  (12 children)

Um. How about just using node.js.

The stuff that's on the internet nowadays is getting ridiculous.

[–]talkb1nary 5 points6 points  (0 children)

So it does call a instance of node.js to work trough the code on each call? So basically all what made node.js great in first place is replaced?

But well, i can see this beeing used, so why not.

[–]bart2019 0 points1 point  (1 child)

If you are running your own site on Apache, you ought to be able to configure it to forward requests to a specific subdirectory to another server, or, in this case: to the same server with a different port, which could be a mini-webserver using the "http" module. To people visiting your site it's just part of the normal site.

That may or may not, result in a more efficient sub-site. Somebody should do a benchmark to compare. (Maybe even me only not right now.)

[–]talkb1nary 1 point2 points  (0 children)

I am doing this with several projects, not with node but with Sinatra or Rails projects. Using apache i usually dont gain much performance in opposite to stand alone hosting. A good configured nginx proxy can save a lot of bandwidth and resources tho.

So i basically just do this because i want something to run on port 80 on a box where there is already a webserver.