Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of laronfin@hotmail.com
 designates 65.54.246.90 as permitted sender)
Message-ID: <BAY134-F1EE32CE3324AD968E2B4CD0B30@phx.gbl>
In-Reply-To: <cc67648e0701091032nb3a6284t205e731e400cbf14@mail.gmail.com>
From: =?gb2312?B?1cUg1emyqQ==?= <laronfin@hotmail.com>
To: dev@httpd.apache.org
Subject: Re: process the request
Date: Tue, 09 Jan 2007 19:37:06 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed

Hello,

Thanks all for your valuable answer. I think now i am clear. Acturally, I 
am now trying to write some new code for Apache. It makes Apache be 
possible to be used in another protocol layer...

Thanks a lot.
br
frankie


>From: "Jeff Trawick" <trawick@gmail.com>
>Reply-To: dev@httpd.apache.org
>To: dev@httpd.apache.org
>Subject: Re: process the request
>Date: Tue, 9 Jan 2007 13:32:43 -0500
>
>On 1/9/07, �� �鲩 <laronfin@hotmail.com> wrote:
>>hello
>>
>>I am reading the code of apache. Is there anybody who knows whether
>>ap_run_pre_connection() and ap_run_process_connection() are 
>>functions or
>>macro? and where is the definition for those two , as i can not 
>>find any
>>detailed code for them?
>
>macros
>
>The chase begins with http_connection.h:
>
>/**
>* This hook gives protocol modules an opportunity to set everything 
>up
>* before calling the protocol handler.  All pre-connection hooks are
>* run until one returns something other than ok or decline
>* @param c The connection on which the request has been received.
>* @param csd The mechanism on which this connection is to be read.
>*            Most times this will be a socket, but it is up to the 
>module
>*            that accepts the request to determine the exact type.
>* @return OK or DECLINED
>*/
>AP_DECLARE_HOOK(int,pre_connection,(conn_rec *c, void *csd))
>
>/**
>* This hook implements different protocols.  After a connection has 
>been
>* established, the protocol module must read and serve the request.  
>This
>* function does that for each protocol module.  The first protocol 
>module
>* to handle the request is the last module run.
>* @param c The connection on which the request has been received.
>* @return OK or DECLINED
>*/
>AP_DECLARE_HOOK(int,process_connection,(conn_rec *c))
>
>
>What do you want to find out?  The actual implementation isn't so
>interesting.  If you want to see how to implement your own 
>connection
>hook, see how the "process_connection" string is used in Apache in a
>few macro invocations.

_________________________________________________________________
��������ص����ѽ��н������������  Live Messenger; 
http://get.live.com/messenger/overview