Changes between Version 6 and Version 7 of DjangoSpecifications/Contrib/Sessions


Ignore:
Timestamp:
Apr 4, 2008, 7:22:36 AM (17 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DjangoSpecifications/Contrib/Sessions

    v6 v7  
    1818`django.contrib.session` should be a secure session framework that
    1919 * will not be re-used under any circumstances (#6941), is protected against key collisions (#1180) and session hijacking (#6941),
    20  * supports concurrency by using locking throughout (as Beaker does, think mod_wsgi with threads and AJAX),
     20 * supports concurrency by using locking throughout (as Beaker does, think mod_wsgi with threads and AJAX), see also [DjangoSpecifications/Core/Threading Threading improvements],
    2121 * supports destroying sessions (no dangling data nor session ID should remain),
    2222 * supports controlling session lifetime (comment:ticket:2548:9 describes the use case),
Back to Top