[
https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640065#comment-16640065
]
Sebb commented on CODEC-55:
---------------------------
If lack of thread-safety means that there is a security issue, then just about
every Java program is at risk -
there are lots of methods/classes in the JVM which are not thread-safe.
Surely the issue is whether the methods/classes are *used* in a thread-safe
manner?
That is not something over which Apache Commons has any control.
Obviously it makes it easier for users of the API if everything is thread-safe,
but that may not be feasible or necessary in the general case.
> make all "business" method implementations of public API thread safe
> ---------------------------------------------------------------------
>
> Key: CODEC-55
> URL: https://issues.apache.org/jira/browse/CODEC-55
> Project: Commons Codec
> Issue Type: Wish
> Reporter: Qingtian Wang
> Priority: Major
> Fix For: 1.x
>
> Attachments: CODEC-55-Wrapper-Implementations.patch,
> concurrentCodecs.diff, concurrentQDiff.diff, urlcodec.patch
>
>
> Maybe most of the implementations are already thread safe. Just such that
> codec can say so in general...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
