Hi. In production environment IMHO it really doesn't matter because you have to restart server anytime you change the python code. If you treat templates as code that really doesn't matter. We have about 50 production servers and we restart a farm every time we change the code. We do it progressively so users don't feel the difference. We do it 2-3 times a day. So I think this is not a huge issue when you have to restart server every time you change templates.
On Dec 23, 4:55 pm, Eratothene <[EMAIL PROTECTED]> wrote: > Hi forgems! > > Your snippet requires to restart django each time the templates have > changed. Did you try to add checking of template file modification > date in order automatically invalidate cache? What it is performance > of such implementation? Adding this kind of mechanism will increase > performace without any loss of functionality. Such implemention will > definitely be included into django base. Please, try it out. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
