commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <joerg.schai...@gmx.de>
Subject Re: [codec] Moving on to codec 2.0
Date Thu, 31 Mar 2011 21:12:24 GMT
Hi Jochen,

Jochen Wiedmann wrote:

> On Thu, Mar 31, 2011 at 9:23 PM, Julius Davies <juliusdavies@gmail.com>
> wrote:
> 
>> I'm confused.  We support streaming for Base64 since codec-1.4 (and
>> now Base32 since codec-1.5).  You committed the Base64InputStream
>> patch, Jochen!
>>
>> https://issues.apache.org/jira/browse/CODEC-69
>>
>> Is there other streaming you would like to see in commons-codec?
> 
> 
> Sure, you still dropped a lot of functionality when copying the stuff
> from ws-commons. The Encoder and Decoder classes from ws-commons are
> way more abstract and generic than the current codec stuff is and the
> SAXEncoder is just one example where this is actually useful. Not to
> mention StAX, NIO, and a lot of other places where streaming codecs
> might be useful.

Nothing of this (including minimum requirement of Java 5) requires 
automatically 2.x. As long as the API is *upward* binary compatible, you can 
improve the implementation using this features, adding new methods or new 
classes. Even generics can be added to some extend in a binary compatible 
way. This has been done for dbcp and there we deliver due to JDBC 3/4 even 
two versions.

Therefore is the question of Sebb not so limiting as you seem to imply.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message