I was wondering whether there would be interest to extend web2py
caching with shove ( http://pypi.python.org/pypi/shove ). Shove
probably wouldn't be directly exposed to the user, but wrapped in the
current cache module (just like mem, disk or memcache is now). By
using shove for caching, we could choose from the following storage/
cache options (and gain cache compression as a side effect):
For those that are unfamiliar with shove: Common object storage
frontend that supports dictionary-style access, object serialization
and compression, and multiple storage and caching backends.
Currently supported storage backends are:
* Amazon S3 Web Service
* Berkeley Source Database
* Filesystem
* Firebird
* FTP
* DBM
* Durus
* Memory
* Microsoft SQL Server
* MySQL
* Oracle
* PostgreSQL
* SQLite
* Subversion
* Zope Object Database (ZODB)
Currently supported caching backends are:
* Filesystem
* Firebird
* memcached
* Memory
* Microsoft SQL Server
* MySQL
* Oracle
* PostgreSQL
* SQLite
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
