trait ExplicitAskSupport extends AnyRef
This object contains implementation details of the “ask” pattern, which can be combined with "replyTo" pattern.
- Source
- AskSupport.scala
- Alphabetic
- By Inheritance
- ExplicitAskSupport
- AnyRef
- Any
- by any2stringadd
- by StringFormat
- by Ensuring
- by ArrowAssoc
- Hide All
- Show All
- Public
- Protected
Value Members
- def ask(actorSelection: ActorSelection, messageFactory: (ActorRef) => Any, sender: ActorRef)(implicit timeout: Timeout): Future[Any]
- def ask(actorSelection: ActorSelection, messageFactory: (ActorRef) => Any)(implicit timeout: Timeout): Future[Any]
Sends a message asynchronously and returns a scala.concurrent.Future holding the eventual reply message; this means that the target actor needs to send the result to the
sender
reference provided.Sends a message asynchronously and returns a scala.concurrent.Future holding the eventual reply message; this means that the target actor needs to send the result to the
sender
reference provided.The Future will be completed with an akka.pattern.AskTimeoutException after the given timeout has expired; this is independent from any timeout applied while awaiting a result for this future (i.e. in
Await.result(..., timeout)
). A typical reason forAskTimeoutException
is that the recipient actor didn't send a reply.Warning: When using future callbacks, inside actors you need to carefully avoid closing over the containing actor’s object, i.e. do not call methods or access mutable state on the enclosing actor from within the callback. This would break the actor encapsulation and may introduce synchronization bugs and race conditions because the callback will be scheduled concurrently to the enclosing actor. Unfortunately there is not yet a way to detect these illegal accesses at compile time.
Recommended usage:
val f = ask(worker, replyTo => Request(replyTo))(timeout) f.map { response => EnrichedMessage(response) } pipeTo nextActor
- implicit def ask(actorSelection: ActorSelection): ExplicitlyAskableActorSelection
Import this implicit conversion to gain
?
andask
methods on akka.actor.ActorSelection, which will defer to theask(actorSelection, message)(timeout)
method defined here.Import this implicit conversion to gain
?
andask
methods on akka.actor.ActorSelection, which will defer to theask(actorSelection, message)(timeout)
method defined here.import akka.pattern.ask // same as `ask(selection, askSender => Request(askSender))` val future = selection ? { askSender => Request(askSender) } // same as `ask(selection, Request(_))` val future = selection ? (Request(_)) // same as `ask(selection, Request(_))(timeout)` val future = selection ? (Request(_))(timeout)
All of the above use a required implicit akka.util.Timeout and optional implicit sender akka.actor.ActorRef.
- def ask(actorRef: ActorRef, messageFactory: (ActorRef) => Any, sender: ActorRef)(implicit timeout: Timeout): Future[Any]
- def ask(actorRef: ActorRef, messageFactory: (ActorRef) => Any)(implicit timeout: Timeout): Future[Any]
Sends a message asynchronously and returns a scala.concurrent.Future holding the eventual reply message; this means that the target actor needs to send the result to the
sender
reference provided.Sends a message asynchronously and returns a scala.concurrent.Future holding the eventual reply message; this means that the target actor needs to send the result to the
sender
reference provided.The Future will be completed with an akka.pattern.AskTimeoutException after the given timeout has expired; this is independent from any timeout applied while awaiting a result for this future (i.e. in
Await.result(..., timeout)
). A typical reason forAskTimeoutException
is that the recipient actor didn't send a reply.Warning: When using future callbacks, inside actors you need to carefully avoid closing over the containing actor’s object, i.e. do not call methods or access mutable state on the enclosing actor from within the callback. This would break the actor encapsulation and may introduce synchronization bugs and race conditions because the callback will be scheduled concurrently to the enclosing actor. Unfortunately there is not yet a way to detect these illegal accesses at compile time.
Recommended usage:
val f = ask(worker, replyTo => Request(replyTo))(timeout) f.map { response => EnrichedMessage(response) } pipeTo nextActor
- implicit def ask(actorRef: ActorRef): ExplicitlyAskableActorRef
Import this implicit conversion to gain
?
andask
methods on akka.actor.ActorRef, which will defer to theask(actorRef, askSender => message)(timeout)
method defined here.Import this implicit conversion to gain
?
andask
methods on akka.actor.ActorRef, which will defer to theask(actorRef, askSender => message)(timeout)
method defined here.import akka.pattern.ask // same as `ask(actor, askSender => Request(askSender))` val future = actor ? { askSender => Request(askSender) } // same as `ask(actor, Request(_))` val future = actor ? (Request(_)) // same as `ask(actor, Request(_))(timeout)` val future = actor ? (Request(_))(timeout)
All of the above use a required implicit akka.util.Timeout and optional implicit sender akka.actor.ActorRef.