Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: ping for http in mod_proxy
Date: Fri, 15 Feb 2008 17:03:38 +0100
Message-ID: 
 <99EA83DCDE961346AFA9B5EC33FEC08B46497C@VF-MBX11.internal.vodafone.com>
In-Reply-To: <C3DB1D6C.A6DB7%Brian.Akins@turner.com>
Thread-Topic: Re: ping for http in mod_proxy
Thread-Index: Achv030UK6179hXmTAKxFk2aT2JbLwAAKryQAAVarrwAAIgC0A==
References: 
 <99EA83DCDE961346AFA9B5EC33FEC08B46493E@VF-MBX11.internal.vodafone.com>
 <C3DB1D6C.A6DB7%Brian.Akins@turner.com>
From: =?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_VF-Group?=
 <ruediger.pluem@vodafone.com>
To: <dev@httpd.apache.org>

=20

> -----Urspr=FCngliche Nachricht-----
> Von: Akins, Brian=20
> Gesendet: Freitag, 15. Februar 2008 16:44
> An: dev@httpd.apache.org
> Betreff: Re: ping for http in mod_proxy
>=20
> On 2/15/08 8:13 AM, "Pl=FCm, R=FCdiger, VF-Group"=20
> <ruediger.pluem@vodafone.com>
> wrote:
>=20
> =20
> > Any specific reason why we need to add an hook here and why=20
> this cannot be
> > done by the existing provider (interface). I am scared of=20
> adding another
> > level of indirection here if it is not really needed and=20
> things can be already
> > done with the existing infrastructure.
>=20
>=20
> I like hooks bcs providers are "one-shot."  I use both, but=20
> find my self
> using hooks more and more.
>=20
> A good example is the discussion around having stacked providers in
> mod_cache.  If it were a hook, you'd already have that...
>=20
> Providers are good when you will have one, and only one,=20
> "thing" that needs
> to munge/manipulate/compute like database stuff.  With the=20
> proxy stuff, it
> looks like we want "n" things to be able to manipulate the=20
> data.  Once you
> make the leap from 1 to 2, might as well make it a hook.

But in the Auth framework we also work with providers and may call
more then one provider per request to do authn / authz. So I guess
this will be also doable. My main point is that I want to avoid
using both hook and provider if not really needed, as it

- creates unneeded overhead which lowers performance
- makes it harder to extend things with own modules as things are
  more complex
- make debugging harder

So as far as possible for solving the problem in a flexible manner
I would like to stick to KISS.

Regards

R=FCdiger