[
https://issues.apache.org/jira/browse/CODEC-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987031#action_12987031
]
Gary Gregory commented on CODEC-95:
-----------------------------------
Well if you explain it intelligently like that how can I not bend to your will?
:)
Great explanation and I see the issue different now.
Your POV is then that we are designing defensively for multi threaded clients.
I've never considered these codecs to be expensive enough to be worth caching.
I'd like us to consider whether MT safety is really is a goal we want at the
expense of IMO clarity. I never like to see calls large ctors.
I am just not convinced on the need for these codec objects to mt safe.
We want to stay backward compatible of course so this might be a moot point!
> Base64: optionally allow strict parsing of base64 strings
> ---------------------------------------------------------
>
> Key: CODEC-95
> URL: https://issues.apache.org/jira/browse/CODEC-95
> Project: Commons Codec
> Issue Type: Improvement
> Affects Versions: 1.4
> Reporter: Adam Rabung
> Priority: Minor
> Attachments: strictMode.zip
>
>
> Currently, Codec skips base64 characters that are outside of the encode
> table. I realize this is perfectly to spec, but I wonder if other users
> might appreciate a "strict" mode that throws an exception when one of these
> illegal characters are encountered. For example, I would love an exception
> to be thrown here:
> new Base64().decode("!@#$ iHaveIllegalCharsAtBeginningAndEnd %^&"));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
