|
Re: JCiP Memoizer: msg#00028java.jsr.166-concurrency
It's only 1am here, but it looks funny to me, too. I remember that the intent was that a thread interrupted in the middle of a long computation should not leave the incomplete computation lying around in the cache. So any thread that detects a cancellation removes the task from the cache and tries again. But an interruption during ft.run() will not be seen as a cancellation of the FutureTask, so this doesn't work. The fix would probably involve checking for interruption after the call to ft.run(). I just read Joe's response, but I don't see how a Memoizer-created FutureTask, encapsulated as it is, could ever be cancelled. (Also, I don't think cache.remove(arg, f) ensures that only the task creator removes the task; it just ensures that the only the failed task is removed.) --tim On 10/18/06, Joe Bowbeer <
joe.bowbeer@xxxxxxxxx> wrote: On 10/17/06, Alexandru Popescu < the.mindstorm.mailinglist@xxxxxxxxx> wrote: _______________________________________________ Concurrency-interest mailing list Concurrency-interest@xxxxxxxxxxxxxxxxxxxx http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: JCiP Memoizer, Joe Bowbeer |
|---|---|
| Next by Date: | Re: JCiP Memoizer, Alexandru Popescu |
| Previous by Thread: | Re: JCiP Memoizer, Joe Bowbeer |
| Next by Thread: | Re: JCiP Memoizer, Alexandru Popescu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |