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-19 08:36 ------- Hi folks, my apologies for taking so long to look into this again. The current architecture is definitely useful, so take these comments as something that might just as well end up on the lower end of some to-do list :-) There are two things I'm not quite happy with: 1. Taking HttpClient as an example, I'm missing a constructor HttpClient(HttpClientParams) I really want a way to instantiate classes without triggering the properties loading mechanism at all. Second best would be a setParams(HttpClientParams), so I can simply copy the params of another client. Ok, the copying idea makes more sense using HttpMethodParams and HttpMethodBase as an example :-) 2. From a design point of view, shouldn't HttpMethodParams better be an attribute than a base class of HttpClientParams? Since that would require parsing properties into different params objects, I don't really think it's worth the effort. I just want to put it up for discussion. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
