diff options
| -rw-r--r-- | docs/narr/urlmapping.rst | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/docs/narr/urlmapping.rst b/docs/narr/urlmapping.rst index 87f8c9862..2eeaa0646 100644 --- a/docs/narr/urlmapping.rst +++ b/docs/narr/urlmapping.rst @@ -63,13 +63,12 @@ URL-dispatch based systems, and some assertions just aren't possible. For example, URL-dispatch based systems don't deal very well with URLs that represent arbitrary-depth hierarchies. -Graph :term:`traversal` works well if you need to divine meaning from -of these types of "ambiguous" URLs and from URLs that represent -arbitrary-depth hierarchies. When traversal is used, each URL segment -represents a single traversal step through an edge of a graph. So a -URL like ``http://example.com/a/b/c`` can be thought of as a graph -traversal on the ``example.com`` site through the edges ``a``, ``b``, -and ``c``. +Graph :term:`traversal` works well for these types of "ambiguous" URLs +and for URLs that represent arbitrary-depth hierarchies. When +traversal is used, each URL segment represents a single traversal step +through an edge of a graph. So a URL like +``http://example.com/a/b/c`` can be thought of as a graph traversal on +the ``example.com`` site through the edges ``a``, ``b``, and ``c``. If you're willing to treat your application models as a graph that can be traversed, it also becomes easy to provide "row-level security" (in |