Keep it simple. Use nginx or apache and in your Django app you simply write to the filesystem. "Invalidation" can be done by simply deleting the file which is easy. Something like nginx for serving static file is faster than anything else. I'm sure you already know how to deploy static files such as css files.
On Jan 22, 7:17 am, Hinnack <henrik.gens...@googlemail.com> wrote: > Hi, > > I am using memcached for caching my sites. The documentation says when > not to use it:http://code.google.com/p/memcached/wiki/WhyNotMemcached > > one point is output larger 1 MB > > I have a site producing pdf files only, where size can easily go over > 1 MB. As the docs above mention mogilefs as > an alternative, I wonder if this is the right way to do it, as there > is no batterie for djangos caching system. > > I know that the cach system has support for filesystem cache - has > someone used this for large files? and maybe even > in conjunction with GlusterFS (http://www.gluster.org/), as that seems > to be more complete then mogilefs? > > What about concurrent writes from different hosts to the cache system? > > -- > > Hinnack -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
