Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <40202108.1000009@cultura.com.br>
Date: Tue, 03 Feb 2004 19:30:32 -0300
From: ranier <ranier@cultura.com.br>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: Help in Writing Apache Modules in C
References: <D17600FAE4FED711A1BD204C4F4F5020048C20@MAILSERVER>
 <20040129054406.GA3389@thebackrow.net>
 <Pine.LNX.4.53.0401290608220.2827@hugin.webthing.com>
In-Reply-To: <Pine.LNX.4.53.0401290608220.2827@hugin.webthing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Nick Kew wrote:

>On Wed, 28 Jan 2004, Will Lowe wrote:
>
>  
>
>>If you're looking for Apache 1.x (not 2.x)
>>    
>>
>
>Given that he's writing C, and that 2.x is a vastly richer development
>environment than 1.3, why should he even consider that?
>
>In 1.3 days, application developers had to resort to all kinds of
>add-ons, none of which are in C.  If it had had the power of the
>2.0 API, we'd probably still have CGI and PHP at the bottom end,
>of add-ons, but the need for backends like Tomcat would probably
>never have been felt.
>
>  
>
>>>Awaiting for a Helping Hand.
>>>      
>>>
>
>Suggest looking at existing modules, and reading the nicely-documented
>Apache header files.
>
>  
>
Look at http://modules.apache.org/doc/Intro_API_Prog.html and
                http://www.oreillynet.com/pub/ct/38 and
                
http://threebit.net/tutorials/apache2_modules/tut1/tutorial1.html

Ranier.