commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IO-342) Add getChartset/getBOMCharset methods to ByteOrderMark/BOMInputStream
Date Wed, 08 Aug 2012 09:02:10 GMT

    [ https://issues.apache.org/jira/browse/IO-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430960#comment-13430960
] 

Joerg Schaible commented on IO-342:
-----------------------------------

There's in any case the issue with serialization compatibility. You have to declare the new
member as transient and ensure that it is initialized again after deserialization.
                
> Add getChartset/getBOMCharset methods to ByteOrderMark/BOMInputStream
> ---------------------------------------------------------------------
>
>                 Key: IO-342
>                 URL: https://issues.apache.org/jira/browse/IO-342
>             Project: Commons IO
>          Issue Type: Improvement
>          Components: Utilities
>            Reporter: Yaniv Kunda
>            Priority: Minor
>         Attachments: ByteOrderMark-charset.patch
>
>
> ByteOrderMark/BOMInputStream currently support getting the detected charset name via
getCharsetName/getBOMCharsetName.
> Calling Charset.forName() is rather expensive, and its result should be fixed throughout
the life of a JVM.  Adding a cached copy of its result in ByteOrderMark will save callers
of BOMInputStream.getBOMCharsetName this price.
> In case the JVM does not support the detected charset, the method can either throw the
standard exception or return null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message