Zope2 session implementation using Beaker
Project description
Introduction
Products.BeakerSessionDataManager is a replacement for the default Zope 2 session implementation. It uses Beaker as a backend (via collective.beaker) and adapts the Beaker session to provide the same interface as a normal Zope session.
Beaker is a better alternative to the default session implementation for several reasons:
The Zope session implementation does not perform well in high-write scenarios.
Beaker provides better flexibility in where session data is actually stored.
Beaker is used and maintained outside of the Zope ecosystem.
Installation
Add the Products.BeakerSessionDataManager egg to your buildout:
[instance] eggs = Products.BeakerSessionDataManagerMake sure that buildout adds Beaker configuration to zope.conf. For example:
zope-conf-additional = <product-config beaker> session.type file session.data_dir ${buildout:directory}/var/sessions/data session.lock_dir ${buildout:directory}/var/sessions/lock session.key beaker.session session.secret secret </product-config>The “secret” should be replaced with a unique string for your system. It must be the same for all Zope instances using the same session store.
See the collective.beaker docs for more details on configuration.
In the ZMI, delete the session_data_manager object and add a Beaker Session Data Manager.
Notes
Beaker does not automatically clean up old sessions, so you may want to set up a cron job to take care of this.
Changelog
1.0b1 (2011-04-17)
Initial release
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Hashes for Products.BeakerSessionDataManager-1.0b1.zip
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 940f2387c08fdc419a84924536c317d5072367b2f1233fafdd84fe4f890089e9 |
|
| MD5 | b8ef1850ec43010b05321c2d8cab1bb3 |
|
| BLAKE2b-256 | e8e82dc75e98f492b9b8e1bfc548fa8a73077392ed11cf9e84ae4fa9709fdd39 |
