ActorPool vs. Dispatchers
If you set a dispatcher on an ActorPool, it'd be nice if that was inherited automatically by all actors within the pool without us having to put it in the instance method.
Leave a comment
on 2011-07-22 12:34 *
By viktorklang
You can probably solve that with a trait and an abstract override, it's hard to keep track of whether you have manually changed the dispatcher in "instance" or not.
on 2011-07-22 13:01 *
By bruce.mitchener
We did solve it on our own ... but I submitted this because I think it is an area where Akka could do better.
If you use spawn { ... } it uses the same dispatcher. But ActorPools do not...
If you use spawn { ... } it uses the same dispatcher. But ActorPools do not...
on 2011-10-04 15:24 *
By viktorklang
ActorPool.instance should have a parameter, def instance(defaults: Props): ActorRef, and then the pool can set itself as supervisor by default, and it can set it's own dispatcher as the default dispatcher etc.
on 2011-10-05 01:46 *
By viktorklang
Assigned to set to viktorklang
Status changed from New to Fixed
Updating tickets (#967, #974, #975, #976, #980, #981, #989, #990, #992, #993, #994, #999, #1000, #1004, #1008, #1011, #1015, #1018, #1022, #1023, #1024, #1025, #1027, #1028, #1029, #1030, #1032, #1033, #1036, #1047, #1053, #1062, #1067, #1068, #1069, #1072, #1075, #1078, #1082, #1102, #1107, #1110, #1111, #1115, #1116, #1121, #1122, #1123, #1124)