Hi folks, I am new to Django, and trying to figure out if Django could be used for a new project which is similar to a news site (stories & syndication feeds), as well as more permanent content.
The twist is that we already have thousands of such stories stored as Markdown or RST files on the filesystem, and maintained with a version control system. We would like to keep it that way: stories are written on the filesystem, committed to the VCS, and published by Django. This is hardly rocket science, and there are probably apps or snippets that already do this. I have not looked too closely yet, because I was concentrating on the issue of caching so far. Rather than processing markup on the fly for each request, one would like to cache the result. I found that the Textpattern CMS seems to use a database for that: http://code.djangoproject.com/wiki/UsingMarkup this gave me the following idea: For a given request, if it maps into the filesystem storage space, obtain the mtime of the file and compare it to a timestamp stored in a database table. If the mtime is newer, process the file and store the result in the database. Then return the contents of the database. Compared to Django caching, this is purely on-demand, there is no maximum age, but instead you get mtime queries into the filesystem for every request (those could be cached…). Does anyone know of an app or plugin which already does this? Can anyone imagine a way to re-use the existing cache framework as much as possible for this? Any other thoughts or concerns? Thanks, -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; n...@madduck "i must get out of these wet clothes and into a dry martini." -- alexander woolcott spamtraps: madduck.bo...@madduck.net
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
