re: Linking ActorsWhen two actors are linked, it makes it so that they notify each other on exit. So if you have actors A and B, they are linked, and B exists, then as part of the shutdown process A will notified. The default behavior is for A to exit when it receives this notification, however if you set the trapExit variable on the actor to true the notification will be done via an Exit message instead ( http://www.scala-lang.org/docu/files/api/scala/actors/Exit.html )
On Mon, Jul 6, 2009 at 3:44 PM, Andy the destroyer < [email protected]> wrote: > Hi Vassil, > > What sort of JMX operations do you have in mind? Reset? Query stats? > > I went through the code base this weekend and so far I think I have a > pretty > good idea of how things are working. I am a little confused with one thing > however. > > What exactly does the scala.actors.Actor.link method do? What does it mean > to "link" an actor to another? No books ( Programming in Scala, Beginning > Scala, Definitive Guide to LIFT), scaladocs or blogs I have found give an > explanation, but I see it peppered through the ESME and LIFT codebase. > > Also, the touch method on the Distributor, MessagePullActor and > ScedulerActor is used to load the class like an empty init method, am I > correct in this? After the touch method is called in Boot.scala the class > is > initialized which ends with a StartMeUp message sent to the loading Actor ( > loading users in the case of the Distributor ). Correct? > > I just want to make sure I understand things correctly before I go coding > wildly and blindly. > > I should be able to start throwing some code together in the next few days. > > Thanks, > Andy > > > > On Fri, Jul 3, 2009 at 2:22 AM, Vassil Dichev <[email protected]> wrote: > > > Hey Andy, > > > > Welcome aboard, I hope you have lots of fun with ESME- and Scala! > > > > Regarding JMX, one of the ideas of ESME is that text messages could be > > used as a control interface to different types of services. It would > > be great if we eat our own dog food and have a bot that executes > > JMX-related commands when sent to it in the form of a message. > > > > A fun part of ESME where it makes a difference from other messaging > > platforms is actions. You can take some time to research about actions > > from the wiki (http://cwiki.apache.org/confluence/display/ESME/Actions). > > There are a number of small things to do to get one started with > > actions, e.g. issue ESME-29 (Add new tags to Actions). Another related > > feature would be to create a message when someone has been added to an > > access pool (a functionality we are now implementing). > > > > Let us know what you're interested in and don't hesitate to ask if you > > have questions. > > > > Happy hacking, > > Vassil > > > -- http://erikengbrecht.blogspot.com/
