#7398: Making it easier to add custom cache backends
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone:
Component: Cache system | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-----------------------------------+----------------------------------------
Changes (by mtredinnick):
* needs_better_patch: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
I think a whole extra setting and a dictionary like this is too much for
this feature. Let's handle it like database backends: if the cache name
(the bit before the colon, ":") is not one of the standard names, it's
treated as an import path. Everything after the colon is passed through as
an argument, just like now.
So extra caches can be added anywhere on the Python path and we don't need
an extra setting. Being able to redefine the existing names to mean
something else isn't needed here. If you want to have "some other
memcached", just import it under a different name using the extension
mechanism in the above paragraph. The point is that every time we add an
extra setting, it's one more bit of documentation, one more thing for
people to wonder if they need, etc. Let's go for simplicity first.
--
Ticket URL: <http://code.djangoproject.com/ticket/7398#comment:6>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
