commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ortwin Gl├╝ck <>
Subject [HttpClient] Preferences Architecture Implementation Draft II
Date Mon, 30 Sep 2002 16:59:11 GMT
This is the second iteration in finding the right architecture for the 
preferences API.
- Moved to a separate package: httpclient.config
- Configuration is not immutable.
- Configuration is now hierarchical and reflects changes in underlying 
Configurations immediately.
- The new ConfigManager links any object with a Configuration instance.
- If the user does nothing the default configuration is always used.

Sample Code

The user can set the configuration from the outside for HttpClient, 
HttpMultiClient, HttpMethod, HttpConnection. The user should not try to 
configure other classes directly:
--user app
HttpClient client = new HttpClient();
Properties patch = new Properties();
patch.setProperty(ConfigKeys.USER_AGENT, "My HTTP Client 0.01");
Configuration clientConfig = new Configuration(Configuration.DEFAULT, 
ConfigManager.setConfiguration(client, clientConfig);

HttpClient configures HttpMethod automatically IF not yet configured. 
The same way a HttpConnection is configured:
  public synchronized int executeMethod(HttpMethod method) {
    if (!ConfigManager.isConfigured(method)) {
     ConfigManager.setConfiguration(method, myConfig);
    method.execute(getState(), connection);

Low level objects use the configuration of a higher level object. The 
same applies to inner classes:
  myConfig = ConfigManager.getConfiguration(method);
  ... myConfig.getBooleanValue(ConfigKeys.IGNORE_PROTOCOL_VIOLATION);

A static class must be configured by the caller using the meta object.
Users should never try to configure low-level classes:
--caller class
  ConfigManager.setConfiguration(NTLM.class, myConfig);

  Configuration myConfig = ConfigManager.getConfiguration(NTLM.class);
  String mySecurityProvider = 


As you can see this approach generates a large overhead. This is mainly 
caused by one requirement: "Would there be a means to assign my own 
properties object to the HttpClient, HttpConnection and HttpMethod 
objects? So I could control the settings on a "client by client", 
"connection by connection",  or "method by method" basis?" by Mark R. 
Diggory, 2002-9-18.

Any single object (e.g. Cookie) must therefore know which Configuration 
applies to it. This means that the creator of an object must set its 
configuration in the ConfigManager. For static classes  the requirement 
can not be fulfilled at all. Not so nice, is it.

Please, if any of you has a good idea how to deal with this, drop me a note.


View raw message