In my opinion, yes. Others will disagree.
In my experience, storing things in the session causes really strange
behavior in tabbed browsers - because all tabs share a single session.
Also, the data vanishes when the session expires - which causes a
bizarre user experience ("Where did my shopping cart go??").
-Adrian
Quoting Christian Carlow <[email protected]>:
Thanks Adrian,
So is it best not to use <session-to-field> and <field-to-session>?
On 01/10/2014 01:15 PM, [email protected] wrote:
From my perspective, modifying the session object in Mini-language
is a bad idea. There are plenty of examples of request events and
services modifying the session object, but doing so always results
in quirky behavior.
If you need to persist a value, then it would be best to store the
value in the database.
-Adrian
Quoting Christian Carlow <[email protected]>:
Anyone know how to access the session in simple methods so that
setAttribute and getAttribute can be performed?
