Hi - It's my understanding that using persistent page properties involves letting Tapestry shuffle objects back and forth from the users HttpSession. In our admin apps we have large object graphs that we need to store between requests and are thinking that we'd like to allow Tapestry to do the management of this (i.e. less code for us to write) but we also want to remove the objects from the HttpSession when the user moves on to another page.
Are there any hooks in the framework to allow for this? One thought is to call a base class "clean up" method that removes all the persistent properties from the HttpSession. Ideally there would be some sort of EventListener we could tap into or some Engine method that is called when the user is going to a new Page object so that we could trigger this clean up. I just haven't been able to determine which method would be best to override in this instance since it's not just the end of the response, it's triggered when the IRequestCycle activates a different IPage then the one the user is currently on. Thanks for any advice MIke --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
