From dev-return-65340-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org Thu Aug 13 13:47:41 2009 Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 38636 invoked from network); 13 Aug 2009 13:47:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Aug 2009 13:47:40 -0000 Received: (qmail 6720 invoked by uid 500); 13 Aug 2009 13:47:46 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 6619 invoked by uid 500); 13 Aug 2009 13:47:46 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 6601 invoked by uid 99); 13 Aug 2009 13:47:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Aug 2009 13:47:45 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [195.232.224.74] (HELO mailout05.vodafone.com) (195.232.224.74) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Aug 2009 13:47:33 +0000 Received: from mailint05 (localhost [127.0.0.1]) by mailout05 (Postfix) with ESMTP id 755D114670C for ; Thu, 13 Aug 2009 15:47:12 +0200 (CEST) Received: from avoexs01.internal.vodafone.com (unknown [145.230.4.134]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailint05 (Postfix) with ESMTPS id 6626B14683D for ; Thu, 13 Aug 2009 15:47:12 +0200 (CEST) Received: from VF-MBX11.internal.vodafone.com ([145.230.5.20]) by avoexs01.internal.vodafone.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 13 Aug 2009 15:47:10 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA1C1C.8E9FD77F" Subject: RE: Defining mandatory parameters for Apache modules Date: Thu, 13 Aug 2009 15:47:10 +0200 Message-ID: <99EA83DCDE961346AFA9B5EC33FEC08B0293E83F@VF-MBX11.internal.vodafone.com> In-Reply-To: <3F2DD0FCF1E2EA4D974C6195B482FD88075CC262@bfs-exch-prd1.myopwv.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Defining mandatory parameters for Apache modules Thread-Index: AcocF5zgpbvsKAYmREan4gL14/o96gAAx3nwAABxJnA= References: <3F2DD0FCF1E2EA4D974C6195B482FD88075CC262@bfs-exch-prd1.myopwv.com> From: =?iso-8859-1?Q?=22Pl=FCm=2C_R=FCdiger=2C_VF-Group=22?= To: X-OriginalArrivalTime: 13 Aug 2009 13:47:10.0864 (UTC) FILETIME=[8E7C1900:01CA1C1C] X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01CA1C1C.8E9FD77F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I guess the post_config hook should be your friend here. =20 Regards =20 R=FCdiger ________________________________ From: Raj Iyer [mailto:Rajalakshmi.Iyer@openwave.com]=20 Sent: Donnerstag, 13. August 2009 15:34 To: dev@httpd.apache.org Subject: Defining mandatory parameters for Apache modules =09 =09 =20 Hello,=20 =20 The Apache web server on start up iterates through the list of = configuration directives and invokes the associated module handler for = each directive.=20 =20 For e.g. if module A has handlers for directives D1 and D2, then the = httpd process on start up will invoke the handlers within module A when = it encounters D1 and D2 in httpd.conf. =20 However, what is the best way to find out missing mandatory parameters = from within the module. For e.g. if a directive D3 is mandatory for the = module to work, then how can the module on initialization guarantee that = this configuration parameter is provided?=20 =20 I do not want to provide a default value for this mandatory = configuration directive and also, I do not want to check whether this = mandatory directive is defined or not while handling each request.=20 =20 Thanks in advance, Best regards, Raj Iyer =20 ------_=_NextPart_001_01CA1C1C.8E9FD77F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I guess the post_config hook should be your = friend=20 here.
 
Regards
 
R=FCdiger

From: Raj Iyer=20 [mailto:Rajalakshmi.Iyer@openwave.com]
Sent: Donnerstag, = 13. August=20 2009 15:34
To: dev@httpd.apache.org
Subject: = Defining=20 mandatory parameters for Apache modules

 

Hello,=20

 

The Apache web = server on=20 start up iterates through the list of configuration directives and = invokes the=20 associated module handler for each directive.

 

For e.g. if = module A has=20 handlers for directives D1 and D2, then the httpd process on start up = will=20 invoke the handlers within module A when it encounters D1 and D2 in=20 httpd.conf.

 

However, what is = the best=20 way to find out missing mandatory parameters from within the module. = For e.g.=20 if a directive D3 is mandatory for the module to work, then how can = the module=20 on initialization guarantee that this configuration parameter is = provided?=20

 

I=20 do not want to provide a default value for this mandatory = configuration=20 directive and also, I do not want to check whether this mandatory = directive is=20 defined or not while handling each request.

 

Thanks in=20 advance,

Best=20 regards,

Raj=20 Iyer

 

------_=_NextPart_001_01CA1C1C.8E9FD77F--