Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44CC58D4.3040700@rowe-clan.net>
Date: Sun, 30 Jul 2006 01:59:32 -0500
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
User-Agent: Thunderbird 1.5.0.4 (X11/20060614)
MIME-Version: 1.0
To: Eli Marmor <marmor@netmask.it>
CC: david reid <david@jetnet.co.uk>,  dev@apr.apache.org,
 apreq-dev@httpd.apache.org
Subject: Re: apreq -> apr-util
References: <44CA47B9.5060108@jetnet.co.uk> <44CBCA08.497F142E@netmask.it>
In-Reply-To: <44CBCA08.497F142E@netmask.it>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Eli Marmor wrote:
> 
> Bill: as an insider, what do you suggest?  to start with apr-util, and
> only then integrating the other parts in httpd and mod_perl, or to try
> to do all of these projects together?

Personal opinion?  Only sane way to approach this is to take every element
that's a good, broad fit into apr-util and plug it in there (usual votes to
accept etc.)

Then take the slightly less generic, more httpd-ish and propose those into
httpd core.

That should solve the 80/20, then propose the perl glue into modperl and
voila - useful fn's for everyone, close integration, and specific modperl
connectivity where it belongs.

Bill