Thanks Scott.

How about Lighttpd?

-Wesley

----- Original Message ----- 
From: "Scott Ferguson" <f...@caucho.com>
To: "General Discussion for the Resin application server" 
<resin-interest@caucho.com>
Sent: Wednesday, March 11, 2009 2:30 AM
Subject: Re: [Resin-interest] Why Apache?


>
> On Mar 10, 2009, at 11:14 AM, wesley wrote:
>
>> Hi Scott,
>>
>>    Here is my long wait question :
>>
>>    How to configure Resin run with nginx?
>
> Hmm.  nginx has a http proxy 
> http://wiki.codemongers.com/NginxHttpProxyModule
> .
>
> However, it looks like they only support HTTP/1.0 on the backend,
> which is a big limitation because keepalives are very important in a
> proxy configuration.  I'd assumed they supported HTTP/1.1.  That's
> actually a problem.
>
> We could add a FastCgi frontend interface to Resin, which would let it
> run behind nginx efficiently. (e.g. for Resin 4.0.1 or 4.0.2 whenever
> we upgrade our own FastCgi.)
>
> -- Scott
>
>>
>>
>> regards
>> Wesley
>>
>> ----- Original Message -----
>> From: "Scott Ferguson" <f...@caucho.com>
>> To: "General Discussion for the Resin application server"
>> <resin-interest@caucho.com>
>> Sent: Wednesday, March 11, 2009 1:52 AM
>> Subject: Re: [Resin-interest] Why Apache?
>>
>>
>>>
>>> On Mar 10, 2009, at 10:44 AM, Rachel McConnell wrote:
>>>
>>>> Static file serving, perhaps?  I don't know the current benchmarks
>>>> but
>>>> Apache has always had the reputation of being very fast for static
>>>> files, whereas that's not what resin is optimized for.
>>>>
>>>> I say this from the POV of not using Apache at all, though: we use
>>>> resin behind HAProxy for load balancing, and a lighttpd instance for
>>>> image files.
>>>
>>> Actually, Resin's static file performance matches Apache's, because
>>> Apache really isn't all that fast.
>>>
>>> If you really need ultra fast static files, then something like
>>> lighttpd or nginx would be a better choice than Apache.
>>>
>>> -- Scott
>>>>
>>>>
>>>> Rachel
>>>>
>>>> On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman
>>>> <aaron.free...@layerz.com> wrote:
>>>>> After watching a few of these threads about people using mod_caucho
>>>>> with
>>>>> Apache, it dawned on me to ask an open-ended question:
>>>>>
>>>>> Why use Apache at all?
>>>>>
>>>>> I am sure there are good reasons for it out there, so I am just
>>>>> curious what
>>>>> the use-case is for using Apache plus Resin instead of using just
>>>>> Resin?
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> resin-interest mailing list
>>>>> resin-interest@caucho.com
>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> resin-interest mailing list
>>>> resin-interest@caucho.com
>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>
>>>
>>>
>>> _______________________________________________
>>> resin-interest mailing list
>>> resin-interest@caucho.com
>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>
>>
>>
>>
>> _______________________________________________
>> resin-interest mailing list
>> resin-interest@caucho.com
>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>
>
>
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest
> 



_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to