@akira, I had experience with nginx and other languages, but this is the first time that I had deployed a 100% javascript stack. Let's wait and see what this stack it's capable of.
A good point for node-http-proxy is the support for socket.io out of the box ;) -- Att, Alan Hoffmeister 2012/4/13 akira <[email protected]>: > This is very interesting. I always though that Node developers use > Nginx in their stack for proxying. But reading the docs, node-http- > proxy is mentioned as battle-hardened. How does this hold up when one > serves images? Is the performance comaparable? Nginx is alleged to be > almost unbeatable at serving static files, but if there is some way to > optimize a pure node stack, I would not really mind if it was a bit > slower. > > Anyone with experience on this? Figures? > > Thanks > > On Apr 12, 11:25 pm, mlegenhausen <[email protected]> wrote: >> @alan Why you want to do that? You also normally don't run several MySQL >> instances for each site? That's why you can define databases and >> collections and not just only collections ;) > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
