From 3cf5e6149eea71549d794adcf0bf86e8916ab3cd Mon Sep 17 00:00:00 2001 From: Andrew Godwin Date: Wed, 23 Dec 2015 15:45:08 +0000 Subject: [PATCH] ASGI draft todo tweak --- docs/asgi.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/asgi.rst b/docs/asgi.rst index 870f0c4..85bb03b 100644 --- a/docs/asgi.rst +++ b/docs/asgi.rst @@ -82,7 +82,8 @@ specific in-process async solution, such as ``asyncio``, ``twisted``, or returns ``None`` or a ``(channel, message)`` tuple immediately. This approach should work with either synchronous or asynchronous code; part of the design of ASGI is to allow developers to still write synchronous code where possible, -as this makes for easier maintenance and less bugs, at the cost of performance. +as this generally makes for easier maintenance and less bugs, +but at the cost of performance. The distinction between protocol servers and applications in this document is mostly to distinguish their roles and to make illustrating concepts easier. @@ -752,6 +753,9 @@ TODOs * Be sure we want to leave HTTP ``get`` and ``post`` out. +* ``receive_many`` can't easily be implemented with async/cooperative code + behind it as it's nonblocking - possible alternative call type? Extension? + Copyright =========