On Sat, 2007-05-26 at 20:55 +0200, Roland Weber wrote:
> > Step 1:
> > Create AbstractHttpParams
>
> done
>
> > Step 2:
> > Declare set/getDefaults as internal and not part of
> > the official API.
>
> done
>
> > Step 3:
> > Remove the setDefaults() in HttpRequestExecutor.
>
> done
>
> In ElementalHttp{Get|Post}, I've used request.setParams(),
> since .setDefaults() is now an internal API. In the tests
> and in HttpClient, I've used .setDefaults().
>
> Oleg, the NHttpReverseProxy example still uses .setDefaults().
> I can live with that.
>
> I'll let this settle for a while before I dig deeper
> into the hierarchies we need. I'll stick to the client
> side for that. Currently, parameters are linked in
> - AbstractHttp*Connection
> - DefaultClientRequestDirector
>
Hi Roland
I would like to have #setDefaults() calls moved from
AbstractHttp*Connection to the corresponding HTTP services. Connection
objects ought not meddle with HTTP parameter hierarchies.
> We might build a parameter hierarchy for the conn mgr, too.
> In the director and for the connection, we can build the
> hierarchy once and store it in the request and connection,
> respectively. That is not possible for conn mgrs that are
> used by multiple clients. Per-manager parameters like
> connection limits should probably not be hierarchical at
> all. Per-operation parameters could be passed as argument
> to the respective operation, allowing each client to
> provide it's own hierarchy (which should include the
> conn mgr's params in it).
>
Presently Http*Connection objects do not contain a local HttpParams
instance. They only read values from a HttpParams parameter once at the
initialization time. If we are not going to expose ClientConnection
instances to the user, there is probably no point in building a
parameter hierarchy for connection objects.
Anyways, please do feel free to go ahead with this idea
Oleg
> If anyone has ideas or questions, please share them.
>
> cheers,
> Roland
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
