Hi, I'm looking to learn Lift coming from working with Ruby on Rails for a while and I've been voraciously consuming the documentation and tutorials that are available on the internet. There are a few things I really like about Lift so far:
- Out of the box Comet support - Rapid development (incremental compiles are awesome) - Being able to design without having to think of the request/response cycle* I'm putting an asterisk on the last item because I'm a bit confused how this will work in a production application running two or more load balanced Lift instances of the same application. The fact that form processing can happen without inspecting GET/POST params or dealing with data that needs to life longer than a standard request cycle is pretty neat, but it raises questions about horizontal scalability. Where is the session data stored? If it is in-memory by default, are there any best practices for sharing session data across application servers, or is the recommended solution to use load balancer affinity? Ikai --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
