Hi,

In an explanation to J. Peng you wrote some interesting bits that I put in
a condensed form below. Now you mentioned in another mail that the subject
has shifted a bit, so I changed the subject and dehooked this mail from
the thread. Because there is something that "worries" me...

> As for /var/www/a/b/c, a user can request for a file that does not exists.
> ... until it finds a match. In Torsten's example, this would be:
>
> /var/www/a/b/
>
> Then, the RequestRec object now stores two parts. A filename
> "/var/www/a/b/" and a path_info "/c/d/e". Why would you want to do that.
> Say you have a news site like:
>
> http://example.com/archive/news/2008/02/29/index.html
>
> Instead, you could do
> a trick above and keep going up the hierarchy until you have a filename
> "/var/www/archive/news/" and a path_info "/2008/02/29/index.html". You can
> then use the path_info as a query string to some database to retrieve
> today's news.


I am using a mechanism where I use the path_info to carry information
about the content to be served. However, as far as I know the only way to
do this is to create a handler that is defined for the correct location.
In the described situation, something like,


PerlHandler MyNews->handler()


I do not see how MapToStorage handler will help here. There probably is no
/var/www/archive/news file (or directory), and even if there is, it is of
no use to Apache. Or am I completely and utterly mistaken here?

Kind regards,
Frank