#36863: Under WSGI, multiple calls to asgiref.sync.async_to_sync within the same
request do not share the same event loop.
-------------------------------------+-------------------------------------
Reporter: Mykhailo Havelia | Owner: Vishy
Type: | Algo
Cleanup/optimization | Status: new
Component: HTTP handling | Version: 6.0
Severity: Normal | Resolution:
Keywords: async, wsgi | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
At a glance that cleanup strategy seems more attractive in order to
unclutter the `WSGIHandler`, but we can defer that to PR review.
I think I understand the ask here; I'm just wondering why it was never
designed this way. Our [https://docs.djangoproject.com/en/6.0/topics/async
/#async-views docs] read:
> Under a WSGI server, async views will run in their own, one-off event
loop.
> This means you can use async features, like concurrent async HTTP
requests,
> without any issues, but you will not get the benefits of an async stack.
So, am I to understand that there are, in fact, "issues" here, issues that
are not resolvable by, "just use an ASGI stack"?
--
Ticket URL: <https://code.djangoproject.com/ticket/36863#comment:12>
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/0107019c0fa1e1c3-40bbbc05-cf38-4c20-b0e1-e1ad306ecf8e-000000%40eu-central-1.amazonses.com.
