Folks, I migrated ESME to use Lift Actors. I ran a smoke test and the code seems fine.
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. Thanks, David -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics
