From 8bafcf33a10ea788f6affe311a87bdf37f343afb Mon Sep 17 00:00:00 2001 From: Elias Dorneles Date: Fri, 30 Sep 2016 11:20:30 -0300 Subject: [PATCH] improve description of engine --- docs/topics/architecture.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/topics/architecture.rst b/docs/topics/architecture.rst index 31b1c4ddd..91c80acc0 100644 --- a/docs/topics/architecture.rst +++ b/docs/topics/architecture.rst @@ -29,7 +29,7 @@ Data flow The data flow in Scrapy is controlled by the execution engine, and goes like this: -1. The :ref:`Engine ` gets the first Requests to crawl from the +1. The :ref:`Engine ` gets the initial Requests to crawl from the :ref:`Spider `. 2. The :ref:`Engine ` schedules the Requests in the @@ -62,8 +62,9 @@ this: :ref:`Spider Middleware ` (output direction). 8. The :ref:`Engine ` sends processed items to - :ref:`Item Pipelines ` and processed Requests to - the :ref:`Scheduler `. + :ref:`Item Pipelines `, then send processed Requests to + the :ref:`Scheduler ` and asks for possible next Requests + to crawl. 9. The process repeats (from step 1) until there are no more requests from the :ref:`Scheduler `.