Permalink
Browse files

controlling flow with scala futures

  • Loading branch information...
1 parent cf788b2 commit 390f9c8932f23f16e64f8383bf5ecaf9dadec632 @Srirangan committed Jan 15, 2013
Showing with 5 additions and 3 deletions.
  1. +5 −3 public/posts/2013-01-controlling-flow-with-scala-futures.html
@@ -2,8 +2,8 @@
<div class="entry-content">
<blockquote>
- This post is a continuation of <a href="/2013-01-first-steps-with-scala-futures">First steps with `futures` in Scala</a> especially if
- you're unfamiliar with <code>Futures</code> introduced in Scala 2.10.
+ If you're unfamiliar with <code>Futures</code> in Scala 2.10, check out <a href="/2013-01-first-steps-with-scala-futures">First steps with `futures` in
+ Scala</a>.
<small>Sri</small>
</blockquote>
<p>Composing units of code that execute asynchronously | concurrently | in-parallel is now trivial and elegant.</p>
@@ -135,7 +135,9 @@
// Yes! :D | No :(
</pre>
<hr/>
- <p>Like all futures, <code>promise.future</code> can only be complete once. Thus multiple asynchronous block that <code>tryComplete</code> a promise.</p>
+ <p>Like all futures, <code>promise.future</code> can only be complete once. Thus you can have multiple asynchronous block that can each
+ <code>tryComplete</code> a promise.</p>
+ <p>The first one that calls <code>tryComplete</code> is taken forward and the rest aren't.</p>
<pre>
// Two asynchronous blocks `tryComplete` a promise

0 comments on commit 390f9c8

Please sign in to comment.