« Return to Thread: Moving CompletionHandler to java.util.concurrent

Re: Moving CompletionHandler to java.util.concurrent

by Sam Berlin :: Rate this Message:

There seem to be many inventions designed to workaround the fact that Futures don't have a listening mechanism. CompletionHandler is one mechanism to asynchronously listen to the completion of a Future. Google recently open-sourced their "guava" library which adds methods for listening to a Future. There was a long discussion a while ago about different folks implementing their own listeners to Future.

IMO, I'd rather really & truly add listeners to Future. But CompletionHandler is nice too.

Sam

On Mon, Oct 19, 2009 at 3:26 PM, cowwoc <cowwoc@...> wrote:

Hi,

Hi,

I would like to propose moving CompletionHandler to package
java.util.concurrent. Its use is not limited to I/O operations. For example,
I use it for monitoring asynchronous Swing operations. CompletionHandler can
be used virtually anywhere that java.util.concurrent.Future can, so why not
place them in the same package?

Orginal post:
http://n2.nabble.com/Moving-CompletionHandler-to-java-util-concurrent-tt3845440.html#a3848449

Thanks,
Gili
--
View this message in context: http://www.nabble.com/Moving-CompletionHandler-to-java.util.concurrent-tp25958440p25958440.html
Sent from the JSR166 Concurrency mailing list archive at Nabble.com.

_______________________________________________
Concurrency-interest mailing list
Concurrency-interest@...
http://cs.oswego.edu/mailman/listinfo/concurrency-interest

_______________________________________________
Concurrency-interest mailing list
Concurrency-interest@...
http://cs.oswego.edu/mailman/listinfo/concurrency-interest

« Return to Thread: Moving CompletionHandler to java.util.concurrent