you mean like those that seaside using? it lives as long as session lives, and tied to session you are working in..��

in early versions of seaside they were using exceptions to access session storage..��

quite ineffective.. but it works.

for that purpose it is much better to use process-specific variables, that live and die together with process that hosts them..

but has significantly better access timings. and since seaside allocates a separate process per session, that's perfect fit.

in any case, the concern about getting rid of volatile data is covered..��

while with memoization, i don't see it. and that seems like a HUGE argument against using it,

because it is more trouble in a long run than time saver when you just start using it everywhere.

��