[concurrency-interest] is choice between asynchrone/synchrone method an implementation detail?

Brian Goetz brian at quiotix.com
Tue Jul 25 12:52:49 EDT 2006


> Don't get me wrong. Asynchronous calls are great. But it should be part
> of the interface definition: you say that the cook method blocks
> untill the water boils (synchronous) or you say: press the cook
> button, but don't wait (the asynchronous call).

And blocking methods (those that wait for an action to occur in another 
thread) should strongly consider throwing InterruptedException, both to 
facilitate cancellation, and as a nice way of saying "I'm a blocking 
method."


More information about the Concurrency-interest mailing list