This is a theoretical question and I suspect the hair may not be worth it, but has anyone given thought to persistent sessions? The idea is that you have a public page which is a separate tree from the live site (I do this) and when someone logs in, instead of creating a new tree you restore an existing tree and redirect to the last known URL for that session. You can record this URL and the session state on timeout or on log out.
When a session has timed out, you can at least return the user to the page they were at along with the application state and a message saying 'you timed out, please log back in' and then put them back where they were. All you need to store on timeout is the last known URL (for fresh logins) and the widget tree along with any app-specific session state. How hard would it be to serialize widgets? (I wonder if my Elephant contrib, the snapshot set, would just do the right thing...) Any hitches I'm missing? Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
