Jody Garnett a écrit :
> So you understand how Executor is isolating the implementor of Callable
> from external influence; in order to have more flexibility and control
> over what is going on. The trade off and motivations for their strict
> design decisions are clear to you ... do you actually agree with them?
I must have missed something...
Executor can not assumes such isolation since Callable was given by the user. I
would be surprised if Sun expressed such a motivation in their design, but
maybe
I just missed it.
> Can I ask if in your experience you are holding on to your Callables
> after passing them to an Executor?
I do not hold Callables, but even if I did I don't see any harm I could do.
- The user could invokes addProgressListener.
Right, him too want progress.
- He could invokes removeProgressListener(...); well, since he can't know
the references to other listeners (at least through our API) it will have
no effect.
- He can invokes cancel() - so I assume he really want to cancel.
If holding Callable is considered harmful, I must have missed something?
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
