There is nothing that needs to be done here. It's only if you *mutate* values stored in the session that you need to do explicit persistence triggering. I provided an example of doing this in my last email. - C On Dec 15, 2005, at 4:20 PM, Dennis Allison wrote:
Chris McDonnough pointed out a problem with my setSessionVariable code which I am now fixing. I want a generic routine to set a session variable whether it is a simple variable, a list, or a dictionary.
The question is one of triggering the persistence mechanism. If a dictionary or list is stored in a session variable, what is needed to ensure that the setSessionVariable() routine triggers the persistence mechanism?
Is it adequate to simply read the session variable in the setSessionVariable() routine prior to writing it when the session variable is a dictionary or list? Or is something else needed?