mention “import context.dispatcher” in the docs, see #2638
This commit is contained in:
parent
84bb53fbf6
commit
543087df9d
2 changed files with 27 additions and 0 deletions
|
|
@ -394,4 +394,18 @@ class FutureDocSpec extends AkkaSpec {
|
|||
intercept[IllegalStateException] { Await.result(result, 2 second) }
|
||||
}
|
||||
|
||||
"demonstrate context.dispatcher" in {
|
||||
//#context-dispatcher
|
||||
class A extends Actor {
|
||||
import context.dispatcher
|
||||
val f = Future("hello")
|
||||
def receive = {
|
||||
//#receive-omitted
|
||||
case _ ⇒
|
||||
//#receive-omitted
|
||||
}
|
||||
}
|
||||
//#context-dispatcher
|
||||
}
|
||||
|
||||
}
|
||||
|
|
|
|||
|
|
@ -22,6 +22,19 @@ by the ``ExecutionContext`` companion object to wrap ``Executors`` and ``Executo
|
|||
.. includecode:: code/docs/future/FutureDocSpec.scala
|
||||
:include: diy-execution-context
|
||||
|
||||
Within Actors
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
Each actor is configured to be run on a :class:`MessageDispatcher`, and that
|
||||
dispatcher doubles as an :class:`ExecutionContext`. If the nature of the Future
|
||||
calls invoked by the actor matches or is compatible with the activities of that
|
||||
actor (e.g. all CPU bound and no latency requirements), then it may be easiest
|
||||
to reuse the dispatcher for running the Futures by importing
|
||||
``context.dispatcher``.
|
||||
|
||||
.. includecode:: code/docs/future/FutureDocSpec.scala#context-dispatcher
|
||||
:exclude: receive-omitted
|
||||
|
||||
Use With Actors
|
||||
---------------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue