Re: Coupling Plack/PSGI with mod_perl, or an alternate architecture?

On Fri, Oct 12, 2012 at 12:26 PM, Perrin Harkins <[email protected]> wrote:
> On Wed, Oct 10, 2012 at 3:57 PM, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 <[email protected]> wrote:
>>> reasons to pick a mod_perl approach over a plack runner approach
>> Requires no proxying.
>
> Isn't Starman normally run with a proxy in front of it?  If not, it
> should be.  Otherwise, you'd be tying up large processes sending bytes
> to slow remote clients, just like you would with a standard mod_perl
> app.

I think Lars meant no proxy required with *mod_perl* rather than plack
stuff, but yes, Starman is recommended to put behind proxy otherwise
your precious worker process is bound to slow networked clients, and
gets even worse if you run Starman with keepalive support (which you
can turn off with the options).



-- 
Tatsuhiko Miyagawa