Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Apache2::DBI
Date: Tue, 14 Jun 2005 08:20:55 -0600
Message-ID: <2F413D5F33545D4A8465BBEE900238CC45F885@cymmail.cymphonix.com>
Thread-Topic: Apache2::DBI
Thread-Index: AcVr5ihYSZCokcDvRbS1xVYr6WWtNgFBE4dw
From: "Aaron Scott" <ascott@cymphonix.com>
To: "Adam Kennedy" <adam@phase-n.com>,
	"Philip M. Gollucci" <pgollucci@p6m7g8.com>,
	"mod_perl" <modperl@perl.apache.org>


> -----Original Message-----
> From: Adam Kennedy [mailto:adam@phase-n.com]
> Sent: Tuesday, June 07, 2005 10:43 PM
> To: Philip M. Gollucci; mod_perl
> Subject: Re: Apache2::DBI
>=20
> Indeed.
>=20
> All that might be needed is a small...
>=20
> =3Dhead1 COMPATIBILITY
>=20
> Apache::DBI is compatible with both the mod_perl 1 and mod_perl 2
APIs.
>=20
> ... somewhere very near the beginning of the POD. (personally I'd have
> it right after the synopsis and before the description).
>=20
> And I'd recommend this for anyone that is going to take the "one
module
> to rule them all and in the darkness bind them" strategy :)


The mp2 API being 'the darkness'? :)  Besides compatibility with legacy
code (which isn't an issue in my case), are there any benefits to
maintaining the Apache namespace that I'm not considering?

-Aaron