Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: domain of torsten.foertsch@gmx.net
 designates 213.165.64.20 as permitted sender)
From: Torsten Foertsch <torsten.foertsch@gmx.net>
To: modperl@perl.apache.org
Subject: [ANNOUNCE]Apache2::Translation
Date: Wed, 8 Mar 2006 13:48:12 +0100
User-Agent: KMail/1.7.1
Cc: Glenn Martin <lifewarped@yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart15232342.OGcAxGjfvC";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200603081348.20718.torsten.foertsch@gmx.net>

--nextPart15232342.OGcAxGjfvC
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

This email is to announce the new Apache2::Translation:
http://search.cpan.org/~opi/Apache2-Translation-0.08/lib/Apache2/Translatio=
n.pod

Apache2::Translation can be looked at in 2 ways:

1) it is similar to mod_rewrite in that it lives mostly in the uri translat=
ion=20
phase where it can change/route/redirect/whatever the request. Unlike=20
mod_rewrite it fetches it's configuration from a database at runtime. Hence=
,=20
the rules can be changed without restarting Apache.

2) dynamic configuration. It can apply configuration directives read from a=
=20
database apply to the current request. Thus, it can be seen as a .htaccess=
=20
replacement for modperl handlers where real files and directories are not=20
necessary involved. But it can more than that. Almost anything=20
request-specific can be applied.

Hope some people find it useful...

Torsten

--nextPart15232342.OGcAxGjfvC
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBEDtKUwicyCTir8T4RAqCfAJsFnzcHWRB9UWfXs4o1Gff+biJ0JwCgxeLv
oEO1F3MG1/BLHBpiAgOOQsY=
=qTS4
-----END PGP SIGNATURE-----

--nextPart15232342.OGcAxGjfvC--