--- On Fri, 10/12/12, Fred Moyer <f...@redhotpenguin.com> wrote: > On Wed, Oct 10, 2012 at 12:39 PM, Perrin Harkins wrote: > >> 2) Do you believe that there are any compelling reasons to pick a mod_perl > >> approach over a plack runner approach that we may be missing? > > > > Advantages of a mod_perl approach: > > - Access to all the mod_perl stuff on CPAN (auth modules, SizeLimit, > > rate-limiting, etc.). > > - Ability to use the Apache API when handling requests. > > - Sounds like at least some of your team has real-life experience > > running a site on mod_perl. > > - Knowledge that the base Apache httpd codebase is used by many other > websites, and has been through security audits, performance tuning, > and is composed of a set of developers who are committed to the long > term health of the codebase.
Not all of them. Using the duck principle, some of them are just shills. After the recent DNT fiasco https://github.com/apache/httpd/commit/a381ff35fa4d50a5f7b9f64300dfd98859dee8d0 I don't believe apache can be trusted. (Or the W3C, who permitted their version of the standard to magically change at a single editor's whim 11 days ago, a month after his patch submission.) Phil
