https://github.com/bbangert/beaker

WSGI middleware for sessions and caching
https://github.com/bbangert/beaker

Last synced: about 9 hours ago
JSON representation

WSGI middleware for sessions and caching

• Host: GitHub
• URL: https://github.com/bbangert/beaker
• Owner: bbangert
• License: other
• Created: 2011-10-16T17:48:39.000Z (about 13 years ago)
• Default Branch: master
• Last Pushed: 2024-06-21T19:39:55.000Z (5 months ago)
• Last Synced: 2024-10-31T15:47:51.817Z (8 days ago)
• Language: Python
• Homepage: https://beaker.readthedocs.org/
• Size: 1.1 MB
• Stars: 524
• Watchers: 24
• Forks: 143
• Open Issues: 81
• Metadata Files:
  • Readme: README.rst
  • Changelog: CHANGELOG
  • License: LICENSE

Awesome Lists containing this project

• best-of-python - GitHub - 55% open · ⏱️ 11.04.2024): (Data Caching)
• awesome-python-resources - GitHub - 53% open · ⏱️ 07.12.2021): (缓存)

README

        
=========================

Cache and Session Library

=========================

About

=====

Beaker is a web session and general caching library that includes WSGI

middleware for use in web applications.

As a general caching library, Beaker can handle storing for various times

any Python object that can be pickled with optional back-ends on a

fine-grained basis.

Beaker was built largely on the code from MyghtyUtils, then refactored and

extended with database support.

Beaker includes Cache and Session WSGI middleware to ease integration with

WSGI capable frameworks, and is automatically used by `Pylons

`_ and 

`TurboGears `_.

Features

========

* Fast, robust performance

* Multiple reader/single writer lock system to avoid duplicate simultaneous

  cache creation

* Cache back-ends include dbm, file, memory, memcached, Redis, MongoDB, and

  database (Using SQLAlchemy for multiple-db vendor support)

* Signed cookies to prevent session hijacking/spoofing

* Cookie-only sessions to remove the need for a db or file backend (ideal

  for clustered systems)

* Extensible Container object to support new back-ends

* Caches can be divided into namespaces (to represent templates, objects,

  etc.) then keyed for different copies

* Create functions for automatic call-backs to create new cache copies after

  expiration

* Fine-grained toggling of back-ends, keys, and expiration per Cache object

Documentation

=============

Documentation can be found on the `Official Beaker Docs site

`_.

Source

======

The latest developer version is available in a `GitHub repository

`_.

Contributing

============

Bugs can be filed on GitHub, **should be accompanied by a test case** to

retain current code coverage, and should be in a pull request when ready to be

accepted into the beaker code-base.