summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2010-08-07 02:06:22 +0000
committerChris McDonough <chrism@agendaless.com>2010-08-07 02:06:22 +0000
commit8aa82def247688bcbc5140974d3696d77f81bbbb (patch)
tree82cab0f58eabfc80468bbc62e56e38a87a38ae1d /docs/designdefense.rst
parent7be3b177ed08596fed85022fd6d494d34509cf54 (diff)
downloadpyramid-8aa82def247688bcbc5140974d3696d77f81bbbb.tar.gz
pyramid-8aa82def247688bcbc5140974d3696d77f81bbbb.tar.bz2
pyramid-8aa82def247688bcbc5140974d3696d77f81bbbb.zip
wording
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index bacbdaea6..6d9659c1c 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -1550,14 +1550,15 @@ defined in our module. As a result, the view associated with the
``/admin`` routing pattern will be invoked: it matches first. All is
right with the world.
-In the first case, where we did not achieve the expected result, we
+In the second case, where we did not achieve the expected result, we
first added a route with the pattern ``/:action``, then we added a
route with the pattern ``/admin``. When a request with a
``PATH_INFO`` of ``/admin`` enters our application, the web framework
loops over each of our application's route patterns in the order in
which they were defined in our module. As a result, the view
associated with the ``/:action`` routing pattern will be invoked: it
-matches first. A 404 error is raised.
+matches first. A 404 error is raised. This is not what we wanted; it
+just happened due to the order in which we defined our view functions.
You may be willing to maintain an ordering of your view functions
which reifies your routing policy. Your application may be small