Thanks for the data! Yeah, not a fan of needless uphill battles, seems I'll avoid GAE for now. Took a look at Stax. Seems it's still in beta, and uses Amazon Web Services; I'll probably just go with Amazon as well. Anyone have any experience with EC2 and Lift?
On Jul 12, 4:05 pm, "marius d." <[email protected]> wrote: > On Jul 12, 9:16 am, TakeTheStage <[email protected]> wrote: > > > Hello, new to both Scala and Lift. After weighing several options, > > I've decided to create a new app using Lift, with GAE for hosting. As > > such, I chose Lift due to its support for concurrency, inherited from > > its Scala base. > > Ok, so I'm preaching to the choir. > > Here is my question: with the limitations imposed by GAE (no new > > threads) does Lift lose its scalability and concurrency advantages, or > > has David's alternate actor library (for Lift) taken care of this > > issue? > > Not quite. LiftActors is still using Java threads via Java's executor > framework and in GAE you still can't use it AFAIK .Dave did not > replace ScalaActors with LiftActors except for a single place where > actors needed to be created and destroyed very often. And this happens > internally. CometActors are still Scala actors. If you can live > without Comet (and actors in general) and JDBC you can go ahead and > use GAE. Personally I would usehttp://stax.net/... no threading > restrictions and they provide MySql. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
