I don't have the time to actually try this now, but one way to achieve this comes to mind:
The ActorCell underneath should have access to the message currently in work. AFAIK, you can cast the context to ActorCell and just read the current message out of it. For good reason, however, the ActorCell is an akka-private. - So, you'd have to put the described functionality in the akka packge. I am not sure about the full implications when working with ActorCell, though. ... not a very neat solution, I know. hth -Tom On Wednesday, March 18, 2015 at 11:55:08 PM UTC+1, Eric Pederson wrote: > > Actually, though, methods in an actor really shouldn't be called > asynchronously. That would circumvent the actor model. That's why things > like pipeTo exist, to minimize the chance that a future could interact with > the guts of an actor. An actor's methods should really only be called from > a thread started from receive, with few exceptions. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
