Home/ Questions/Q 6569759
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T14:40:19+00:00

The Akka 1.1.3 documentation states that [t]he become method is useful for many different

  • 0

The Akka 1.1.3 documentation states that “[t]he become method is useful for many different things, but a particular nice example of it is in example where it is used to implement a Finite State Machine (FSM).” What are some other use cases for hotswapping an Akka actor’s implementation at runtime?

The actorClass method in the ActorRef trait is deprecated with the message, “Will be removed without replacement, doesn’t make any sense to have in the face of become and unbecome.” Can someone please explain this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For Question 1: Encoding variable behavior:

    http://klangism.tumblr.com/post/968180337/dining-hakkers

    For Question 2:

    Knowing the backing classname of an actor is pointless, since it will not tell you anything about the behavior. It also will not work reliably with remoting since the service can be re-bound, and there’s no exchange of such information. Essentially actorClassName violates tell-don’t-ask

    • 0