➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients gvanrossum, pklanke, vstinner, yselivanov
Date 2017-07-05.09:24:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499246678.9.0.534554154646.issue30847@psf.upfronthosting.co.za>
In-reply-to
Content 
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?
History
Date User Action Args
2017-07-05 09:24:38vstinnersetrecipients: + vstinner, gvanrossum, yselivanov, pklanke
2017-07-05 09:24:38vstinnersetmessageid: <1499246678.9.0.534554154646.issue30847@psf.upfronthosting.co.za>
2017-07-05 09:24:38vstinnerlinkissue30847 messages
2017-07-05 09:24:38vstinnercreate