Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <509728833.1249298115236.JavaMail.jira@brutus>
Date: Mon, 3 Aug 2009 04:15:15 -0700 (PDT)
From: "Niall Pemberton (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (CODEC-55) make all "business" method
 implementations of public API thread safe
In-Reply-To: <26896886.1191789710570.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niall Pemberton updated CODEC-55:
---------------------------------

    Attachment: CODEC-55-Wrapper-Implementations.patch

An alternative solution is to provide wrappers that only expose the Encoder/Decoder methods.

Attaching CODEC-55-Wrapper-Implementations.patch which contains:

 * StringEncoderWrapper - wrapper for StringEncoder implementations - can be used to resolve DoubleMetaphone, Metaphone, RefinedSoundex and Soundex thread safety issues
 * StringCodecWrapper  - wrapper for StringEncoder and StringDecoder implementations - can be used to resolve QCodec thread safety issue (making charset final has already been committed).

The other issue was with the protected fields in URLCodec - changing them to final would break binary compatibility but also its less of an issue IMO since URLCodec used directly will not have an issue as those fields are not exposed - its only implementations that extend from URLCodec that could have problems.

> 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
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.