Hervé Guidetti wrote:
>
> In fact, I can have an application where I don't have to login (a site with
> public part and a secure part)
> An example. I connect to the site. I set the language (which is associated
> with the session because there is no user). Then the "surfer" want to login
> to access the secure part of the site. If the session variable are reset, he
> has to redefine the language and all the variable associated with the
> session.
OK now I understand. Overriding this behaviour would indeed reqire moving some
code from Turbine.java to actions/LoginUser.java.
But I'm wondering about another thing - your registered user has to set the
language prefernce once only, because you can store it in user's Perm data.
Does an unregistered user have to chose the language every time he visits
the site? Maybe you should use a cookie, that would be evaluated by, say
SessionValidator and converted into a setting in the session? And there would
be a SetLanugage action, that would set the cookie, and store the setting in
user's Perms if a registered user is logged in. This would solve your problem
with language being reset, and would also keep the setting permanent across
mulitple sessions for unregistered users also, without overringing the behaiour
of Turbine.
What do you think about this?
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
