summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-04-30 04:24:28 +0000
committerChris McDonough <chrism@agendaless.com>2009-04-30 04:24:28 +0000
commit27b87596a09ae4616b2445f85e6c4edea85114f9 (patch)
treec3f09ba37282f5a819d0ad90463dd4b459ccd088 /docs
parent812ca0af0161680ccaf7c67d2393107d62c775ef (diff)
downloadpyramid-27b87596a09ae4616b2445f85e6c4edea85114f9.tar.gz
pyramid-27b87596a09ae4616b2445f85e6c4edea85114f9.tar.bz2
pyramid-27b87596a09ae4616b2445f85e6c4edea85114f9.zip
Remove incorrect info from security chapter.
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/security.rst35
1 files changed, 2 insertions, 33 deletions
diff --git a/docs/narr/security.rst b/docs/narr/security.rst
index 590b90b2e..87907730e 100644
--- a/docs/narr/security.rst
+++ b/docs/narr/security.rst
@@ -150,18 +150,12 @@ Location-Awareness
In order to allow the security machinery to perform ACL inheritance,
model objects must provide *location-awareness*. Providing
location-awareness means two things: the root object in the graph must
-have a ``_name__`` and a ``__parent__`` attribute and the root object
-must be declared to implement the ``repoze.bfg.interfaces.ILocation``
-interface. For example:
+have a ``_name__`` attribute and a ``__parent__`` attribute.
.. code-block:: python
:linenos:
- from repoze.bfg.interfaces import ILocation
- from zope.interface import implements
-
class Blog(object):
- implements(ILocation)
__name__ = ''
__parent__ = None
@@ -170,33 +164,8 @@ is said to be *location-aware*. Location-aware objects define an
``__parent__`` attribute which points at their parent object. The
root object's ``__parent__`` is ``None``.
-If the root object in a :mod:`repoze.bfg` application declares that it
-implements the ``repoze.bfg.interfaces.ILocation`` interface, it is
-assumed that the objects in the rest of the model are location-aware.
-If those objects are not explictly location-aware, if the root object
-is marked as ``ILocation``, the bfg framework will wrap each object
-during traversal in a *location proxy* that has both the ``__name__``
-and ``__parent__`` attributes, but otherwise acts the same as your
-model object.
-
-.. note::
- In order to use this feature, you must register the
- ``WrappingModelGraphTraverser`` as the traversal policy, rather
- than the standard ``ModelGraphTraverser``. E.g., your application
- will need to have the following in its ``configure.zcml``::
-
- <adapter
- factory="repoze.bfg.traversal.WrappingModelGraphTraverser"
- provides="repoze.bfg.interfaces.ITraverserFactory"
- for="*"
- />
-
-You can of course supply ``__name__`` and ``__parent__`` attributes
-explicitly on all of your model objects, and no location proxying will
-be performed.
-
See :ref:`location_module` for documentations of functions which use
-location-awareness.
+location-awareness. See also :ref:`location_aware`.
.. _debug_authorization_section: