Permalink
Browse files

reviewed

  • Loading branch information...
1 parent 7cf0676 commit f9896b60700ea4334f3df0a83f9b291e167b322d @mcdonc mcdonc committed Jul 12, 2011
Showing with 2 additions and 5 deletions.
  1. +0 −3 TODO.txt
  2. +2 −2 docs/narr/hooks.rst
View
@@ -10,9 +10,6 @@ Must-Have
(DBSession.rollback()/transaction.abort() in scaffold vs. "pass" in
tutorial)
-- deprecate request.add_response_callback (or at least review docs, in light
- of request.response property).
-
Should-Have
-----------
View
@@ -284,8 +284,8 @@ Using Response Callbacks
Unlike many other web frameworks, :app:`Pyramid` does not eagerly create a
global response object. Adding a :term:`response callback` allows an
-application to register an action to be performed against a response object
-once it is created, usually in order to mutate it.
+application to register an action to be performed against whatever response
+object is returned by a view, usually in order to mutate the response.
The :meth:`pyramid.request.Request.add_response_callback` method is used to
register a response callback.

0 comments on commit f9896b6

Please sign in to comment.