From f9896b60700ea4334f3df0a83f9b291e167b322d Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Tue, 12 Jul 2011 03:31:08 -0400 Subject: reviewed --- TODO.txt | 3 --- docs/narr/hooks.rst | 4 ++-- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/TODO.txt b/TODO.txt index ee5275952..a28ab8800 100644 --- a/TODO.txt +++ b/TODO.txt @@ -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 ----------- diff --git a/docs/narr/hooks.rst b/docs/narr/hooks.rst index 94701c9f9..a156426ae 100644 --- a/docs/narr/hooks.rst +++ b/docs/narr/hooks.rst @@ -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. -- cgit v1.2.3