Re: An interface to Apache

From: Randy Terbush <randy(at)zyzzyva.com>
Date: Mon Jun 23 1997 - 14:14:49 EDT

> On Mon, 23 Jun 1997, Matthew J. Probst wrote:

Exactly right.

On that note, can I turn the conversation back to some type of API to the config information? By adopting an API, a change in config file format can be transparent to GUI developers.

I'm including again the suggestion I made last week. Is this too high level?

For example:

telnet config.yourserver.org 8080
Password: .....
config>
config> show config

        .... output of config in familiar format ....

config> show config vhost www.someotherserver.org

	
		ServerName www.someotherserver.org
		DocumentRoot .....
		.....
	

config> edit config vhost www.someotherserver.org password>.....
config-edit> documentroot /some/different/directory config-edit> save exit
config> show stats vhost www.someotherserver.org

        ......

config> save sql sqlhost.server.org
config> save file /usr/local/etc/httpd.conf
config> exit

With this type of interface to the _running_ configuration of the server, everyone here can go out and create whatever GUI they wish. It only needs to speak the language of this interface. It offers other benefits such as realtime syntax checking, access to running configuration info, debugging capability, etc.

Thoughts? Received on Mon Jun 23 11:16:06 1997