From eddf5254fbafc03abf0a11ee818f4c070f0a8146 Mon Sep 17 00:00:00 2001 From: Daniel Hengeveld Date: Thu, 20 Oct 2011 23:55:03 -0700 Subject: [PATCH] Clarify documentation around async.map and Request.send --- docs/user/advanced.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/user/advanced.rst b/docs/user/advanced.rst index 9f0a6838..cc6dcb27 100644 --- a/docs/user/advanced.rst +++ b/docs/user/advanced.rst @@ -69,9 +69,10 @@ We can build a list of ``Request`` objects easily:: rs = [async.get(u) for u in urls] -Now we have a list of ``Request`` objects, ready to be sent. We could -send them one at a time with ``Request.send()``, but that would take a while. -Instead, we'll send them all at the same time with ``async.map()``:: +Now we have a list of ``Request`` objects, ready to be sent. We could send them +one at a time with ``Request.send()``, but that would take a while. Instead, +we'll send them all at the same time with ``async.map()``. Using ``async.map()`` +will also guarantee execution of the ``response`` hook, described below. :: >>> async.map(rs) [, , , ]