httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David M. Oliver" <>
Subject Re: Let's get rid of .htaccess files :-)
Date Thu, 18 Jul 1996 18:48:24 GMT
On Thu, 18 Jul 1996, Howard Fear wrote:

> But, this is exactly the problem.  There are at least two general
> philosophies to 'webspace': the web as a filesystem, and the web
> as an interface to files in the underlying file system. 

	There is also a 3rd philosophy, not now prevalent in the 
	Internet, which is "capability based" - relating to access
	to information in databases.  Here, of course, a person has
	access to a subset of the DBMS's capabilities not specific

	We are finding also that certain types of information providers
	have almost no static files.  All the output is generated by 
	accumlating pieces from different databases, which have their
	own (private) view of the underlying file system.

> We also should preserve the distinction between server configuration
> and 'file' configuration.  The former should not only have limited
> access, but also limited visibility.  It also, probably, causes
> a server restart.  The second should be available to all users
> (for their files) and shouldn't (mustn't) cause server restarts.

	I am inclined to agree with this view, though it is thorny
	when you take a database view of the world (whre the database
	is doing much of the access control).

> > It would be very easy to have a separate daemon watching the
> > conf/ for changes and sending a SIGHUP when needed.
> I don't see the need for this.  And, I think this is a real problem
> if you're going to let your users control the configuration of their
> own files.  (This may not generally be the case for commercial
> web servers, but is certainly desireable for intranets.)

| David Oliver                        |
| Managing Director-Technology              Clickshare Corporation |

View raw message