> Some of the stuff now in encodingUtil is dependent on HttpClient > NameValuePair etc. and seems specifically for managing the > encoding/building of query strings. > > The ASCII stuff is just dependent in that it throws HttpclientError's > > I suspect the later will be usefull to move out, while the former will > be difficult without added complexity. >
Mark, I agree. See what can be reused and makes sense to be reused. We'll play along. > I wonder what the best "design pattern" is for the ASCII conversion > stuff. Is ASCII conversion to be considered "encoding" or string > "translation" > > See CharSetUtils in [lang]: > http://jakarta.apache.org/commons/lang/api.1.0.1/org/apache/commons/lang/CharSetUtils.html#translate(java.lang.String,%20java.lang.String,%20java.lang.String) > It can certainly be seen as either depending on your particular angle. Design purism aside, for a very simple reason of keeping the number of external dependencies for HttpClient to the minimum, I would rather see these conversion routines a part of codec. I doubt HttpClient should be made dependent on Commons-Lang just because of ASCII conversion routines. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
