|
Posted by Jerry Stuckle on 11/10/06 19:06
John Dunlop wrote:
> Jerry Stuckle:
>
>
>>When dealing with file URI's, the file extension is meaningful.
>
>
> Frankly, Jerry, I don't know whether to laugh or cry.
>
John, when you figure out, please let the rest of us know.
Theory is great. And if there were some way for the web server to
determine what type of file it is, it would be a different story.
But right now all we have (on Linux) is an executable flag. The file
can either be executed by the OS or not. There is no way for the web
server to determine what it needs to parse for various languages.
Let me give you an example from one site. Most of the site is written
in VBScript (.asp). However, we have a discussion forum written in
Perl. We have other packages written in PHP. And we're looking at
adding another package which requires Python.
Now - do you expect the webserver to parse every one of those files,
including the static pages, for VBScript, PHP, Perl and Python?
Right now the only way the web server can tell is by the file extension.
Of course this is on IIS, so there's no .htaccess. But I guess if you
dug deeply enough there might be a way to tell the server to parse
index.html as .asp code, but blog.html as PHP code and discussion.html
as Perl code.
Can you imagine the trouble trying to keep up with a couple of thousand
files like that?
This is the real world, not some theoretical Utopia.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|