diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-07-05 22:25:26 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-07-05 22:25:26 +0000 |
| commit | 727d349420b2f303bd8bb09fbd506113c8ac0f5c (patch) | |
| tree | c72d17b06f0b2e8be2fa82ac33b9ee5218cf47e9 /docs/narr/hybrid.rst | |
| parent | 957a9366a72d4ee406e671e4e3652f85e9a5217c (diff) | |
| download | pyramid-727d349420b2f303bd8bb09fbd506113c8ac0f5c.tar.gz pyramid-727d349420b2f303bd8bb09fbd506113c8ac0f5c.tar.bz2 pyramid-727d349420b2f303bd8bb09fbd506113c8ac0f5c.zip | |
Spellcheck.
Diffstat (limited to 'docs/narr/hybrid.rst')
| -rw-r--r-- | docs/narr/hybrid.rst | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/narr/hybrid.rst b/docs/narr/hybrid.rst index 129d76732..48b2eedfc 100644 --- a/docs/narr/hybrid.rst +++ b/docs/narr/hybrid.rst @@ -43,7 +43,7 @@ URL Dispatch Only ~~~~~~~~~~~~~~~~~ An application that uses :term:`url dispatch` exclusively to map URLs -to code will usually exlusively have declarations like this within +to code will usually exclusively have declarations like this within their ``configure.zcml`` file: .. code-block:: xml @@ -93,10 +93,11 @@ code just won't have any ``<route>`` declarations. Instead, its ZCML /> "Under the hood", the above view statements register a view using the -:term:`context` interface ``None``, the IRequest :term:`request type` -with a :term:`view name` matching the name= argument. The "foobar" -view above will match the URL ``/a/b/c/foobar`` or ``/foobar``, etc, -assuming that no view is named "a", "b", or "c" during traversal. +:term:`context` interface ``None``, the ``IRequest`` :term:`request +type` with a :term:`view name` matching the name= argument. The +"foobar" view above will match the URL ``/a/b/c/foobar`` or +``/foobar``, etc, assuming that no view is named "a", "b", or "c" +during traversal. Hybrid Applications ------------------- @@ -198,7 +199,7 @@ view will be called. A ``<route>`` declaration *must* precede (in XML order) any ``<view>`` declaration which names it as a ``route_name``. If it does not, at -application startup time a ConfigurationError will be raised. +application startup time a ``ConfigurationError`` will be raised. Route Factories --------------- @@ -225,7 +226,7 @@ Using ``*subpath`` in a Route Path ---------------------------------- There are certain (extremely rare) cases when you'd like to influence -the traversal :term:`subpath` when a route matches without atually +the traversal :term:`subpath` when a route matches without actually performing traversal. For instance, the ``repoze.bfg.wsgi.wsgiapp2`` decorator and the ``repoze.bfg.view.static`` helper attempt to compute ``PATH_INFO`` from the request's subpath, so it's useful to be able to @@ -467,4 +468,4 @@ A ``<route>`` Statement *Must* Precede Any ``<view>`` Statement Which Mentions I A ``<route>`` declaration *must* precede (in XML order) any ``<view>`` declaration which names it as a ``route_name``. If it does not, at -application startup time a ConfigurationError will be raised. +application startup time a ``ConfigurationError`` will be raised. |