Hi Stephane
One approach is to store this data transiently in an ASO. (This data
object needs to be serializable though, but using soft references works
great). In your getter method be sure to check if its null and if so
reinitialize it)... Inject the ASO in your pages and never worry about
data activation in pages. This is the real value of IoC. However, bear
in mind when using persisted data if it becomes large, it gets expensive
to carry around in a high volume application, so you loose scalability.
Stephane Decleire wrote:
Hi,
I would like to know how do you handle session timeout with T5 or if
there is a "design pattern" for this case.
When a session timeout occurs, a lot of pages won't work because of a
lack of data (for example, normaly setted before returning the page).
So i need to write a piece of code in the activation event of almost
of my pages. In T4, i would have writen it in a parent page and would
have subclassed all the pages from it. In T5 should i consider writing
a mixin or something else ?
Thanks in advance.
Stephane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
