Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 pats@acm.org does not designate 209.86.89.68 as permitted sender)
Message-ID: <53733409.5060305@acm.org>
Date: Wed, 14 May 2014 02:14:49 -0700
From: Patricia Shanahan <pats@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dev@river.apache.org
Subject: Re: The King of all Bugs
References: <53733158.7020102@zeus.net.au>
In-Reply-To: <53733158.7020102@zeus.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

ByteBuffer is a subclass of Buffer, whose documentation says, under 
"Thread Safety", "Buffers are not safe for use by multiple concurrent 
threads. If a buffer is to be used by more than one thread then access 
to the buffer should be controlled by appropriate synchronization."

Is access controlled by appropriate synchronization? How are the buffers 
communicated between the threads?

Patricia

On 5/14/2014 2:03 AM, Peter Firmstone wrote:
> One of the things I like about JERI is it's multiplexing and multithreaded.
>
> What I don't like about JERI is, it passes ByteBuffers between calling
> threads and pool threads.
>
> Who can guess what's wrong with that?
>
> Peter.