I found RequestVar surprising/confusing at first, too, because I assumed its scope would be a single request -- but clearly isn't.
My suggestion here would be to rename RequestVar to PageVar since that's closer to its lifecycle and rename TransientRequestVar to RequestVar based on my initial expectation. I think this would make it more intuitive for newbies learning lift. alex On Tue, Dec 29, 2009 at 2:49 AM, Adam Warski <a...@warski.org> wrote: > Hello, > > > These are the names we use in Lift - appreciate what your saying, but its > not confusing IMHO, just different to other things you are used to. Lift is > Lift, not RoR, or Seam, or any other framework ;-) > > Sure, it's just a simple terminology switch, I don't really mind if they > are named one way or the other. The only objection I would have is that I > would make TransientRequestVar public, and, as Naftoli wrote, > statefullness/dispatching a trait. > > -- > Adam > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@googlegroups.com. > To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com<liftweb%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
