Moving CompletionHandler to java.util.concurrent

[Gili]

You know what Alan? The more I take a look at
http://guava-libraries.googlecode.com/svn/trunk/javadoc/com/google/common/util/concurrent/ListenableFuture.html
the more it doesn't make sense to introduce CompletionHandler in Java7.
Instead of introducing duplicate methods (one that uses Futures, another
that uses CompletionHandler) we should just have a single method that
handles both use-cases using a ListenableFuture.

Have you guys reviewed this possibility already...?

Thanks,
Gili


Alan Bateman wrote:
> 
> Gili wrote:
>> 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?
>>
>> Gili
>>   
> Have you brought this up on concurrency-interest? I'm pretty sure this 
> type of thing has come up many times (in the context of Executors at
> least).
> 
> -Alan.
> 
> 

-- 
View this message in context: http://n2.nabble.com/Moving-CompletionHandler-to-java-util-concurrent-tp3845440p3866513.html
Sent from the nio-discuss mailing list archive at Nabble.com.