#13894: Disable upstream caching with messages framework
---------------------------------------------+------------------------------
Reporter: bronger | Owner: nobody
Status: new | Milestone:
Component: Contrib apps | Version: 1.2
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by SmileyChris):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* component: Uncategorized => Contrib apps
* needs_tests: => 0
* needs_docs: => 0
Comment:
It does sound like a valid issue.
But isn't the opposite true as well? If a page (without any messages
displayed) is cached, then assuming messages were in the queue and this
page was hit again, the messages will not get rendered (or consumed). It
seems like fixing this only fixes half of the caching problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/13894#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
