Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
To: Chris Shiflett <shiflett@php.net>
Cc: Geoffrey Young <geoff@modperlcookbook.org>,
	Perrin Harkins <perrin@elem.com>,
	Modperl List <modperl@perl.apache.org>
Subject: Re: mod_perl presence at OSCON (and other CONs) is at danger
References: <20040609010045.98925.qmail@web52802.mail.yahoo.com>
From: merlyn@stonehenge.com (Randal L. Schwartz)
Date: 08 Jun 2004 18:33:30 -0700
In-Reply-To: <20040609010045.98925.qmail@web52802.mail.yahoo.com>
Message-ID: <86ekopv7kl.fsf@blue.stonehenge.com>
Lines: 16
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

>>>>> "Chris" == Chris Shiflett <shiflett@php.net> writes:

Chris> Well, surely there are plenty of people fully utilizing mod_perl for all
Chris> it's worth. Are there things you can speak/write about more to illustrate
Chris> the benefit of the Apache API? Input/output filters seem like one such
Chris> thing, and surely there are others.

I've personally used trans, postreadrequest, log, mime, and auth, as
well as the normal content handler.  Each type of the 14 handler slots
provides a specific contribution to the response given by a request.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html