<p><span class="h-card" translate="no"><a href="https://cloudisland.nz/@coderanger" class="u-url mention">@<span>coderanger</span></a></span> as I understand, the primary role of uwsgi is to implement and manage a dynamic pool of worker, which you need if you use blocking sockets. If you're talking about iouring, you're in the land of one worker servicing many connections asynchronously, you simply don't need a separate pool manager. You can just expose your framework's asgi endpoint. (I'm talking theoretically, I haven't run async Django myself.)</p>
