hc-httpclient-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Defining preferences using properties
Date Sun, 17 Sep 2006 17:07:14 GMT
On 17/09/06, Roland Weber <http-async@dubioso.net> wrote:
> Hi Sebastian,
>
> > Qualified classnames for the conversion makes it harder to use.
> >
> > Given that there aren't many different types, I'm intending to use a
> > simple naming convention that is documented in an example parameters
> > file.
>
> I was thinking ahead for the future. We don't know what kind of
> parameters may be required in the future. Arrays of MessageFormat
> to parse dates in cookies, for example?
>

It's unlikely these will need to be overridden by the casual user.

I've now added an option to run a BeanShell script at start-up, if
necessary the user can write the Java code to set up the defaults
directly.

> > It is easy enough for the user to look at the parameter page and work
> > out the corresponding property name.
>
> Sure. I still recommend $int rather than $Integer :-)
>

I went with the types as shown in the preference api documentation.

> > But if you are considering adding something to HttpClient, then
> > perhaps it would be worth considering some form of parameter name +
> > type registry, perhaps via annotations. This information could be used
> > to validate parameters, and the list could be compared against the
> > user documentation. Or maybe the documentation could be generated from
> > the annotations?
>
> I doubt we'll have spare time for that before 2008.
>

OK.

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-user-help@jakarta.apache.org


Mime
View raw message