Re: (jeffa) Re: thinking about mod

i've been reading though the online mod_perl guide. i read the third book mentioned a while ago but it's about to come off the shelf.

i'm trying to decide which is going to be better -- writing the app and running it under Apache::Registry, or writing an app that starts with mod_perl ( Apache::DBI, etc ) and stays there. i don't see the client moving the site to another server ... so i think it's safe to write a 100% mod_perl app.

Comment on Re: (jeffa) Re: thinking about mod_perl

Replies are listed 'Best First'.
Re: Re: (jeffa) Re: thinking about mod_perl by bobn (Chaplain) on Jul 19, 2003 at 20:49 UTC
mod_perl is pretty common in OpenSource OSs. As an example, Redhat has provided apache w/ mod_perl since rh 6.1 or 6.2. Apache::Registry does give you that 'out' though. I actually did some code that way - so it would run both with and wihout mod_perl. In fact I did it both ways on the same box, in the same directory, using a Location directive to use apacche registry if the url was, eg, /perl/... and letting it be regular CGI if the URL was, eg, /cgi-bin/... it's not hard --Bob Niederman, http://bob-n.com	[reply]

Replies are listed 'Best First'.

Re: Re: (jeffa) Re: thinking about mod_perl
by bobn (Chaplain) on Jul 19, 2003 at 20:49 UTC

mod_perl is pretty common in OpenSource OSs. As an example, Redhat has provided apache w/ mod_perl since rh 6.1 or 6.2.

Apache::Registry does give you that 'out' though. I actually did some code that way - so it would run both with and wihout mod_perl. In fact I did it both ways on the same box, in the same directory, using a Location directive to use apacche registry if the url was, eg, /perl/... and letting it be regular CGI if the URL was, eg, /cgi-bin/... it's not hard

[reply]