RomanNum3ral
/
scrapy
mirror of https://github.com/scrapy/scrapy.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2296 from scrapy/architecture-overview-once-more-with-feeling 

[MRG+1] architecture docs: restore explanation loop to step 1 (see comment in 3ac3ac4)
This commit is contained in:
Paul Tremberth 2016-09-30 16:30:37 +02:00 committed by GitHub
parent 86eb865598 8bafcf33a1
commit ab3f27b502
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/architecture.rst
View File

@ -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 <component-engine>` gets the first Requests to crawl from the
1. The :ref:`Engine <component-engine>` gets the initial Requests to crawl from the
:ref:`Spider <component-spiders>`.
2. The :ref:`Engine <component-engine>` schedules the Requests in the
@ -62,11 +62,11 @@ this:
:ref:`Spider Middleware <component-spider-middleware>` (output direction).
8. The :ref:`Engine <component-engine>` sends processed items to
:ref:`Item Pipelines <component-pipelines>`, then sends processed Requests to
the :ref:`Scheduler <component-scheduler>` and asks for the next
Requests to crawl.
:ref:`Item Pipelines <component-pipelines>`, then send processed Requests to
the :ref:`Scheduler <component-scheduler>` and asks for possible next Requests
to crawl.
9. The process repeats (from step 2) until there are no more requests from the
9. The process repeats (from step 1) until there are no more requests from the
:ref:`Scheduler <component-scheduler>`.
Components