diff options
| author | Chris McDonough <chrism@agendaless.com> | 2008-11-15 23:52:14 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2008-11-15 23:52:14 +0000 |
| commit | 4542cd95c5a8bc962395c53aade9c1782f81731d (patch) | |
| tree | 40ba1fb7b937f7045607d242d4ea2fd855518b23 | |
| parent | 2dc0b5f7e57721b9a9d56b6dfdc07cbb3e929ac8 (diff) | |
| download | pyramid-4542cd95c5a8bc962395c53aade9c1782f81731d.tar.gz pyramid-4542cd95c5a8bc962395c53aade9c1782f81731d.tar.bz2 pyramid-4542cd95c5a8bc962395c53aade9c1782f81731d.zip | |
Don't mention XML-RPC.
| -rw-r--r-- | docs/narr/events.rst | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/narr/events.rst b/docs/narr/events.rst index 376d7b796..900f8499d 100644 --- a/docs/narr/events.rst +++ b/docs/narr/events.rst @@ -107,11 +107,10 @@ Using An Event to Vary the Request Type The most common usage of the ``INewRequestEvent`` is to attach an :term:`interface` to the request to be able to differentiate, for -example, a request issued by a browser from a request issued by an -XML-RPC from a request issued by a REST client. This differentiation -makes it possible to register different views against different -``request_type`` interfaces; for instance, depending on request -headers, you might return JSON or XML data. +example, a request issued by a browser from a request issued by a REST +client. This differentiation makes it possible to register different +views against different ``request_type`` interfaces; for instance, +depending on request headers, you might return JSON or XML data. To do this, you should subscribe an function to the ``INewRequest`` event type, and you should use the ``zope.interface.alsoProvides`` API |