It used to be that when a User went from anonymous to logged in status,
the User object did not change. The User object only changed when a
user logged out. I think this is the proper behavior, but Rafal had
security concerns; I do not recall what they were. Copying the temp
hashtable does not help in the case where a custom User is being used
that is storing some attributes outside the hashtable. But you can just
say you have to write your own Login action to account for any
differences. I still like just keeping the same User.
john mcnally
Sean Legassick wrote:
>
> In message <[EMAIL PROTECTED]>, Jason Crickmer
> <[EMAIL PROTECTED]> writes
> >I have created a new PullTool called EventTool. I have configured it
> >for session scope. It works great if you are logged in to the site or
> >not. But, once a user does logs in, the user gets a new EventTool
> >instance and the old one appears to be discarded.
> >
> >Why is that? Am I using the wrong scope?
>
> No. This is a limitation of session scope for pull tools as currently
> implemented. Session scope is implemented via the User temp hashtable,
> and the anonymous User object is thrown away when a user logs in.
>
> You can write your own LoginUser action that copies across everything
> from the anonymous User temp hashtable into the new authenticated User
> temp hashtable.
>
> It's arguable that this should be the default - what do others think?
>
> --
> Sean Legassick
> [EMAIL PROTECTED]
> Ek is 'n man: niks menslik is vreemd vir my nie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
