Re: Coupling Plack/PSGI with mod_perl, or an alternate architecture?
Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 <[email protected]>
| Newsgroups | gmane.comp.apache.mod-perl |
|---|---|
| Message-ID | <[email protected]> |
> Has anyone on this list actually run a Plack application *inside* > mod_perl? Yes. > how one does that. <http://p3rl.org/Plack::Handler::Apache2> > relative merits of this approach? It is very similar to the way traditional mod_perl apps are deployed and therefore familiar. > reasons to pick a mod_perl approach over a plack runner approach Requires no proxying. More reasons in <http://www.catalystframework.org/calendar/2007/17#Motivation>; don't get confused about the deployment notes, that was before the switch-over to PSGI. > would you pick a different approach? Catalyst main mindshare is that if decoupling is desired, to achieve it through mod_fastcgi/FastCgiExternalServer. <http://wiki.catalystframework.org/wiki/deployment>
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlB100wACgkQFtlTdOX00Ho7rQCgmY5ZcERUx48273ra4LbGpuIm z88An2c9JxHRmJHlwdOEicjmHVKEBp6k =oJJX -----END PGP SIGNATURE-----