Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <user@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.198.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=e+xLM+H81pklVS+W4qz699p8rVhD8vDxFEL8d1iW6WQW995CMxL19nLB3SuD6k3/cE+lQDb2GO8MQxSA9WFqYd/qncsYCIJ4GFR2ip/owgndTdlGS+bPSTEdzwBe436qyq1E9Mpvr3SGPrPtMnkTFzLWRCHnToRBn5Fyjwa9JQw=
Message-ID: <25aac9fc0710070341n78f7a22dg3c1988cda341075c@mail.gmail.com>
Date: Sun, 7 Oct 2007 11:41:26 +0100
From: sebb <sebbaz@gmail.com>
To: "Jakarta Commons Users List" <user@commons.apache.org>
Subject: Re: codec - thread safe
In-Reply-To: <1191742284.6050.2.camel@simon-laptop>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <49645ccf0709292130ud20383y756f33415e224e31@mail.gmail.com>
	 <31cc37360710052122i4712da78i692bec260321f6e@mail.gmail.com>
	 <49645ccf0710061350i646dfc19i83a44b0e24bf360@mail.gmail.com>
	 <86aa493a0710061401w3811cc11h1e5945cdb7a4e453@mail.gmail.com>
	 <49645ccf0710062131u7b595636n48d3be87249dd62@mail.gmail.com>
	 <1191742284.6050.2.camel@simon-laptop>

On 07/10/2007, simon <simon.kitching@chello.at> wrote:
> On Sat, 2007-10-06 at 23:31 -0500, Qingtian Wang wrote:
> > Well, it's pick-your-poison kind of a deal. Either block on one
> > instance and take a performance hit, or burn up the memory with lots
> > of instances.....
> >
> > But in the case of BCodec, I think encode/decode is thread safe.
> > Unfortunately per Henri, that's not generally true for others.
> >
> > Well, let me make it clear that I am a total layman on codec. But it
> > seems to me it's not that difficult to implement all the codec methods
> > in a thread safe manner, without sync blocks.
> >
> > Can the dev team make that happen? - a humble request from a user.
>
> The think about open source is that there is no distinction between
> developer and user. The developers develop because they want to use the
> code. And when somebody wants to use a feature that doesn't exist, then
> they can develop it.
>
> In short, if you want this feature, you can do this yourself and post a
> patch to this list so it gets included in the next release. There is no
> paid "dev team" for any of the commons code.

Might be better to create a JIRA issue and attach the patch to that:
* others can easily see that the issue has been reported
* patches can get mangled when posted to lists, and are more difficult
to keep track of.

For Codec, start here:
http://commons.apache.org/codec/issue-tracking.html

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org