Re: [Resin-interest] lighttpd and nginx

2009-06-18 Thread Ronan Lucio
Understood Scott, thank you, Ronan Scott Ferguson escreveu: On Jun 17, 2009, at 6:14 AM, Ronan Lucio wrote: Hi Scott, Scott Ferguson escreveu: If you're looking at nginx for performance, you should benchmark Resin as a load-balancer as well, especially if you're using proxy

Re: [Resin-interest] lighttpd and nginx

2009-06-17 Thread Ronan Lucio
Hi Steffen, For all I have understood it refers to Resin's-4.0, which is still beta. Anyway to use it with 3.1? Thanks, Ronan Steffen Busch escreveu: I don't know about lighttpd, but there was a blog post recently regarding nginx, check this: http://blog.caucho.com/?p=173 Regards, Steffen

Re: [Resin-interest] lighttpd and nginx

2009-06-17 Thread Ronan Lucio
Hi Scott, Scott Ferguson escreveu: If you're looking at nginx for performance, you should benchmark Resin as a load-balancer as well, especially if you're using proxy caching. For 4.0, the performance numbers were fairly close (nginx slightly faster). Do you think Resin-4.0 is reliable

Re: [Resin-interest] lighttpd and nginx

2009-06-17 Thread Scott Ferguson
On Jun 17, 2009, at 6:14 AM, Ronan Lucio wrote: Hi Scott, Scott Ferguson escreveu: If you're looking at nginx for performance, you should benchmark Resin as a load-balancer as well, especially if you're using proxy caching. For 4.0, the performance numbers were fairly close (nginx

Re: [Resin-interest] lighttpd and nginx

2009-06-16 Thread Steffen Busch
I don't know about lighttpd, but there was a blog post recently regarding nginx, check this: http://blog.caucho.com/?p=173 http://blog.caucho.com/?p=173Regards, Steffen 2009/6/16 Ronan Lucio lis...@tiper.com.br Hi, Does Resin works with lighttpd or nginx? Thanks, Ronan

Re: [Resin-interest] lighttpd and nginx

2009-06-16 Thread Scott Ferguson
On Jun 16, 2009, at 12:09 PM, Steffen Busch wrote: I don't know about lighttpd, but there was a blog post recently regarding nginx, check this: http://blog.caucho.com/?p=173 For Resin 4.0, you can use the new FastCgi protocol implementation (or use a http proxy). It's configured like the