<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>django on linux &amp; the mountains</title>
    <link>https://bzed.de/tags/django/</link>
    <description>Recent content in django on linux &amp; the mountains</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>Copyright 2009-2017 Bernd Zeimetz</copyright>
    <lastBuildDate>Wed, 10 Feb 2010 15:41:13 +0100</lastBuildDate><atom:link href="https://bzed.de/tags/django/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Caching issues in django</title>
      <link>https://bzed.de/post/2010/02/caching_issues_in_django/</link>
      <pubDate>Wed, 10 Feb 2010 15:41:13 +0100</pubDate>
      
      <guid>https://bzed.de/post/2010/02/caching_issues_in_django/</guid>
      <description>Yesterday I stumbled upon an interesting and broken behaviour of Django: Running two instances with the same memcached as cache backend might result in displaying the wrong template from the cache in case we have template files with the same name but a different content.
This behaviour is also visible in all django applications which use the cache backend without taking care of settings.CACHE_MIDDLEWARE_KEY_PREFIX. As mentioned in the bug report a design decision is necessary here, as the setting was only supposed to be used in middlewares.</description>
    </item>
    
  </channel>
</rss>
