Groups > comp.lang.java.programmer > #28458

Re: threadpool and ui paint

From	markspace <markspace@nospam.nospam>
Newsgroups	comp.lang.java.programmer
Subject	Re: threadpool and ui paint
Date	2014-05-13 10:46 -0700
Organization	A noiseless patient Spider
Message-ID	<lktlp3$giu$1@dont-email.me> (permalink)
References	<lkshvd$143g$1@ariadne.rz.tu-clausthal.de> <lkt242$qea$1@dont-email.me> <lkti7l$lhu$1@dont-email.me> <lktkc1$6eh$1@dont-email.me>

Show all headers | View raw

On 5/13/2014 10:22 AM, Eric Sosman wrote:

>      I don't think using synchronizedCollection() helps here.  It will
> ensure that individual actions on the collection are atomic, but will
> not atomize (?!) sequences of actions.  In particular, you can still
> get a ConcurrentModificationException.

Yes, if the collection is modified as the EDT is attempting to read it, 
that'll happen.

I'm not sure that MVC will solve all of these issues, but a better 
architecture will definitely help decompose the problem(s) into easier 
pieces.  I don't really like the way M. Kraus has designed his threading 
code at all.

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

threadpool and ui paint Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-05-13 09:35 +0200
  Re: threadpool and ui paint Joerg Meier <joergmmeier@arcor.de> - 2014-05-13 11:26 +0200
    Re: threadpool and ui paint markspace <markspace@nospam.nospam> - 2014-05-13 09:35 -0700
  Re: threadpool and ui paint Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-05-13 08:10 -0400
    Re: threadpool and ui paint markspace <markspace@nospam.nospam> - 2014-05-13 09:45 -0700
      Re: threadpool and ui paint Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-05-13 13:22 -0400
        Re: threadpool and ui paint markspace <markspace@nospam.nospam> - 2014-05-13 10:46 -0700

csiph-web