I would like to raise (or keep alive) this use case but cannot edit the wiki (so I hope the list is the right place to raise it):

OrthogonalInstrumentation

It would be nice if HttpClient provides a way to perform configuration either at a global scope, or according to some criteria, independent of direct programmatic usage; for example through system properties, static/global configuration mutators, or classloader lookups. This would allow client applications to configure or modify http client behavior when Commons HttpClient is used by an intermediary library which does not or should not expose access to HttpClient. You can be sure there will be libraries that use HttpClient internally, but will not expose it, locking consumer applications out of customizing http client behavior.

Aaron Hamid



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to