Currently session management is handled in the default PHP fashion and thus resides on the webserver. To make it more flexible we'll need to support the following alternatives:Database (aka module based)
Memcache / Redis
File based
Since sessions (both _session and _config) are quite fundamental to the functioning of JAS it seems wise to have as little dependencies on JAS to avoid circular dependencies. That said, replicating the Cache class seems futile as well...
Configuration...
Report issues
We're currently not allowing issue reporting directly via ITS. Please use the feedback form to submit your issues.