Create /service path for pre-deployed or JIT-deployed service actors from config
(No description)
Leave a comment
on 2011-12-20 11:03 *
By Patrik Nordwall
Should probably be an Extension
on 2011-12-20 16:05 *
By Patrik Nordwall
The reason why it should be an Extension is that we should not specify actor type (creator) in config, because then we have soon our own Spring DI framework.
on 2012-01-17 11:03 *
By Patrik Nordwall
Assigned to set to Patrik Nordwall
Status changed from New to Accepted
It is better implemented using the existing extension mechanism.
App that need these kind of /service actors can write a simple extension that starts the actors. Configure the extension in config so it's run on boot.
For the lazy create scenario the extension will still start the actor, but it is implemented as lazy in itself, i.e. initialize whatever is costly on first message.
Instantiating actors at system start-up is trivial even without an extension: system.actorOf exists today.
App that need these kind of /service actors can write a simple extension that starts the actors. Configure the extension in config so it's run on boot.
For the lazy create scenario the extension will still start the actor, but it is implemented as lazy in itself, i.e. initialize whatever is costly on first message.
Instantiating actors at system start-up is trivial even without an extension: system.actorOf exists today.