You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by peter royal <pr...@apache.org> on 2007/08/02 16:55:01 UTC

Re: Unsafe concurrency issue in SocketIoProcessor ?

On Jul 30, 2007, at 11:50 PM, James Im wrote:
> An alternative to synchronization would be to declare the selector
> final. However this doesn't seems to be possible without some broader
> refactoring.

... which i would love to see if you want to take it on :)

-pete


-- 
proyal@apache.org - http://fotap.org/~osi

Re: Unsafe concurrency issue in SocketIoProcessor ?

Posted by Mike Heath <mh...@apache.org>.

On Thu, 2007-08-02 at 07:55 -0700, peter royal wrote:
> On Jul 30, 2007, at 11:50 PM, James Im wrote:
> > An alternative to synchronization would be to declare the selector
> > final. However this doesn't seems to be possible without some broader
> > refactoring.
> 
> ... which i would love to see if you want to take it on :)

In TRUNK the selector is already declared final in SocketIoProcessor.