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-04 19:51 ------- > HttpParams: generic parameters and conversion methods from and to strings > HttpClientParams: specific getters and setters for the client's properties, > kept in attributes. Constructor and/or readFrom(HttpParams) to initialize > the attributes, and saveTo(HttpParams) to write them back. > HttpMethodParams: like HttpClientParams, just for the HttpMethodBase params > HttpGetMethodParams: derived from HttpMethodParams, adding some GET-specific > attributes. > ...and so on for every component that defines parameters Roland, how about this? interface HttpGenericParams: implemented by HttpParams interface HttpClientParams: derived from HttpGenericParams, implemented by HttpClient interface HttpHttpParams: derived from HttpGenericParams, implemented by HttpMethodBase Interface implementations act as a facade that abstract the intricacies of physical representation and conversion of parameters contained in the associated HttpParams instance. All parameters can still be accessed directly through HttpGenericParams interface. That would also be a way to interact with non-standard parameters Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
