diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-06-24 19:41:09 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-06-24 19:41:09 +0000 |
| commit | ea18a50b5e38afdc01748473036988be5289718a (patch) | |
| tree | a5d25e0fcc9054dbf0b816c3a7c2b13e594794c6 /docs/narr/urlmapping.rst | |
| parent | 05c02322f5a09c14f49c529d6fd885153e52c66f (diff) | |
| download | pyramid-ea18a50b5e38afdc01748473036988be5289718a.tar.gz pyramid-ea18a50b5e38afdc01748473036988be5289718a.tar.bz2 pyramid-ea18a50b5e38afdc01748473036988be5289718a.zip | |
- ``repoze.bfg`` no longer relies on the Routes package to interpret
URL paths.
Diffstat (limited to 'docs/narr/urlmapping.rst')
| -rw-r--r-- | docs/narr/urlmapping.rst | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/docs/narr/urlmapping.rst b/docs/narr/urlmapping.rst index 21f6235f8..269061e40 100644 --- a/docs/narr/urlmapping.rst +++ b/docs/narr/urlmapping.rst @@ -13,11 +13,12 @@ components. Examples: `Django's URL dispatcher <http://www.djangoproject.com/documentation/url_dispatch/>`_ and the :term:`Routes` URL mapping system. -:mod:`repoze.bfg` supports :term:`URL dispatch` via :term:`Routes`. -:term:`URL dispatch` is convenient and straightforward. When you -limit your application to using URL dispatch, you know every URL that -your application might generate or respond to, and all the URL -matching elements are listed in a single place. +:mod:`repoze.bfg` supports :term:`URL dispatch` via a subsystem that +was inpsired by :term:`Routes`. :term:`URL dispatch` is convenient +and straightforward. When you limit your application to using URL +dispatch, you know every URL that your application might generate or +respond to, and all the URL matching elements are listed in a single +place. Like :term:`Zope`, :mod:`repoze.bfg`, in contrast to URL dispatch, can also map URLs to code slightly differently, by using using object @@ -35,8 +36,8 @@ Differences Between Traversal and URL Dispatch item "below" ``members`` in the URL represents a member in the system. You just match everything "below" ``members`` to a particular view. -For example, you might configure a :term:`Routes` URL map to match -against the following URL patterns:: +For example, you might configure a :term:`route` to match against the +following URL patterns:: archives/:year/:month/:day members/:membername |