#11331: Memcached backend closes connection after every request
--------------------------------------+------------------------------------
Reporter: booink@… | Owner: edmorley
Type: Cleanup/optimization | Status: assigned
Component: Core (Cache system) | Version: 1.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by edmorley):
* owner: nobody => edmorley
* cc: emorley@… (added)
* status: new => assigned
Comment:
I'm going to open a new PR for this - however one question:
We definitely need to `disconnect_all()` for python-memcached (since it's
why this behaviour was added in #5133), and definitely don't want it for
pylibmc (see pylibmc owner's comment here:
https://github.com/django/django/pull/4866#issue-88649865) -- but what
about third party backends? (eg python-binary-memcached and pymemcache)
ie: should I move the `disconnect_all()` from the base class to the
python-memcached backend (`MemcachedCache`), or make it a no-op only for
the `PyLibMCCache` backend?
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/11331#comment:13>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.8713da3b6f1c4d8945876730f0736b81%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
