RE: NameWithVirtualHost

[Doug MacEachern]

On Thu, 17 May 2001, Geoffrey Young wrote:
 
> well, you're not using Apache::Registry (which uses the
> $Apache::Registry::NameWithVirtualHost global)
> but Apache::RegistryNG (for which there's no corresponding
> $Apache::RegistryNG::NameWithVirtualHost :)

he used Apache::RegistryNG in the startup.pl, but we didn't see
httpd.conf, which i'm guessing is configured to use Apache::Registry,
because..

> I haven't used RegistryNG at all, so I don't know the benefits of it over
> Registry (someone might) but I suspect that you
> will get the namespace isolation you desire if you move to Apache::Registry
> instead.

Apache::RegistryNG actually uses $r->filename instead of $r->uri so it
should have namespace protection.

RE: NameWithVirtualHost

[Geoffrey Young]

> -Original Message-
> From: Jason Czerak [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 16, 2001 3:18 PM
> To: [EMAIL PROTECTED]
> Subject: NameWithVirtualHost
> 
> 
[snip] 
> and the lines in startup.pl:
> 
> #! /usr/bin/perl
> use strict;
> use Apache::RegistryNG;
> use CGI ();
> use DBI ();
> use DBD::Pg ();
> 1;
> 
> nothing changes if the
> $Apache::Registry::NameWithVirtualHost = 1 is in the
> startup.pl or not.

well, you're not using Apache::Registry (which uses the
$Apache::Registry::NameWithVirtualHost global)
but Apache::RegistryNG (for which there's no corresponding
$Apache::RegistryNG::NameWithVirtualHost :)

I haven't used RegistryNG at all, so I don't know the benefits of it over
Registry (someone might) but I suspect that you
will get the namespace isolation you desire if you move to Apache::Registry
instead.

--Geoff