You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Joerg Schaible (JIRA)" <ji...@apache.org> on 2007/11/16 14:12:43 UTC
[jira] Commented: (CODEC-59) Add methods to Base64 which work with
String instead of byte[]
[ https://issues.apache.org/jira/browse/CODEC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543066 ]
Joerg Schaible commented on CODEC-59:
-------------------------------------
As explained in CODEC-58 the term character refers 8-bit values in the RFC and 16-bit values in Java. The encoding can never receive a String, since it has no idea about the encoding of the String and the algorithm encodes arbitrary bytes. Same applies to the result of a decoding. The result of an encoding and the input of the decoding could be Strings in ASCII encoding.
> Add methods to Base64 which work with String instead of byte[]
> --------------------------------------------------------------
>
> Key: CODEC-59
> URL: https://issues.apache.org/jira/browse/CODEC-59
> Project: Commons Codec
> Issue Type: New Feature
> Reporter: Pepijn Schmitz
> Priority: Minor
>
> It would be great if the Base64 class had String encode(byte[]) and byte[] decode(String) methods. The RFC is stated in terms of "characters" for the encoding, so there should be no problem with unwarranted assumptions with this. Currently everyone is having to convert to and from Strings themselves.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.