I see. Well, its good to see people actually doing that sort of thing....
Its taken me a few months to convince my associates that we need to be
doing this.
- Matt
Oleg Kalnichevski <[EMAIL PROTECTED]>
06/26/2003 05:05 PM
Please respond to "Commons HttpClient Project"
To: Commons HttpClient Project <[EMAIL PROTECTED]>
cc:
Subject: Re: [VOTE] Re: 2.0 release - deprecate some methods?
On Thu, 2003-06-26 at 23:40, [EMAIL PROTECTED] wrote:
> I just got through Internationalizing a website... input and output. I
> ran into the exact same issues, and as Andre states, you pretty much
need
> to check everywhere for byte[] ->String and String->byte[].
Matt, we actually do. We do have a specialised class called
HttpConstants that requires a charset to be explicitly specified for all
byte[] to String and String to byte[] conversions. Httpclient's coding
guidelines require HttpConstants class to be used for ALL byte[] to
String and String to byte[] conversions. And we are VERY strict about
it.
The problem is that we can't convince just one guy to fix just one damn
method. This issue has been dragging on for 6 (six) months already and
finally has really blown out of all reasonable proportions
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
