DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15435>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15435 New Preferences Architecture ------- Additional Comments From [EMAIL PROTECTED] 2003-09-08 16:11 ------- Hello Oleg, I'm currently stuck at a customer site and can dial in only occasionally. Since I'm unable to browse through the source, could you consider the following two use cases? 1. A servlet class is instantiated multiple times with different config, but in the same classloader context. Can different instances of the servlet create HttpClient instances with different parameters? 2. A framework uses HttpClient and has it's own mechanism for defining properties. How tricky is it to pass the properties - once they are loaded - to the Http Client? Loading the set of default properties should be initiated by the application. I don't see a need for an automatic loading mechanism, or automatic selection of an HttpParamsFactory. Make it a one-liner to choose a factory and delegate that responsibility to the application (or the framework) that is using the Http Client. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
