summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMichael Merickel <michael@merickel.org>2013-08-12 16:28:57 -0500
committerMichael Merickel <michael@merickel.org>2013-08-12 16:28:57 -0500
commit8339cd1095be5e49fe41662e3618b8da6055a4f0 (patch)
tree6aaacaeb083c206a2726d406addadef1f6a4b257 /docs
parent084f12252356879b7d4cad085d64e1f0d3679cd1 (diff)
downloadpyramid-8339cd1095be5e49fe41662e3618b8da6055a4f0.tar.gz
pyramid-8339cd1095be5e49fe41662e3618b8da6055a4f0.tar.bz2
pyramid-8339cd1095be5e49fe41662e3618b8da6055a4f0.zip
remove the "thread" reference
Diffstat (limited to 'docs')
-rw-r--r--docs/api/registry.rst8
-rw-r--r--docs/narr/events.rst6
2 files changed, 8 insertions, 6 deletions
diff --git a/docs/api/registry.rst b/docs/api/registry.rst
index 42a405a32..7736cf075 100644
--- a/docs/api/registry.rst
+++ b/docs/api/registry.rst
@@ -32,10 +32,10 @@
.. method:: notify(*events)
Fire one or more events. All event subscribers to the event(s)
- will be notified. The subscribers will be called synchronously on
- the current thread. This method is often accessed as
- ``request.registry.notify`` in Pyramid applications to fire
- custom events. See :ref:`custom_events` for more information.
+ will be notified. The subscribers will be called synchronously.
+ This method is often accessed as ``request.registry.notify``
+ in Pyramid applications to fire custom events. See
+ :ref:`custom_events` for more information.
.. class:: Introspectable
diff --git a/docs/narr/events.rst b/docs/narr/events.rst
index 5004a1787..11af89ca6 100644
--- a/docs/narr/events.rst
+++ b/docs/narr/events.rst
@@ -229,5 +229,7 @@ This example view will notify all subscribers to the custom
``DocCreated`` event.
Note that when you fire an event, all subscribers are run
-synchronously on the current thread. So it's generally not a good idea
-to create event handlers that may take a long time to run.
+synchronously so it's generally not a good idea
+to create event handlers that may take a long time to run. Although
+event handlers could be used as a central place to spawn tasks on your
+own message queues.