diff options
author | root <root> | 2012-04-28 12:10:07 +0000 |
---|---|---|
committer | root <root> | 2012-04-28 12:10:07 +0000 |
commit | 6b2ac50b05c2fbd0025f2cb5ff1c654bdab8949a (patch) | |
tree | 6a565c837e536a6cbb55e98f07603368f5254ebc | |
parent | 7a5605caed9da54c5b02d99104e68b8b96cc3c1b (diff) |
*** empty log message ***
-rw-r--r-- | ev.pod | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -3315,7 +3315,7 @@ it by calling C<ev_async_send>, which is thread- and signal safe. This functionality is very similar to C<ev_signal> watchers, as signals, too, are asynchronous in nature, and signals, too, will be compressed (i.e. the number of callback invocations may be less than the number of -C<ev_async_sent> calls). In fact, you could use signal watchers as a kind +C<ev_async_send> calls). In fact, you could use signal watchers as a kind of "global async watchers" by using a watcher on an otherwise unused signal, and C<ev_feed_signal> to signal this watcher from another thread, even without knowing which loop owns the signal. |