Jody Garnett a écrit :
> Changes for this commit:
> - Processors (formally ProcessFinder) is similar to Executors
> - ProcessExecutor extends Executor and is similar to ExecutorService
> - Process is implemented as we described (ie the same style as
> Callable<Map<String,Object>>)
> - Progress extends Future (and is returned by a ProcessExecutor for each
> submitted Process)
Thats sound good :)
> I have also implemented:
> - ThreadPoolProcessExecutor - implementation of ProcessExecutor
I presume that it uses java.util.concurrent.ThreadPoolExecutor under the hood?
> - ProcessTask (an implementation of Progress by copying the Java class
> FutureTask - this is just for show we will need to implement this
> ourself prior to public release)
Just for my information: is there any chance to avoid this copying and instead
just wrap the standard FutureTask and delegate most methods to the wrapped
instance?
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
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
