|
|
Posted by Jerry Stuckle on 11/11/06 02:53
Michael Fesser wrote:
> .oO(Jerry Stuckle)
>
>
>>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.
>
>
> Everything is possible, at least on Apaches.
>
>
>> Of course this is on IIS, so there's no .htaccess.
>
>
> There's not even a webserver ... SCNR
>
Bullshit. It may not be as good as Apache, but it still is a perfectly
good webserver.
>
>>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.
>
>
> Apache: Options +MultiViews
>
> http://example.com/index.html.asp
> http://example.com/blog.html.php
> http://example.com/discussion.html.pl
>
> That's it. You could even remove the '.html' from the filenames and
> still call them how it's supposed to be in the most userfriendly way:
>
And I would love to see you parse asp on Apache. Obviously you've never
tried it or you wouldn't even attempt to make this statement.
There still is not a solid plugin for ASP files on Apache. People have
been working on them, but they're still not ready for a serious server.
And no, don't think I'm a Microsoft fan. Most of my servers are
Linux/Apache. However, none of those are using asp pages.
> http://example.com/
> http://example.com/blog
> http://example.com/discussion
>
> That's the whole point of a URL - it describes (OK, it _locates_) a
> resource on a network. It doesn't have to reveal technical details about
> how that resource is created or which variant of it is returned on
> request. Whether it is created from a static file, a PHP script, a Perl
> script or anything else - it simply dosen't matter and is of absolutely
> no interest for the user agent, so it doesn't have to appear in the URL.
>
> Micha
Sorry, Micha. Your theoretical ideas don't work in practice.
Try doing parsing every file (including static html files) for three or
four different languages. Now try to to this on a server which averages
> 100K hits per hour, 24/7, and peaks at close to 1M hits/hr.
IF it works, you'll have a tremendous amount of additional overhead and
you'll be slowed to a crawl. Even in Apache.
Of course, your average "Mom and Pop grocery" which uses 50Mb of disk
and 500Mb of bandwidth per month won't see this. But a serious site
will have a lot of problems.
So before you go touting your great theories, I suggest you try running
a site on dual 3Gh+ processors, 2GB RAM, averaging 20-25% CPU and
peaking close to 100%. Get your no-file-extension idea working. And
I'd love to see the server keep it up.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|