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 13:22 ------- Some quick thoughts from here, having scanned the proposed patch only very briefly: * I like the idea of keeping parameters generic. I use the Slide WebDAV extensions, and likely there will be options that make sense to specify for that in the future (default encoding of XML requests, for example). Clients may also have preferences that they associate with HttpClient, but are not necessarily used by HttpClient. By keeping the options generic, extensions like WebDAV, and other client wrappers can use the same mechanism for setting their preferences. If you make the settings functions specific, it will be harder over time for the library to accommodate new options, and clients will not be able to extend it as easily. * The "discovery" process standard could use the approach outlined here: http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/parsers/SAXParserFactory.html#newInstance() which is as close to a "standard" as Java has for this kind of thing. * Ortwin has an excellent point, namely that the discovery process should kick in only if the caller doesn't provide default information. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
