From b9595cd2578fa1cbc2b817c9cd9c4bc93c9508b8 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 16 Sep 2012 14:49:09 -0400 Subject: no longer an issue --- docs/designdefense.rst | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'docs') diff --git a/docs/designdefense.rst b/docs/designdefense.rst index d896022e6..b468ddac6 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -390,20 +390,6 @@ completely optional. No ZCML is required at all to use :app:`Pyramid`, nor any other sort of frameworky declarative frontend to application configuration. -.. _model_traversal_confusion: - -Pyramid Uses "Model" To Represent A Node In The Graph of Objects Traversed --------------------------------------------------------------------------- - -The ``repoze.bfg`` documentation used to refer to the graph being traversed -when :term:`traversal` is used as a "model graph". A terminology overlap -confused people who wrote applications that always use ORM packages such as -SQLAlchemy, which has a different notion of the definition of a "model". As -a result, in Pyramid 1.0a7, the tree of objects traversed is now renamed to -:term:`resource tree` and its components are now named :term:`resource` -objects. Associated APIs have been changed. This hopefully alleviates the -terminology confusion caused by overriding the term "model". - Pyramid Does Traversal, And I Don't Like Traversal -------------------------------------------------- -- cgit v1.2.3