David, What is the actual status of scala.actors.remote. I mean if you want to distribute your application, do you still need to use JMS or AMQP or something like that?
Thx, Ramzi On Wed, Jan 7, 2009 at 5:15 AM, David Pollak <[email protected]> wrote: > Bob, > memcached is failure. Using memcached means that the application stack has > somehow failed to deliver the appropriate caching and concurrency tools. > Scala and Scala Actors provide a powerful mechanism for building domain > appropriate caching. > > Please look at this presentation. > Thanks, > David > On Tue, Jan 6, 2009 at 7:27 PM, Bob Eastbrook <[email protected]> > wrote: >> >> >> I'm keeping my eye on Lift, but I'm primarily a PHP guy as far as >> paying the bills goes. I've got a slightly better high-level >> understanding of things now versus a month or so ago, but I'm not sure >> where caching fits into the picture. In the LAMP world, it's standard >> practice to put memcache in front of your database server. It's >> pretty much a "cache everything" philosophy. Is this not encouraged >> with Lift? I assume there are more caching choices in the Java world >> such as ehcache, but I don't see them mentioned on the list. >> >> Bob >> >> > > > > -- > Lift, the simply functional web framework http://liftweb.net > Collaborative Task Management http://much4.us > Follow me: http://twitter.com/dpp > Git some: http://github.com/dpp > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
