Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 52408 invoked by uid 500); 23 Mar 2000 14:52:47 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 52392 invoked from network); 23 Mar 2000 14:52:46 -0000 Message-ID: <20000323145258.19612.qmail@jamesmith.com> From: James G Smith To: new-httpd@apache.org Subject: Re: Server auto-reconfiguration Reply-To: JGSmith@JameSmith.Com X-Url: http://www.JameSmith.Com/ X-Reposting-Policy: redistribute only with permission In-reply-to: Your message of "Wed, 22 Mar 2000 20:26:56 CST." Date: Thu, 23 Mar 2000 08:52:58 -0600 Sender: jgsmith@jamesmith.com X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N mark@mjwilcox.com wrote: >On 21 Mar 00, at 20:53, James G Smith wrote: > > >> What ACAP gives us is a way of addressing the configuration items, even >> if we don't use the ACAP syntax -- they've already had to think of how >> to name everything - those issues transcend the particular sequence of >> bits used to represent the entities. >> >I'm not sure that you should even just lock in ACAP. I'm also not >one to say that we should lock in LDAP, XML, etc. I do know that >I'd rather try my luck with LDAP or something like XML-RPC than >ACAP at the moment because more people out there have built >things like this with LDAP or XML (e.g. Tomcat) than ACAP. I'd be >more concerned if this became something part of the core of >Apache than an optional module. Actually, I was thinking `configuration' -> `communication' -> `serialization' -> `protocol' -> `ACAP', with ACAP being where they have had to deal with those issues. I would not want to see ACAP itself implemented internally. I'm only thinking of issues such as default behavior and namespaces. I'm somewhat more comfortable with the way ACAP does namespaces (as URL-like strings) than LDAP/DAP, though I can see where one could argue for the DAP/LDAP form. Either way, the actual API will be using some #define's and asciiz strings instead of a wire protocol. Hope this alleviates some fears. ------------------------------------+------------------------------------------ James Smith - jgsmith@jamesmith.com | http://www.jamesmith.com/ jsmith@sourcegarden.org | http://sourcegarden.org/ jgsmith@tamu.edu | http://cis.tamu.edu/systems/opensystems/ ------------------------------------+------------------------------------------