> The only class that I didn't port was the PopStatsActor... I couldn't figure > out its states. > > Based on the pattern of having actors that had subactors that were used for > timer events, I'm guessing that's where the thread/memory explosion came > from, > > In general, it's best to use ActorPing.schedule to schedule a message to be > sent at some point in the future.
Whoops, my bad. When I first learned about actors I only looked in the scala-lang API and didn't think to look in the Lift classes. I should know better now. Added to my todo list.
