From da6ed19bc80cae601b3d8cbafb4cff425e04a3a1 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Wed, 30 Sep 2009 05:49:12 +0000 Subject: - Add a diagram which explains the operation of the BFG router to the "Router" narrative chapter. --- docs/narr/router.png | Bin 0 -> 168209 bytes docs/narr/router.rst | 10 ++++++---- 2 files changed, 6 insertions(+), 4 deletions(-) create mode 100644 docs/narr/router.png (limited to 'docs/narr') diff --git a/docs/narr/router.png b/docs/narr/router.png new file mode 100644 index 000000000..fc4407e81 Binary files /dev/null and b/docs/narr/router.png differ diff --git a/docs/narr/router.rst b/docs/narr/router.rst index a86e5267c..55df2936c 100644 --- a/docs/narr/router.rst +++ b/docs/narr/router.rst @@ -3,6 +3,8 @@ How :mod:`repoze.bfg` Processes A Request ========================================= +.. image:: router.png + Once a :mod:`repoze.bfg` application is up and running, it is ready to accept requests and return responses. @@ -65,11 +67,11 @@ processing? a :term:`view name` as well as other ancillary information. #. The request is decorated with various names returned from the - traverser (such as ``context``, ``view_name``, ``matchdict``, and - so forth), so they can be accessed via e.g. ``request.context`` - within :term:`view` code. + traverser (such as ``context``, ``view_name``, and so forth), so + they can be accessed via e.g. ``request.context`` within + :term:`view` code. -#. If an :term:`authentication policy` is in use, :mod:`repoze.bfg` +#. If an :term:`authorization policy` is in use, :mod:`repoze.bfg` passes the context, the request, and the view_name to a function which determines whether the view being asked for can be executed by the requesting user, based on credential information in the -- cgit v1.2.3