Apache still needs to fork mod_perl. This is a non-issue for an external FCGI server.
> -----Original Message----- > From: Octavian Rasnita [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 10, 2007 2:38 PM > To: The elegant MVC web framework > Subject: Re: [Catalyst] serving static files > > > From: "Perrin Harkins" <[EMAIL PROTECTED]> > > > If you're serving static files and running mod_perl without > a reverse > > proxy, that should be the first thing you change. It has a very > > significant effect on performance. > > > > - Perrin > > Sorry for off topicness, but please tell me, does it have a > bad effect if > the files are just some files sitting in a directory, and > they are served by > apache directly, with no relations with the directories that > are handled by > a perl-script handler? > > What I don't understand is why serving the files directly > decreases the > performance of mod_perl apps, even though downloading those > files has no > relation with those mod_perl apps. > > Does it happen the same in case of FastCGI applications? > > Do you have a recommendation for a text for learning how to > use a reverse > proxy? > > Thank you. > > Octavian > > > _______________________________________________ > List: Catalyst@lists.rawmode.org > Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/catalyst@lists.rawmode.org/ > Dev site: http://dev.catalyst.perl.org/ > _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/
