Wiktor Grębla napisał(a):
> I was wondering, is there any way to set a cookie valid for the
> current session only, without setting global
> SESSION_EXPIRE_AT_BROWSER_CLOSE?
I should RTFM more (BTW, thanks for the great documentation):
#v+
from django.contrib.sessions.models import Session
Wiktor Grębla napisał(a):
> I was thinking about it for a while, and I found another simple
> problem. Setting the cache the way I do is also error-prone. I use the
> same cache keys for different connections, so every time a user
> connects and the cache is saved (wherever I think it's sane
Eugene Lazutkin napisał(a):
> 'locmem:///' is a thread-safe process-local memory cache. Every process
> has its own unique instance. Why? It was meant to be used for caching of
> immutable, but expensive-to-calculate values. In your case (making a
> global snapshot of a variable) it'll create
Wiktor Grębla wrote:
>
> I've a "testing" Django configuration with lighttpd (flup +
> django-fastcgi.py) on FreeBSD. Everything seems to work fine, but there
> is one thing "misbehaving": cacheing when CACHE_BACKEND = 'locmem:///'.
...
> If I set CACHE_BACKEND = 'db://some_table' it's working
Hi.
I've a "testing" Django configuration with lighttpd (flup +
django-fastcgi.py) on FreeBSD. Everything seems to work fine, but there
is one thing "misbehaving": cacheing when CACHE_BACKEND = 'locmem:///'.
In my views I often use something like:
images = cache.get('images')
entries =
5 matches
Mail list logo
