I still feel like it's somewhat ambiguous in a remoting context, because there
is not a one-to-one relationship, but the only remaining issue I really have is
that there seems to be no way of preventing a fair amount of scary logs on the
server when the client process exits:
[INFO] [01/10/2014
Hi Erik,
Akka's semantics of stop I'd say is quite well documented, both in the
reference documentation:
http://doc.akka.io/docs/akka/2.2.3/scala/actors.html#Stopping_actors
And in code:
" ActorRef does not have a method for terminating the actor it points to,
use akka.actor.ActorRefFactory.sto
On Sun, Jan 12, 2014 at 9:08 AM, Erik Nelson wrote:
> Thank you!
>
> I will say that, even though I understand why this is the case, it's a
> bit strange in practice. Given the fact that multiple clients can connect
> to the same server, the ability to terminate that way is, well... perhaps a
>
Thank you!
I will say that, even though I understand why this is the case, it's a bit
strange in practice. Given the fact that multiple clients can connect to the
same server, the ability to terminate that way is, well... perhaps a bit
strange.
I suspect it will not be an issue now that I have
Hi Erik,
There is no way to shutdown/close a remote connection.
When you say that you shutdown the ActorRef, I guess that you are using
system.stop(ref), which stops the actor. Thereafter you can't identify the
actor again, because the actor is terminated.
At some point we might implement automat
Hi gang,
I've been playing with our remoting connection management library, and ran into
a bit of a problem. I want to be able to disconnect and reconnect to a given
server, but if I shutdown a local ActorRef that is associated with a remote
actor, the remote becomes unable to accept new connec
