Report issues
We're currently not allowing issue reporting directly via ITS. Please use the feedback form to submit your issues.
Move session management
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...
Mutex
Certain area's of JAS may need mutex to ensure correct functioning. Caching being one example (although overwrites don't matter too much) however there may be more areas where this applies...
Redis support
JAS should support Redis (http://redis.io/) next to (or maybe even instead of memcache) . What client should be used (see http://redis.io/clients#php)?
Config caching
Loading the initial configuration (when setting up the session) take too long. This should be cached (automagically detecting the cache method, i.e. mem, module, file) on a project by project basis and any subsequent config loads should use the cached version.
