On Wed, 18 Jun 1997, Randy Terbush wrote: > In previous side discussions, some of the following possibilities > have been suggested as methods to accomplish our goals. That goal > being a way to safely communicate configuration and status issues > to the Apache webserver. > > - SNMP > - LDAP > - others? > > Storage of the config info could move to: > - Berkeley DB 2.0 > - SQL > - others?
While I think whatever is developed should not specifically exclude any of these ideas, my priority would be for a configuration interface via standard web browsers which stores the configuration in plain-text configuration files as now. Once this basic system is in place it could obviously be extended to encompass additional interfaces and storage mechanisms if necessary (Java within a browser is an obvious extension to get better interactivity). However I expect the majority of people just want something quick and easy they can use from their standard browsers. I would like to see LDAP used for user-databases, but I think that is more a core apache feature (mod_auth_ldap anyone?) and databases used to store document meta-information and content (rather than the filesystem as assumed through the core code at present). So my goals would be: - Develop interface screens that make configuration easy - Develop backend (CGI?) to handle screens - Decide how the backend can write to the config files and signal the server (does this have to be a separate server with setuid scripts - yuck - or can we get something like a Unix-socket interface to Apache?) - Add API functions so that the backend configuration process can _automatically_ pickup directive syntax and usage information from Apache rather than have to be hard-coded with directive information (which may change depending on which modules are compiled in). //pcs
