Mailing-List: contact abdera-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of ixjonez@gmail.com designates
 64.233.162.232 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=H0Kyuefj6l5npUcPNioFiu42nw5GaLWwmcDpcgXOIJHZEd5Gbrgp4WTnVnFb8et2OmM3gz8TwmU6pqGvzUx7Q7tre92U4K+y5Uq8mhmRVFHOzaZVkFkQfDt5gBeKkCnIbxcFvDLXDUlCh3M0z24BZDp8HWtGVNZHEmMwSHgruEA=
Message-ID: <29a761a00706121250o5c207542uec21edba1d36388@mail.gmail.com>
Date: Tue, 12 Jun 2007 12:50:57 -0700
From: "Brian Moseley" <bcm@osafoundation.org>
Sender: ixjonez@gmail.com
To: abdera-user@incubator.apache.org
Subject: supporting multiple Providers
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

my server exposes several different types of resources, and i've found
it convenient to write a separate provider for each resource type.
however, AbstractRequestHandler and ProviderManager don't have any
extension points or other ability to make choices about which Provider
instance to use to handle a particular request.

i'm imagining a provider manager that chooses a provider instance
based on matching a URI pattern or a target's class. this would
require ProviderManager.getProvider having access to the request
context. does this seem reasonable?

for now i've taken the cheesy route of using a ProxyProvider class
that delegates all methods to one of three different providers based
on the target's class. would definitely prefer to have framework
support for this.