Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 52091 invoked from network); 21 Apr 2004 14:42:06 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 21 Apr 2004 14:42:06 -0000 Received: (qmail 88653 invoked by uid 500); 21 Apr 2004 14:41:32 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 88619 invoked by uid 500); 21 Apr 2004 14:41:32 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 88563 invoked from network); 21 Apr 2004 14:41:31 -0000 Received: from unknown (HELO gw-nl6.philips.com) (161.85.127.52) by daedalus.apache.org with SMTP; 21 Apr 2004 14:41:31 -0000 Received: from smtpscan-nl2.philips.com (smtpscan-nl2.philips.com [130.139.36.22]) by gw-nl6.philips.com (Postfix) with ESMTP id 539BC6BE98 for ; Wed, 21 Apr 2004 16:41:33 +0200 (MEST) Received: from smtpscan-nl2.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id 479BC19C52 for ; Wed, 21 Apr 2004 16:41:32 +0200 (MEST) Received: from smtprelay-nl1.philips.com (smtprelay-eur1.philips.com [130.139.36.3]) by smtpscan-nl2.philips.com (Postfix) with ESMTP id 3FD5919C50 for ; Wed, 21 Apr 2004 16:41:31 +0200 (MEST) Received: from prle4.natlab.research.philips.com (prle4.natlab.research.philips.com [130.145.137.96]) by smtprelay-nl1.philips.com (8.9.3p3/8.8.5-1.2.2m-19990317) with ESMTP id QAA22738 for ; Wed, 21 Apr 2004 16:41:31 +0200 (MET DST) Received: from smtpmon (smtpmon [130.145.137.150]) by prle4.natlab.research.philips.com (8.11.6/8.11.6) with ESMTP id i3LEfUN14144 for ; Wed, 21 Apr 2004 16:41:30 +0200 Received: from PC67241939.ddns.htc.nl.philips.com ([130.145.148.159]) by smtpmon (MailMonitor for SMTP v1.2.0 ) ; Wed, 21 Apr 2004 16:41:30 +0200 (CEST) Message-ID: <004201c427ae$bc167e40$9f949182@ddns.htc.nl.philips.com> From: "D. Carroll" To: Date: Wed, 21 Apr 2004 16:41:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: [users@httpd] Arrays of config directives. X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hiya I am new here. I am currently developing a module for apache 2.0 which takes a lot of config arguments in "sets". The most logical way to do this would be with an array, but I wonder if that is possible with the API's For example, ideally I'd like to do something like this in the httpd.conf file. AUTH_SOURCE(1) = auth1.authserver.com AUTH_SOURCE(2) = auth2.authserver.com AUTH_LOGIN(1) = authlogin1 AUTH_LOGIN(2) = authlogin2 AUTH_PASS(1) = authpass1 AUTH_PASS(2) = authpass2 I could do it this way: AUTH_SOURCES = auth1.authserver.com|auth2.authserver.com AUTH_LOGINS = authlogin1|authlogin2 AUTH_PASSES = authpass1|authpass2 Or even AUTH_DATA = auth1.authserver.com(authlogin1,authpass1)|auth2.authserver.com(authlogin2,a uthpass2) The problem with both of these solutions is that there are about 15 config directives to deal with. I wonder if anyone else has an idea of how I'd do this. The *only* way I can think of is to have the data in an external file, which would be listed as the only config directive. Does anyone have a better idea? -D p.s. Should I be writing for apache 2.1.x?? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org