commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <vmas...@octo.com>
Subject RE: [HttpClient] Preferences Architecture Implementation Draft II
Date Sat, 05 Oct 2002 17:18:40 GMT


> -----Original Message-----
> From: news [mailto:news@main.gmane.org] On Behalf Of Costin Manolache
> Sent: 01 October 2002 20:27
> To: commons-dev@jakarta.apache.org
> Subject: Re: [HttpClient] Preferences Architecture Implementation
Draft II
> 
> I personally thing this is a very bad idea.

I agree.

> 
> There are already enough 'config' architectures:
> - ant/jmx/bean style, with introspection used to call java bean
> setters ( with or without Digester )
> - jdk1.4 preferences/JNDI for hierarchical config and components
> getting the info themself.
> - simple Properties storing data with hierarchical names
> 
> Defining another config API and impl - and doing it specifically
> for http client is even worse - as it has implications for the
> code that would like to use http-client and already has its
> own config mechanisms.
> 
> I personally think that for components like http client, java-bean
> style of configuration is the best and in no case should they
> define their own config files and apis.

+1

> 
> Except maybe using a common API modeled after jdk1.4 ( similar with
> commons-logging ) that wraps jdk1.4 logging, jndi and other
> hierarchical-storage configs ( for those who prefer this instead
> of setters ).

Please use the javabeans approach. HttpClient should remain a framework
and not an application. Also, please use the Inversion of Control
pattern as much as possible to make the framework as flexible as
possible.

Thanks Costin.

-Vincent

[snip]



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message