[prev] [thread] [next] [lurker] [Date index for 2003/12/6]
> Hi all!
>
> First of all, I think we should retrieve the path info by using the
> CGI.pm interface:
>
> http://search.cpan.org/~lds/CGI.pm-3.00/CGI.pm#FETCHING_ENVIRONMENT_VA
> RIABLES
>
> (look for path_info()).
I can't see why I would want to import an entire module, or even a
function to retrieve a single variable already available to my
script.
> Secondly, I'm not sure we need the CGI_PATH config variable, as we can
> determine it from the $q->script_name() (that uses $ENV{SCRIPT_NAME}),
> and together with PATH_INFO (as is commonly found throughout the code)
> from the $ENV{REQUEST_URI} variable (which does not seem to have a
> CGI.pm equivalent).
The reason for the cg_path variable will become apparent when I
finish adding "skins" to the site, which will allow you to switch
between different templates, which will require different PATH_INFO's
like:
foo/BLUE/index
and
foo/FRENCH/index
> Otherwise, I think we should reduce the number of absolute links to a
> minimum and use relative links instead. We can do this by calculating
> the relative distance between two URLS and using ../ where
> appropriate.
This is not as easy as it seems. Could you be more specific as to how
this works when your PATH_INFO has '/'s in it?
Yehuda
Generated at 21:25 on 07 Dec 2003 by mariachi 0.51