Turbine holds a session even if no user has logged in (in this case an
anonymous user is assumed). Then you may use setTemp() and getTemp() in
User interface, which allows to store any object in it on a session
basis in a hashtable bound to the 'user'.
Therefore you don't need to worry about cookies or any low-level
mechanism for session maintenance. You just use it ;-)
Regards,
Bartek Walter
Alexander Banthien wrote:
>Hi folks,
>
>if anybody has gained experience in this please give me a hint.
>
>My site is supposed to have on option for the users to change the
>fontsize/stylesheet, for the display of their pages. (Bad idea say the
>layouters ;-)
>
>I chose to store the fontsize information in a cookie, which persists a
>single user session.
>
>I wrote two Actions: IncreaseFontsize, DecreaseFontsize which, when
>called, do thier job correctly and set a new cookie value:
>//------- action -----------------------
>CookieParser cp = data.getCookies();
>cp.set("fontsize",newvalue);
>//--------------------------------------
>
>The problem is that the screen, which is executed right after one of
>those actions, does not know about the new value. Only upon the next
>run, does the new setting become active:
>
>//-------- screen ---------------------
>CookieParser cp = data.getCookies();
>cp.get("fontsize"); //turns out to be old.
>//--------------------------------------
>
>How must I instanciate the CookieParser in the screen in order to get
>the new value?
>
>Thanks for the attention
>
>Alexander
>
>
>--
>
>Mit freundlichen Gr��en
>Alexander Banthien
>
>_______________________________________
>Questech GmbH
>Schwarzwaldstr. 19
>79199 Kirchzarten
>
>Fon: +49 (0)7661 90 35-15
>Fax: +49 (0)7661 90 35-20
>www.questech.de
>
>_______________________________________
>
>
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
