Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id EAA24259; Wed, 12 Apr 1995 04:52:17 -0700 Received: from life.ai.mit.edu by taz.hyperreal.com (8.6.10/8.6.5) with SMTP id EAA24252; Wed, 12 Apr 1995 04:52:14 -0700 Received: from volterra (volterra.ai.mit.edu) by life.ai.mit.edu (4.1/AI-4.10) for new-httpd@hyperreal.com id AA25355; Wed, 12 Apr 95 07:52:12 EDT From: rst@ai.mit.edu (Robert S. Thau) Received: by volterra (4.1/AI-4.10) id AA21404; Wed, 12 Apr 95 07:52:11 EDT Date: Wed, 12 Apr 95 07:52:11 EDT Message-Id: <9504121152.AA21404@volterra> To: new-httpd@hyperreal.com Cc: new-httpd@hyperreal.com, new-httpd@hyperreal.com In-Reply-To: (message from Brian Behlendorf on Tue, 11 Apr 1995 18:19:58 -0800 (PST)) Subject: Re: E71 Description File Addition Sender: owner-new-httpd@hyperreal.com Precedence: bulk Reply-To: new-httpd@hyperreal.com Date: Tue, 11 Apr 1995 18:19:58 -0800 (PST) From: Brian Behlendorf This is one of those creeping-featuritis-potential functions, like log file processing, that as said before are probably better handled by passing that functionality off to a script. Here's a proposal: DirectoryIndexGenerator some_script DirectoryIndexGenerator would be the program that generates the pretty HTML directory index. It's got the full suite of CGI scripts, and gets information about the directory it's in by whatever the language it's written in has for obtaining the current working directory (like CGI scripts do). By default, httpd uses the built-in generator it has now - however, both the 4DOS "descript.ion" and ALIWEB mechanisms can use this, and we could distribute those scripts in the utils/ directory. Thoughts? Seems like a reasonable compromise... it would also probably work well with an internal gateway mechanism, for sites where this sort of thing comes up enough that CGI overhead might be a problem. rst