Something wrong with simple cache
I am not talking about multithreading problems. "locmem:" doesn't have them. But it does have problems with gzip. Sometimes I see binary stuff on my screen. It looks like a gzipped web page without proper gzip encoding flag. I don't do anything related to compression in my cache.
Is it a bug in Django's caching? Hmm... Apparently it works properly with memcache. Can it be some bug in "simple:" implementation, which was a base for "locmem:"? Weird.
Update: Yes, something is wrong. I found one small bug and one weirdness. The bug is easy to fix. But I don't know what to do about the weird part. Apparently if you store HttpResponse object, it behaves like it is modified by some means. But if you pickle it, everything goes smoothly. I'll try to dig up more on that.
Of course, local debugging doesn't help. Does it indicate some other Dreamhost-specific problem?
Save/recommend this post:
Subscribe to this blog:
Most recent related documents:
Documents published at about the same time:
- DreamHost: no transactions — September 12, 2005
- Running on 'sql:' cache now — September 11, 2005
- Running on 'file:' cache now — September 11, 2005
- TinyMCE 2.0RC1 is out — September 10, 2005
- Say no more! Say no more! — September 8, 2005
- Django on Dreamhost: happy end — September 7, 2005
- Django with MySQL: problem solved? — September 5, 2005
