Georg,
Thank you for comprehensive answers. I think the part about interaction
between different types of middleware should go directly to Django's
documentation.
Thanks,
Eugene
"hugo" <[EMAIL PROTECTED]> wrote in
message news:[EMAIL PROTECTED]
>
> Hi,
>
>>1) If I want to use all 3 cache mi
On 10/9/05, Ian Holsman <[EMAIL PROTECTED]> wrote:
> one of the (minor) drawbacks I see with django is the copyright and
> restriction of use of the code templates which come with django.
I think you may be misunderstanding. The admin templates that come
with Django are BSD-licensed, just like th
does django is going to integrate ajax in a near future?
I think that mochikit is a good option
Hi.
one of the (minor) drawbacks I see with django is the copyright and
restriction of use of the code templates which come with django.
This makes it hard for people to bring up a quick prototype to the pointy-heads.
so in order to help out I'd like to contribute a BSD-licenced
template/design
Hi,
>1) If I want to use all 3 cache middlewares + session middleware, what is
>the correct order now? Is this stack correct:
They can have allmost any order you like, but you have to make sure
that the cache middleware is after all middlwares that might change
content depending on headers - for
