Nigel,
If you are referring to the loading of a look-and-feel module, you're out
of luck. The module names themselves are global and do not take on the
properties of the script namespace.
This is actually a *feature* so that different scripts can share the same
modules. :)
I actually spent a lot of time wringing my hands on this problem because I
want the look and feel of our apps to be .pm files. This issue is different
from templating because even templates need some logic behind them which
the view files generate.
So In the end, I came up with a "view loader" mechanism where each view is
granted its own namespace using a special .pm loader that changes the
package namespace that the view has.
Each view has two methods: new and display. new() creates the view and
makes it sticky within the scripts namespace while display() actually
generates the view's display routine.
You can read the view chapter at http://www.extropia.com/ExtropiaObjects/
if you want to know more about one workaround.
Later,
Gunther
At 12:59 PM 11/14/00 +0100, Stas Bekman wrote:
>On Tue, 14 Nov 2000, Nigel Hamilton wrote:
>
> > Hi,
> >
> > I'm encountering name space clashes with two virtual hosts on my
> > server while using Apache::Registry.
>
>http://thingy.kcilink.com/modperlguide/config/A_Script_From_One_Virtual_Host_C.html
>
>
>_____________________________________________________________________
>Stas Bekman JAm_pH -- Just Another mod_perl Hacker
>http://stason.org/ mod_perl Guide http://perl.apache.org/guide
>mailto:[EMAIL PROTECTED] http://apachetoday.com http://jazzvalley.com
>http://singlesheaven.com http://perlmonth.com perl.org apache.org
__________________________________________________
Gunther Birznieks ([EMAIL PROTECTED])
eXtropia - The Web Technology Company
http://www.extropia.com/
