#37177: Performance issue in Async Middleware handling.
--------------------------------+---------------------------------------
Reporter: Carlton Gibson | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: HTTP handling | Version: 6.0
Severity: Normal | Resolution:
Keywords: async | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+---------------------------------------
Comment (by Carlton Gibson):
@Jacob: great thanks! (I'm off on holiday so won't have time to process it
instantly)
My half-thought was, if introspection is too clever:
1. Manually mark (affected) built in middleware as `async_capable = False`
2. Deprecate `MiddlewareMixin.__acall__` implementation.
And that might be sufficient?
Tests: Locally I patched sync_to_async and async_to_sync calls to count
invocations, but that would need to be run alone. 🤔
--
Ticket URL: <https://code.djangoproject.com/ticket/37177#comment:7>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019edb05d363-06005a9c-2059-499c-a8e3-b73d10c52733-000000%40eu-central-1.amazonses.com.
