Portability to me is the ability to take a script from one machine,
move it to another and it works without any modifications. A weak spot
in the current CGI is finding the location of the scripts local data
and the document tree in a portable way. Thus my suggestions of
SCRIPT_DATA_DIR and DOCUMENT_ROOT variables.
As to DOCUMENT_ROOT and the virtual/physical mapping: I agree with Ari
there _need_ not be any direct mapping from URL to file system. However,
I guess most(all?) http server uses the filesystem as the basic mechanism
to do the URL->file mapping, modified by alias-mechanisms etc as needed.
Even if we can't have a 100% solution, a 90% solution would make life a
lot easier. The script author will just have to put into his
documentation what URL's the script accesses as files and the server
administrator will have to make sure they have a direct file mapping.
Baard Haafjeld | When you give a wolf a poodle cut, you
Norwegian Telecom Research | don't get a show dog but a pissed wolf.
SMTP-mail: Baard.Haafjeld@tf.tele.no | -Robert Asprin