I would like a solution that works for cases where a app has subclassed
TurbineUser and added attributes. The simpler solution is less OO. The
user object represents the user in the session. When logging in the user
does not change so I think it is better if the user object does not change.
Of course if the user object before and after logging in are equivalent it
doesn't make much difference, but it seems easier to maintain the
equivalence by just keeping the same user object.
I think it should be as easy as possible to subclass TurbineUser. So it
would be best if one did not have to override the retrieveFromStorage method
to do so.
----- Original Message -----
From: jon * <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Wednesday, May 10, 2000 10:43 AM
Subject: Re: Anonymous User - UserFactory.getUser() - why?
> on 5/10/2000 8:50 AM, John McNally <[EMAIL PROTECTED]> wrote:
>
> > Another simpler solution would be
> > to just copy the temp hash from the anonymous user to the logged in
user,
> > but I do not favor this method.
>
> Why not? It seems to be a cleaner solution.
>
> I worked around this problem with Jyve by using a lot of hidden variables
in
> the login form (ie: major hack), but it really wasn't a good solution.
When
> I last investigated this issue, I came to the conclusion that just copying
> the temp hash over would be the best way to do things. KISS.
>
> -jon
>
> --
> Java Servlet Based - Open Source | Collab.Net
> Bug/Issue Tracking System | now hiring smart people
> <http://scarab.tigris.org/> | <http://Collab.Net/jobs/>
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
