[issue30847] asyncio: selector_events: add_urgent() for urgent data to read, 3rd argument of select.select()

[STINNER Victor]

STINNER Victor added the comment:

In the selectors issue, we discussed how an application should prioritize "urgent" events:
http://bugs.python.org/issue30844#msg297707

While I now agree that it's not the role of selectors to decide, I would like to discuss the plan for asyncio.

Let's say that we got read event on sockets A and B (in an ordered list from selectors: A, then B), but B gets urgent data: should we handle B urgent data before not-urgent A data?

Would it be possible to let the developer decide how to prioritize events?

How does Twisted or Node.JS handle urgent data?

----------
nosy: +gvanrossum

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30847>
_______________________________________