diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-11-02 12:23:26 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-11-02 12:23:26 +0000 |
| commit | 49304cecdf2c51888ee4ff42ec6496207186ad9b (patch) | |
| tree | 82172ae270dfd0d5d972f65d4669c93219c9f469 /CHANGES.txt | |
| parent | 32d95886503540052d9b7075c9ce3326b042bb08 (diff) | |
| download | pyramid-49304cecdf2c51888ee4ff42ec6496207186ad9b.tar.gz pyramid-49304cecdf2c51888ee4ff42ec6496207186ad9b.tar.bz2 pyramid-49304cecdf2c51888ee4ff42ec6496207186ad9b.zip | |
- Add a new event type: ``repoze.bfg.events.AfterTraversal``. Events
of this type will be sent after traversal is completed, but before
any view code is invoked. Like ``repoze.bfg.events.NewRequest``,
This event will have a single attribute: ``request`` representing
the current request. Unlike the request attribute of
``repoze.bfg.events.NewRequest`` however, during an AfterTraversal
event, the request object will possess attributes set by the
traverser, most notably ``context``, which will be the context used
when a view is found and invoked. The interface
``repoze.bfg.events.IAfterTraversal`` can be used to subscribe to
the event. For example::
<subscriber for="repoze.bfg.interfaces.IAfterTraversal"
handler="my.app.handle_after_traverse"/>
Like any framework event, a subscriber function should expect one
parameter: ``event``.
Diffstat (limited to 'CHANGES.txt')
| -rw-r--r-- | CHANGES.txt | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index edd3170ff..b1d84c4d1 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -12,6 +12,27 @@ Documentation - "What's New in ``repoze.bfg`` 1.1" document added to narrative documentation. +Features +-------- + +- Add a new event type: ``repoze.bfg.events.AfterTraversal``. Events + of this type will be sent after traversal is completed, but before + any view code is invoked. Like ``repoze.bfg.events.NewRequest``, + This event will have a single attribute: ``request`` representing + the current request. Unlike the request attribute of + ``repoze.bfg.events.NewRequest`` however, during an AfterTraversal + event, the request object will possess attributes set by the + traverser, most notably ``context``, which will be the context used + when a view is found and invoked. The interface + ``repoze.bfg.events.IAfterTraversal`` can be used to subscribe to + the event. For example:: + + <subscriber for="repoze.bfg.interfaces.IAfterTraversal" + handler="my.app.handle_after_traverse"/> + + Like any framework event, a subscriber function should expect one + parameter: ``event``. + Dependencies ------------ |