From 21677667c48f905e6efd47ad5c9bfe908f1259ef Mon Sep 17 00:00:00 2001 From: root Date: Fri, 19 Sep 2008 03:52:56 +0000 Subject: *** empty log message *** --- ev.pod | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'ev.pod') diff --git a/ev.pod b/ev.pod index b973673..fd20a8e 100644 --- a/ev.pod +++ b/ev.pod @@ -3283,11 +3283,15 @@ Choosing a model is hard - look around, learn, know that usually you can do better than you currently do :-) =item * often you need to talk to some other thread which blocks in the -event loop - C watchers can be used to wake them up from other -threads safely (or from signal contexts...). +event loop. + +C watchers can be used to wake them up from other threads safely +(or from signal contexts...). -=item * some watcher types are only supported in the default loop - use -C watchers to tell your other loops about any such events. +An example use would be to communicate signals or other events that only +work in the default loop by registering the signal watcher with the +default loop and triggering an C watcher from the default loop +watcher callback into the event loop interested in the signal. =back -- cgit v1.2.3