Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id FAA02170; Thu, 25 May 1995 05:07:31 -0700 Received: from eat.organic.com by taz.hyperreal.com (8.6.10/8.6.5) with ESMTP id FAA02164; Thu, 25 May 1995 05:07:29 -0700 Received: (from brian@localhost) by eat.organic.com (8.6.11/8.6.9) id FAA23329; Thu, 25 May 1995 05:07:29 -0700 Date: Thu, 25 May 1995 05:07:27 -0700 (PDT) From: Brian Behlendorf Subject: Re: Woe is me To: new-httpd@hyperreal.com In-Reply-To: <9505251141.AA01536@volterra> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Thu, 25 May 1995, Robert S. Thau wrote: > Actually, I think that if MultiViews is turned on, this already works. > (Incidentally, replacing foo.html with something called foo.html.shtml > (yuck!) should cause the server to respond to requests for the former > by dishing out the latter, processing includes as it goes --- > technically, it's extremely elegant, with the awkward exception that > the cascade of filename suffixes is ugly as hell). Been thinking a little bit here - it seems that attaching meta-information to filenames is extremely attractive for those OS's which don't support it (ones that do support it: Mac's and NeXT's, for example), so why don't we bite the bullet and suggest that with option "N" turned on, all parts of the filename after the first period are parsed to determine meta-information - i.e. foo.html.it is the italian HTML file, whereas bar.txt.de is the german one, or baz.html.gz.uu is the uuencoded gzip'd html file called baz. How hard would it be to convince people to use dashes instead of period for the actual file's name, is the question. report.1995.html would confuse the server. Ah, 5am musings. Go to bed, brian. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/