Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 64964 invoked from network); 10 Feb 2009 17:25:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Feb 2009 17:25:41 -0000 Received: (qmail 48537 invoked by uid 500); 10 Feb 2009 17:25:36 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 48518 invoked by uid 500); 10 Feb 2009 17:25:36 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 48509 invoked by uid 99); 10 Feb 2009 17:25:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2009 09:25:36 -0800 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of adam.prime@utoronto.ca does not designate 216.220.44.220 as permitted sender) Received: from [216.220.44.220] (HELO mail.oanda.com) (216.220.44.220) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2009 17:25:28 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.oanda.com (Postfix) with ESMTP id 7D4ACEC03D; Tue, 10 Feb 2009 12:25:07 -0500 (EST) Received: from mail.oanda.com ([127.0.0.1]) by localhost (mail.q9.oanda.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28258-02; Tue, 10 Feb 2009 12:25:07 -0500 (EST) Received: from gateway.oanda.com (eddie.dev.oanda.com [10.1.1.10]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.oanda.com (Postfix) with ESMTPS id 671B5EC038; Tue, 10 Feb 2009 12:25:07 -0500 (EST) Received: from [10.1.5.118] (primepc.dev.oanda.com [10.1.5.118]) by eddie.dev.oanda.com (Postfix) with ESMTP id 505C364084; Tue, 10 Feb 2009 12:25:07 -0500 (EST) Message-ID: <4991B873.5040106@utoronto.ca> Date: Tue, 10 Feb 2009 12:25:07 -0500 From: Adam Prime User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Patrick Galbraith CC: modperl@perl.apache.org Subject: Re: Apache request processing phases question References: <4991AEBF.8070006@patg.net> In-Reply-To: <4991AEBF.8070006@patg.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Patrick Galbraith wrote: > Hi all, > > I'm in the midst of writing a book currently, and am covering the > sections in the book on mod_perl and Apache. > > In previous texts for Apache 1.3, it > would show 11 phases. In the document on > http://httpd.apache.org/docs/2.2/developer/request.html, it shows 4 > primary phases, each having their own steps within. > > Is it accurate to say then that for Apache 2.2, there are four request > processing phases in the request cycle? How does this reconcile with > 1.3 having 11? Are the new phases just a different way of grouping steps > the used > to be considered their own phases? The 11 phases in 1.3 map to all the steps within the 4 major phases. I think there are new ones added in 2.0, namely map_to_storage. For the mod_perl angle on phases, I'd suggest having a look at this section of the documentation: http://perl.apache.org/docs/2.0/user/index.html specifically, the part titled 'Part V: mod_perl Handlers', including: http://perl.apache.org/docs/2.0/user/handlers/server.html and http://perl.apache.org/docs/2.0/user/handlers/http.html If you're talking about Apache though, not mod_perl, then you'd probably be better off to ask the one of the httpd lists. Adam