Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #23109
| From | markspace <markspace@nospam.nospam> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: polling IRQs in a thread's code |
| Date | 2013-03-24 21:16 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <kioiue$tfo$1@dont-email.me> (permalink) |
| References | <thread-20130324233549@ram.dialup.fu-berlin.de> <nospam-1218C9.22571124032013@news.aioe.org> |
On 3/24/2013 7:57 PM, John B. Matthews wrote: > Also consider SwingWorker<T,V>. That's an excellent point, I completely spaced on the GUI part of his question. If GUI = Swing, then SwingWorker is an excellent solution to many problems. Also, SwingWorkers can be put in executors, and since it returns a Future, there's a convenient Future#cancel() method to kill the thing (which does use Thread#interrupt as I suggested earlier).
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: polling IRQs in a thread's code "John B. Matthews" <nospam@nospam.invalid> - 2013-03-24 22:57 -0400 Re: polling IRQs in a thread's code markspace <markspace@nospam.nospam> - 2013-03-24 21:16 -0700
csiph-web