Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <200509202323.j8KNN3D26132@devsys.jaguNET.com>
Subject: Re: Issues for 2.1.8
To: dev@httpd.apache.org
Date: Tue, 20 Sep 2005 19:22:59 -0400 (EDT)
Reply-To: jim@jaguNET.com
In-Reply-To: <200509202137.59715.nick@webthing.com> from "Nick Kew" at Sep 20,
 2005 09:37:58 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Nick Kew wrote:
> 
> I agree about both of those.  And I'd say the same even more strongly for
> mod_dbd, simply because it (or whatever it becomes when updated in the
> light of real-life experience) should become the basis of a new generation
> of applications.  If it's there, it'll start to permeate the Usual Suspects
> like mod_perl.  If not, we'll still have the old situation of Perl, Python,
> PHP, Tcl, Authentication, Logging etc each maintaining its own separate
> database connections, and having to reinvent the connection pooling
> wheel if they want to if they want to improve scalability.
> 

People will not use it unless they can *really* trust a module. Simply
expecting people to migrate to it because of the theoretical
benefits isn't quite wise, until it has proven itself. The idea is
to make it easier for people to have access to a module, use it
and test it. More exposure means more feedback and more bug-fixes
(hopefully :) ). But simply "being there" isn't enough to
expect world-wide usage, but "being there" is enough to hope
that people have easier access to play around with it.

-- 
=======================================================================
 Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
           "If you can dodge a wrench, you can dodge a ball."