tag:blogger.com,1999:blog-7045524330253482541.post2727171498330760359..comments2024-01-04T22:19:45.990-08:00Comments on Jim McBeath: Actor ExceptionsJim McBeathhttp://www.blogger.com/profile/10541190774989580614noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7045524330253482541.post-28366815884353313712010-06-14T13:14:16.736-07:002010-06-14T13:14:16.736-07:00This comment has been removed by a blog administrator.Unknownhttps://www.blogger.com/profile/04030001587200507713noreply@blogger.comtag:blogger.com,1999:blog-7045524330253482541.post-9576900404020793592008-10-10T08:15:00.000-07:002008-10-10T08:15:00.000-07:00Julian: Thanks for pointing out what the "link" me...Julian: Thanks for pointing out what the "link" methods do, since that functionality is very poorly documented. Using link does sound like a better approach for a more sophisticated system, since it would probably be simpler and you could have one actor that handles restarting a bunch of other actors.Jim McBeathhttps://www.blogger.com/profile/10541190774989580614noreply@blogger.comtag:blogger.com,1999:blog-7045524330253482541.post-55716238637359274002008-09-27T03:54:00.000-07:002008-09-27T03:54:00.000-07:00What you're looking for are the "link" methods. Li...What you're looking for are the "link" methods. Linked actors get each other's exceptions, and die as a unit. If a linked actor sets "trapExit = true" in its act() method, it doesn't die but rather receives a message with the Exit case class. So then it can restart the whole shebang. Erlang design uses this a lot, and Scala copies it.Jules Morrisonhttps://www.blogger.com/profile/01115506275519545033noreply@blogger.com