commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Redington <>
Subject Re: [codec] RE:
Date Tue, 04 Feb 2003 18:24:06 GMT

Hi all,

     personally I favour Ryan's suggestion of setting flags (and/or 
system properties) separately to obtain non-RFC compliant behaviour (or 
to specify which RFC to follow, where they conflict), or to specify 
that exceptions should be raised when encountering a non-Base64 char, 
rather than adding additional args to method signatures.

Given the wide usage of this code, and the need to inter-operate 
smoothly with other implementations that may or may not comply with a 
particular RFC, giving the end-user as much flexibility as possible is 
probably a good thing and shouldn't add too much complexity to the 
code. Maybe both approaches would be appropriate.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message