No, I'm afraid Apache::Registry_plus_Template is only a wish, not a reality at present. I am doing much the same as you as far as having a App::WWW::Base which inherits from CGI::Application and initializes a Template object.
Eventually I suppose I will have to look at making the above module, but i imagine that is going to require extensive mod_perl knowledge which i can't claim to have. -Stephen -----Original Message----- From: Brett Sanger [mailto:[EMAIL PROTECTED]]On Behalf Of Brett Sanger Sent: Friday, December 06, 2002 2:40 PM To: howars Cc: [EMAIL PROTECTED] Subject: Re: [Templates] Run time include path configurability without Apache::Template > I'm actually running my code as a subclass of CGI::Application, and > running the whole thing under Apache::Registry. I'm looking at the same thing, but I've only just started playing with getting CGI::App to happily coexist with mod_perl (well, they coexist just fine, it's more a matter of getting them to exist w/o massive memory usage) > code. Similarly, I'd love to be able to do something like this for > each virtual host: > > PerlModule Apache::DBI PerlModule Apache::Registry_plus_Template Am I to take it you don't have Apache::Registry_plus_Template? I have a master subclass of CGI::App that all my apps are subclasses of, and I'm preloading that class plus Template, then running the scripts under Apache::Registry. I'm very interested in hearing your experiences and pitfalls. Sadly, I don't have any vhosting experience in this particular setup to share in return. -- SwiftOne [EMAIL PROTECTED] _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.ourshack.com/mailman/listinfo/templates
