Use cases for active Akka actors

Question

The Akka 1.1.3 documentation says that "the [t] he become method is useful for many different things, but a specific, nice example of this example is presented in the example when it is used to implement a state machine (FMS)." What are some other use cases for hot-plugging an Akka Akk implementation at runtime?

The actorClass method in the ActorRef deprecated with the message: "It will be deleted without replacement, it makes no sense to have become and unbecome in front of it." Can someone explain this?

Answer 1

In question 1: behavior of a variable encoding:

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

In question 2:

Knowing the base name of an actor class is meaningless, as it will not say anything about behavior. It will also not work reliably with deletion, since the service can be tied up and there will be no exchange of such information. Essentially actorClassName violates tell-don't-ask

Answer 2

You can perform a software update without interrupting the service. You can load new behavior dynamically and then drag it from the old one.