On Fri, 2007-09-14 at 16:16 +0200, Roland Weber wrote:
> > class SomeParams extends BasicHttpParams {
> >
> > public static final String SOME_VALUE = "some.value";
> >
> > public String getSomeValue() {
> > return (String) getParameter(SOME_VALUE);
> > }
> >
> > public void setSomeValue(final String value) {
> > setParameter(SOME_VALUE, value);
> > }
> >
> > }
> >
> > Those classes could be arranged into a hierarchy, as you suggested.
>
> This is pretty close to the 3.x style. I felt that the
> static utility methods were an improvement over that.
> By deriving from BasicHttpParams, a specific implementation
> of the HttpParams interface is mandated. Also, a simple
> tree would not help to define an AllClientParams which
> ties together connection, auth, cookie and other params.
> This can only be done easily on the interface level.
>
Hi Roland
All right. I just thought I should throw some ideas into the mix.
We can deal with Spring friendly parameter beans at some later point
(past BETA1). Feel free to proceed with your original plan.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
