esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Pollak <>
Subject ESME now runs on Lift Actors
Date Thu, 22 Oct 2009 20:55:34 GMT

I migrated ESME to use Lift Actors.  I ran a smoke test and the code seems

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

In general, it's best to use ActorPing.schedule to schedule a message to be
sent at some point in the future.



Lift, the simply functional web framework
Beginning Scala
Follow me:
Surf the harmonics

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message