#4992: Alter cache key based on GET parameters
---------------------------------------------+------------------------------
Reporter: anonymous | Owner: nobody
Status: reopened | Milestone: post-1.0
Component: Cache system | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by PeterKz):
If I understand http://www.w3.org/DesignIssues/Axioms.html correctly you
should treat URL:s as opaque and get three different cache objects for:
* example.com/list/
* example.com/list/?a=1&b=2
* example.com/list/?b=2&a=1
It is likely that there won't be many permutations for multiple URL
parameters as they are typically constructed in a form controlled by the
application developer.
Implementing this would likely give a decent performance boost for Django
apps that filter large lists based on query parameters.
--
Ticket URL: <http://code.djangoproject.com/ticket/4992#comment:9>
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
-~----------~----~----~----~------~----~------~--~---
