On Tue, 2010-04-27 at 22:38 +0200, [email protected] wrote: > Hi Oleg, > > Thanks for your explanation. Just curious to know if this was a design > decision, or if it might change in the future. >
It was a conscious design decision which is unlikely to change. Absence of static / global code helps ensure HttpClient can work correctly in managed environments such as JEE containers with a complex class loader hierarchy. Oleg > Regards, > - Willem > > On 04/26/2010 09:55 PM, Oleg Kalnichevski wrote: > > Willem, > > > > HttpClient 4 does not provide a means of setting global parameters. You > > can provide a custom HttpClient implementation that pre-populates > > certain default parameters upon instantiation and use this class across > > your application. Those parameters, however, will not apply to 3rd party > > libraries if they create HttpClient instances internally. > > > > Oleg > > --------------------------------------------------------------------- > 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]
