#969
  • Created on
    2011-06-27 09:55
  • Reported by
    pveentjer
  • Status
    Invalid
  • Priority
    High (2)
  • Assigned to
    viktorklang
  • Milestone
    2.0-M1
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

RemoteActorRef.start problem

The RemoteActorRef.start method always sets the __status field to started.. no matter if the Actor already has been shut down.

Also the __status field is a very dangerous field since it only reflect the state of the RemoteActorRef, but does not reflect the state of the LocalActorRef (so the real object).

Perhaps the simplest solution would be to throw an error and say this method is not supported? If you get a remote actor ref, by definition it will be started and there is no reason to call start on it yourself. This would be the easiest solution, but could break compatibility with existing code of users that do call start explicitly.

Another option would be to make this method a no-op.
User picture
  on 2011-06-30 23:51 *
By viktorklang
"start" will not be needed in 2.0 since all configuration will be supplied to actorOf, and therefor the actor will already be started when it returns.
User picture
  on 2011-07-09 18:24 *
By viktorklang
Assigned to set to viktorklang
Status changed from New to Invalid
"start" will most likely be removed in 2.0, since when you use an immutable configuration we can implicitly start the actor at creation.
User picture
  on 2011-12-15 01:54 *
By viktorklang
Milestone changed from 2.0 to 2.0-M1
Updating tickets (#684, #883, #886, #995, #1017, #968, #969, #973, #1002, #1016, #1021, #1035, #1048, #1119, #1156, #1451, #231, #470, #595, #599, #639, #655, #687, #691, #692, #693, #724, #728, #729, #749, #751, #755, #765, #766, #767, #769, #770, #771, #772, #784, #785, #807)