mention the event loop

mojolicious · Sep 15, 2014 · 65f83b5 · 65f83b5
1 parent cf9c539
commit 65f83b5
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 4 deletions.
diff --git a/Changes b/Changes
@@ -1,5 +1,5 @@
 
-5.42  2014-09-14
+5.42  2014-09-15
 
 5.41  2014-09-13
   - Deprecated Mojolicious::Controller::render_static in favor of

diff --git a/lib/Mojolicious/Guides/Growing.pod b/lib/Mojolicious/Guides/Growing.pod
@@ -210,15 +210,16 @@ It all starts with an HTTP request like this, sent by your browser.
   GET / HTTP/1.1
   Host: localhost:3000
 
-Once the request has been received by the web server, it will be passed on to
-L<Mojolicious>, where it will be processed in a few simple steps.
+Once the request has been received by the web server through the event loop,
+it will be passed on to L<Mojolicious>, where it will be handled in a few
+simple steps.
 
   1. Check if a static file exists that would meet the requirements.
   2. Try to find a route that would meet the requirements.
   3. Dispatch the request to this route, usually reaching one or more actions.
   4. Process the request, maybe generating a response with the renderer.
   5. Return control to the web server, and if no response has been generated
-     yet, wait for a non-blocking operation to do so.
+     yet, wait for a non-blocking operation to do so through the event loop.
 
 With our application the router would have found an action in step 2, and
 rendered some text in step 4, resulting in an HTTP response like this being