1.2.2 it is then :-) I agree with maintaining 1.2.2 compatibility, it is a bit harsh to require 1.4 to perform base64 encoding. Unfortunately it would make life a lot easier with regards to charset encoding ...
It should be possible to use OutputStreamWriter and InputStreamReader internally to perform the conversions without incurring much of a performance overhead. For example a CharByteEngine??? could use OutputStreamWriter internally to perform charset encoding. In many cases OutputStreamWriter and InputStreamReader can be used directly, it is the cases where byte to char conversion is required during output streaming that require an encoder for transforming between chars and bytes. Perhaps I'm missing something here though ... I also think it would be useful to be able to perform charset conversion without depending on streams. > -----Original Message----- > From: Gary Gregory [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 11 November 2003 4:19 AM > To: 'Jakarta Commons Developers List' > Subject: RE: [codec] Streamable Codec Framework > > > Yes, no problem, 1.2.2. > > Gary > > > -----Original Message----- > > From: Tim O'Brien [mailto:[EMAIL PROTECTED] > > Sent: Monday, November 10, 2003 08:10 > > To: Jakarta Commons Developers List > > Subject: RE: [codec] Streamable Codec Framework > > > > Oleg, this is understood - 1.2.2 should be our LCD for codec. > > > > Tim > > > > > > On Mon, 10 Nov 2003 [EMAIL PROTECTED] wrote: > > > > > Tim, Gary, et al > > > Streamable codec framework would be a welcome addition to Commons > > > Codec. However, as far as we (Commons HttpClient) are > concerned, the > > > decision > > to > > > ditch java 1.2.2 support would render Codec unusable for > us (and I'd > > guess > > > a few other projects that still need to maintain java 1.2.2 > > compatibility). > > > Not that we like it too much, but because lots of our users still > > > demand it. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
