> Randy Terbush wrote: > > It seems that it is time that some thought go into an interface > > that is more politically correct. :-) Hopefully this list will > > allow us to come to some consensus as to what the tools/hooks > > should be to make it easy for interface developers to communicate > > with the server. > > As creator of an even older Apache GUI list (which didn't result in > much, though ... :-( ), I've created a rough description of what the GUI > has to do and included some ideas on how to implement some of the stuff > ... anyone interested can contact me ... I don't know whether I should > post the doc to this list (thrity-some K of MS-Word doc ...)
Just to sound like a broken record, this list is not meant to replace any existing projects or their communication channels. We mainly would like to establish good communication with the Apache server development folks and the people who have begun or are considering GUI development. I would like to read what you have in your document. Since I generally stay clear of machines that can run MS Word, I would prefer to see it in plain ASCII. > > being a way to safely communicate configuration and status issues > > to the Apache webserver. > > Hm ... why not plain CGI ? Less hassle ... or am I missing some issues ? CGI is certainly an option. Since Apache will soon be available for NT, CGI and the portability issues of the language used could be an issue. Giving that CGI or a standalone server the hooks to communicate configuration information should allow the various GUI developers like yourself to create interfaces in different languages using these same hooks. > > Storage of the config info could move to: > [..] > > ... and should allow for config generations, i.e. saving a certain > number of server configs in case of problems/misconfiguration ... > > -gg
