[Lift] Re: Mega*ProtoUser extensibility - a suggestion.

2009-08-05 Thread David Pollak
There was a time when: class Foo { def bar = "Hello" } object Moose { object foo1 extends Foo { def baz = "Howdy" } val foo2 = new Foo { def baz = "From another foo" } } println(Moose.foo1.baz) println(Moose.foo2.baz) Would not compile because the type of foo2 was Foo, not so

[Lift] Re: Mega*ProtoUser extensibility - a suggestion.

2009-08-05 Thread E. Biggs
David, First apologies for accidently taking this thread off the lift group. It was entirely accidental. So my question with regards to the scala language that I can't seem to find an answer for online anywhere is what exactly is an object nested inside a class i.e. : class ObjectWrapper { ob

[Lift] Re: Mega*ProtoUser extensibility - a suggestion.

2009-08-04 Thread E. Biggs
Actually, you're right.. I suppose I got too focused on how I wanted to do it and didn't think of how it could be done more pleasingly this seems to work great: override def currentUserId: Box[String] = { super.currentUserId match { case Full(_) => super.currentUserId cas

[Lift] Re: Mega*ProtoUser extensibility - a suggestion.

2009-08-04 Thread Naftoli Gugenheim
Why not use logUserIdIn, logUserIn, logoutCurrentUser/logUserOut(), and currentUserId, and currentUser? - E. Biggs wrote: I have extended Mega*ProtoUser to achieve cookie-based perpetual login.. and it was fairly easy to do except I ended up having to do so

[Lift] Re: Mega*ProtoUser extensibility - a suggestion.

2009-08-04 Thread David Pollak
In this case, if you change the type/behavior of the SessionVar and/or RequestVar, you could mess up code that depends on these. You also must *always* make RequestVar and SessionVar as object rather than val so that they can make the determination of their unique string ID. I view ProtoUser much