Changes between Version 1 and Version 2 of PylibmcSupport

Timestamp:

Nov 29, 2010, 8:33:37 PM (15 years ago)

Author:

otherjacob

Comment:

--

PylibmcSupport

@@ -19 +19 @@
 
 Another post of note with regards to multithreading [ala, celery] here: http://www.dctrwatson.com/2010/09/python-thread-safe-does-not-mean-fork-safe/#more-48
+
+=== November 2010 ===
+
+11/29: Draft one suggested to the django-dev lift
+Draft #1: https://gist.github.com/91de59e53f7f36f461ec
+
+Caveats/Notes on the draft: 
+A) This is only the memcache.py file, changes to conf/global_settings and core/cache/base will be needed to handle the move towards CACHE_SETTINGS 
+
+B) pylibmc and memcached handle negative timeouts differently. The expected behavior as laid out in template tests is how python-memcached handles it (instant expiration). I had to do a fairly sad looking hack to make pylibmc work, and is noted in a comment.
+
+C) The current version of pylibmc doesn't play nice with python sub-interuptors, and thus, mod_wsgi. There is a commit (https://github.com/lericson/pylibmc/commit/ddd2f011f73d8ccc6347c5471eff378bef58dbd5) in trunk that fixes this, but a release has not been given out. We may want to be extra-communicative of this and the possible workarounds.