Sounds like you need a session keyed stack. Have a look at the various Apache:: modules to store session based info, and you'll need some kind of shared caching structure (eg IPC::SharedCache). You might want to have a look at mod_perl too: the various Auth modules work really well for "click-path" security, ie remembering where you wanted to go before the login screen popped up.rdfield | [reply] |
Thank you for your advice. I looked at IPC::SharedCache, but why would I need something like that? It sounds like what this module is doing is just speeding up template loading, which would be nice and I had been definitely thinking about implementing some kinda caching in my application, but it doesn't really solve my original problem.
| [reply] |
If you're using Apache, you'll need a mechanism for sharing the session stacks across all of the child processes (unless you're using Apache 1.3 on W2K).rdfield
| [reply] |