Mike
[EMAIL PROTECTED] wrote:
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:36 -------
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?
Of course! What would my patch be worth otherwise? It is still up to you to decide if you want your HttpClient instances to share the same global defaults. One can simply set HttpClient#getParams#setDefaults(null) to make it disregard global defaults.
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?
Allow me to try to explain that with the following pseudo-code snippet:
// Select either global HttpParams or HttpClient's params or HttpMethod's params
HttpParams params = GLOBAL_DEFAULTS // Or HttpParams params = httpClient.getParams(); // Or
HttpParams params = httpMethod.getParams();
while (storage.hasMore()) { storageitem = storage.getNext(); String paramName = storageitem.getName(); Object paramValue = storageitem.getObject(); params.setParameter(paramName, paramValue); }
This may look trivial, but at the moment I can't see why we would want something more complex. I still would like to know, though, what Mike has got on his mind with the HttpParamsFactory
Cheers
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]
