- Removed the pickling of ZCML actions (the code that wrote

  ``configure.zcml.cache`` next to ``configure.zcml`` files in
  projects).  The code which managed writing and reading of the cache
  file was a source of subtle bugs when users switched between
  imperative (e.g. ``@bfg_view``) registrations and declarative
  registrations (e.g. the ``view`` directive in ZCML) on the same
  project. On a moderately-sized project (535 ZCML actions and 15 ZCML
  files), executing actions read from the pickle was saving us only
  about 200ms (2.5 sec vs 2.7 sec average). On very small projects (1
  ZCML file and 4 actions), startup time was comparable, and sometimes
  even slower when reading from the pickle, and both ways were so fast
  that it really just didn't matter anyway.

1 files changed, 9 insertions, 11 deletions

diff --git a/docs/narr/startup.rst b/docs/narr/startup.rst
index 58476da79..1d8206f14 100644
--- a/docs/narr/startup.rst
+++ b/docs/narr/startup.rst
@@ -127,17 +127,15 @@ press ``return`` after running ``paster serve MyProject.ini``.
    absolute, the ``package`` argument is ignored.
 
 #. The ``make_app`` function does its work.  It finds and parses the
-   ZCML represented by the application registry file (or may obtain
-   the application registry from a previously cached pickle file,
-   e.g. ``configure.zcml.cache``).  If it fails to parse one or more
-   ZCML files, a ``XMLConfigurationError`` is raised (or possibly
-   another error if the ZCML file just doesn't exist).  If it
-   succeeds, an :term:`application registry` is created, representing
-   the view registrations (and other registrations) for your
-   application.  A :term:`router` instance is created, and the router
-   is associated with the application registry.  The router represents
-   your application; the settings in the application registry that is
-   created will be used for your application.
+   ZCML represented by the application registry file.  If it fails to
+   parse one or more ZCML files, a ``XMLConfigurationError`` is raised
+   (or possibly another error if the ZCML file just doesn't exist).
+   If it succeeds, an :term:`application registry` is created,
+   representing the view registrations (and other registrations) for
+   your application.  A :term:`router` instance is created, and the
+   router is associated with the application registry.  The router
+   represents your application; the settings in the application
+   registry that is created will be used for your application.
 
 #. A ``WSGIApplicationCreatedEvent`` event is emitted (see
    :ref:`events_chapter` for more informations about events).