Re: Namespace issues
| From: | Stig S. Bakken | Date: | Thu, 16 May 2002 22:36:31 +0000 |
| Subject: | Re: Namespace issues | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-6177@lists.php.net to get a copy of this message | ||
On Thu, 2002-05-16 at 21:01, Martin Jansen wrote:
> On Thu, 16 May 2002 10:56:45 +0200, Kristian Koehntopp wrote:
>
> >1. Image namespace issues/URL namespace issues
> >
> > "For the admin/application developer:
> > PEAR reserves the right to use the /internal-pear branch in
> > your webservers URL namespace tree. Your application must
> > not use URLs starting with /internal-pear for its own
> > purposes.
> >
> > For PEAR developers:
> > Any PEAR class that needs URLs may use names below the
> > /internal-pear/<classname>/ branch in a webservers URL
> > namespace tree."
>
> I don't how this can be realized in a multi-hosting environment:
> The PEAR installer needs to copy the files to some place
> during installation. How will the different virtual hosts be
> able to access this files later?
>
> The administrators would need to create symbolic links
> in the vhost configuration like
>
> <VirtualHost 192.168.0.10>
> ServerName foo.bar.com
> DocumentRoot "/var/www/foo.bar.com/htdocs"
>
> Alias /internal-pear "/usr/local/lib/php/data"
> </VirtualHost>
>
> which a lot of mass hosting providers will surely not do. Do you
> have an idea on how to solve this?
Let the PEAR installer handle it, and update what needs updating.
- Stig