cubicweb #2164478 Flexible sessions handling [open]
we should be able to store sessions and associated data in memory, files, database, memcached... To do so, we probably have to lower/clarify the distinction of web/repository sessions first. And then a cube for persistent sessions ? See also beaker wsgi middleware. | |
| priority | normal |
|---|---|
| type | task |
| done in | <not specified> |
| load | 2.000 |
| load left | 2.000 |
| closed by | <not specified> |
similar entities
- cubicweb #1381328 [sessions] have persistent web sessions
- Beaker (http://beaker.groovie.org/)
- cubicweb #1056022 enhance support for distributed config
- cubicweb #1937850 _cwsgid pollutes session data
- cubicweb #4143913 make session handling compatible with the requirements of an integration under pyramid
[see all]