[concurrency-interest] Receiving notifications from Futures

Brian S O'Neill bronee at gmail.com
Mon May 18 11:23:13 EDT 2009

Some of these solutions require the addition of many more classes and 
interfaces, which I think greatly complicates things. I agree with 
Mark's suggestion: pass a collection/queue to the API that created the 
Future. Manik suggestion can also be simplified by accepting an ordinary 
queue as input instead of a special listener. This is the approach I 
took, and it keeps things simple.


peter royal wrote:
> On May 18, 2009, at 8:38 AM, Manik Surtani wrote:
>> I'm guessing I cannot be the first person with the need for a 
>> notifying future - how has this been achieved before?
> Sam Berlin put forth an implementation last November on the list and 
> there was some discussion around it then:
> http://cs.oswego.edu/pipermail/concurrency-interest/2008-November/005588.html 
> -pete
> ------------------------------------------------------------------------
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest

More information about the Concurrency-interest mailing list