On Tue, Mar 24, 2009 at 5:38 PM, Alex <a...@liivid.com> wrote: > With Lift > > 1) Form submits: B2345235DSFGA = "Long agonizing post" > 2) Function mapping has been cleared. Application panics and has no > idea what that junk was. >
1. This is an empirically wrong statement. Test it out. 2. A fair number of Lift apps are in the wild and the kind of problem that you're imaging is very rare. 3. When this kind of problem does happen (the front page of the travel site which is a stateless page rather than something that is part of a user's session), there are simple ways to deal with the situation, but these are exceptions rather than the rule. 4. There is nothing in Lift that stops you from putting stable form field names on a page and extracting them with S.param(field_name) 5. This is Lift's design... to make the common things easier and to allow the developer to fall back to guts of HTTP when necessary. 6. This list is for helping newbies become seasoned and for learning from people's real-world use to Lift in order to enhance Lift. 7. I'd suggest not pushing on this issue any more until you've built an app and seen how Lift works in practice. 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 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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
