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.

prioritynormal
typetask
done in<not specified>
load2.000
load left2.000
closed by<not specified>