#21012: Provide shared "caches" dict to avoid creating multiple cache class
instances.
--------------------------------------+------------------------------------
Reporter: FunkyBob | Owner: FunkyBob
Type: Cleanup/optimization | Status: assigned
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by apollo13):
* needs_better_patch: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
I don't think this is the right way to go. First we need to figure out how
cache classes are supposed to behave, eg does it even make sense to have
one global instance of them or should be put them into threadlocals etc…
Eg, what happens if two requests at the same time request a value, will
python-memcached acquire the GIL during it's operation or can actually
both requests send a request over the wire etc…
--
Ticket URL: <https://code.djangoproject.com/ticket/21012#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.31a0c187305e8f2845a9392abf559e34%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
