… | |
… | |
262 | |
262 | |
263 | Example 2: fire an event after 0.5 seconds, then roughly every second. |
263 | Example 2: fire an event after 0.5 seconds, then roughly every second. |
264 | |
264 | |
265 | my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub { |
265 | my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub { |
266 | warn "timeout\n"; |
266 | warn "timeout\n"; |
267 | }; |
267 | }); |
268 | |
268 | |
269 | TIMING ISSUES |
269 | TIMING ISSUES |
270 | There are two ways to handle timers: based on real time (relative, "fire |
270 | There are two ways to handle timers: based on real time (relative, "fire |
271 | in 10 seconds") and based on wallclock time (absolute, "fire at 12 |
271 | in 10 seconds") and based on wallclock time (absolute, "fire at 12 |
272 | o'clock"). |
272 | o'clock"). |
… | |
… | |
469 | |
469 | |
470 | Example: fork a process and wait for it |
470 | Example: fork a process and wait for it |
471 | |
471 | |
472 | my $done = AnyEvent->condvar; |
472 | my $done = AnyEvent->condvar; |
473 | |
473 | |
|
|
474 | # this forks and immediately calls exit in the child. this |
|
|
475 | # normally has all sorts of bad consequences for your parent, |
|
|
476 | # so take this as an example only. always fork and exec, |
|
|
477 | # or call POSIX::_exit, in real code. |
474 | my $pid = fork or exit 5; |
478 | my $pid = fork or exit 5; |
475 | |
479 | |
476 | my $w = AnyEvent->child ( |
480 | my $w = AnyEvent->child ( |
477 | pid => $pid, |
481 | pid => $pid, |
478 | cb => sub { |
482 | cb => sub { |
… | |
… | |
718 | This works because for every event source (EOF on file handle), |
722 | This works because for every event source (EOF on file handle), |
719 | there is one call to "begin", so the condvar waits for all calls to |
723 | there is one call to "begin", so the condvar waits for all calls to |
720 | "end" before sending. |
724 | "end" before sending. |
721 | |
725 | |
722 | The ping example mentioned above is slightly more complicated, as |
726 | The ping example mentioned above is slightly more complicated, as |
723 | the there are results to be passwd back, and the number of tasks |
727 | the there are results to be passed back, and the number of tasks |
724 | that are begun can potentially be zero: |
728 | that are begun can potentially be zero: |
725 | |
729 | |
726 | my $cv = AnyEvent->condvar; |
730 | my $cv = AnyEvent->condvar; |
727 | |
731 | |
728 | my %result; |
732 | my %result; |
… | |
… | |
736 | }; |
740 | }; |
737 | } |
741 | } |
738 | |
742 | |
739 | $cv->end; |
743 | $cv->end; |
740 | |
744 | |
|
|
745 | ... |
|
|
746 | |
|
|
747 | my $results = $cv->recv; |
|
|
748 | |
741 | This code fragment supposedly pings a number of hosts and calls |
749 | This code fragment supposedly pings a number of hosts and calls |
742 | "send" after results for all then have have been gathered - in any |
750 | "send" after results for all then have have been gathered - in any |
743 | order. To achieve this, the code issues a call to "begin" when it |
751 | order. To achieve this, the code issues a call to "begin" when it |
744 | starts each ping request and calls "end" when it has received some |
752 | starts each ping request and calls "end" when it has received some |
745 | result for it. Since "begin" and "end" only maintain a counter, the |
753 | result for it. Since "begin" and "end" only maintain a counter, the |
… | |
… | |
774 | In list context, all parameters passed to "send" will be returned, |
782 | In list context, all parameters passed to "send" will be returned, |
775 | in scalar context only the first one will be returned. |
783 | in scalar context only the first one will be returned. |
776 | |
784 | |
777 | Note that doing a blocking wait in a callback is not supported by |
785 | Note that doing a blocking wait in a callback is not supported by |
778 | any event loop, that is, recursive invocation of a blocking "->recv" |
786 | any event loop, that is, recursive invocation of a blocking "->recv" |
779 | is not allowed, and the "recv" call will "croak" if such a condition |
787 | is not allowed and the "recv" call will "croak" if such a condition |
780 | is detected. This condition can be slightly loosened by using |
788 | is detected. This requirement can be dropped by relying on |
781 | Coro::AnyEvent, which allows you to do a blocking "->recv" from any |
789 | Coro::AnyEvent , which allows you to do a blocking "->recv" from any |
782 | thread that doesn't run the event loop itself. |
790 | thread that doesn't run the event loop itself. Coro::AnyEvent is |
|
|
791 | loaded automatically when Coro is used with AnyEvent, so code does |
|
|
792 | not need to do anything special to take advantage of that: any code |
|
|
793 | that would normally block your program because it calls "recv", be |
|
|
794 | executed in an "async" thread instead without blocking other |
|
|
795 | threads. |
783 | |
796 | |
784 | Not all event models support a blocking wait - some die in that case |
797 | Not all event models support a blocking wait - some die in that case |
785 | (programs might want to do that to stay interactive), so *if you are |
798 | (programs might want to do that to stay interactive), so *if you are |
786 | using this from a module, never require a blocking wait*. Instead, |
799 | using this from a module, never require a blocking wait*. Instead, |
787 | let the caller decide whether the call will block or not (for |
800 | let the caller decide whether the call will block or not (for |
… | |
… | |
1082 | modules come as part of AnyEvent, the others are available via CPAN (see |
1095 | modules come as part of AnyEvent, the others are available via CPAN (see |
1083 | <http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for a longer |
1096 | <http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for a longer |
1084 | non-exhaustive list), and the list is heavily biased towards modules of |
1097 | non-exhaustive list), and the list is heavily biased towards modules of |
1085 | the AnyEvent author himself :) |
1098 | the AnyEvent author himself :) |
1086 | |
1099 | |
1087 | AnyEvent::Util |
1100 | AnyEvent::Util (part of the AnyEvent distribution) |
1088 | Contains various utility functions that replace often-used blocking |
1101 | Contains various utility functions that replace often-used blocking |
1089 | functions such as "inet_aton" with event/callback-based versions. |
1102 | functions such as "inet_aton" with event/callback-based versions. |
1090 | |
1103 | |
1091 | AnyEvent::Socket |
1104 | AnyEvent::Socket (part of the AnyEvent distribution) |
1092 | Provides various utility functions for (internet protocol) sockets, |
1105 | Provides various utility functions for (internet protocol) sockets, |
1093 | addresses and name resolution. Also functions to create non-blocking |
1106 | addresses and name resolution. Also functions to create non-blocking |
1094 | tcp connections or tcp servers, with IPv6 and SRV record support and |
1107 | tcp connections or tcp servers, with IPv6 and SRV record support and |
1095 | more. |
1108 | more. |
1096 | |
1109 | |
1097 | AnyEvent::Handle |
1110 | AnyEvent::Handle (part of the AnyEvent distribution) |
1098 | Provide read and write buffers, manages watchers for reads and |
1111 | Provide read and write buffers, manages watchers for reads and |
1099 | writes, supports raw and formatted I/O, I/O queued and fully |
1112 | writes, supports raw and formatted I/O, I/O queued and fully |
1100 | transparent and non-blocking SSL/TLS (via AnyEvent::TLS). |
1113 | transparent and non-blocking SSL/TLS (via AnyEvent::TLS). |
1101 | |
1114 | |
1102 | AnyEvent::DNS |
1115 | AnyEvent::DNS (part of the AnyEvent distribution) |
1103 | Provides rich asynchronous DNS resolver capabilities. |
1116 | Provides rich asynchronous DNS resolver capabilities. |
1104 | |
1117 | |
1105 | AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD, |
1118 | AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD, |
1106 | AnyEvent::IGS, AnyEvent::FCP |
1119 | AnyEvent::IGS, AnyEvent::FCP |
1107 | Implement event-based interfaces to the protocols of the same name |
1120 | Implement event-based interfaces to the protocols of the same name |
1108 | (for the curious, IGS is the International Go Server and FCP is the |
1121 | (for the curious, IGS is the International Go Server and FCP is the |
1109 | Freenet Client Protocol). |
1122 | Freenet Client Protocol). |
1110 | |
1123 | |
1111 | AnyEvent::AIO |
1124 | AnyEvent::AIO (part of the AnyEvent distribution) |
1112 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1125 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1113 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1126 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1114 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1127 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1115 | event-based file I/O, and much more. |
1128 | event-based file I/O, and much more. |
|
|
1129 | |
|
|
1130 | AnyEvent::Fork, AnyEvent::Fork::RPC, AnyEvent::Fork::Pool, |
|
|
1131 | AnyEvent::Fork::Remote |
|
|
1132 | These let you safely fork new subprocesses, either locally or |
|
|
1133 | remotely (e.g.v ia ssh), using some RPC protocol or not, without the |
|
|
1134 | limitations normally imposed by fork (AnyEvent works fine for |
|
|
1135 | example). Dynamically-resized worker pools are obviously included as |
|
|
1136 | well. |
|
|
1137 | |
|
|
1138 | And they are quite tiny and fast as well - "abusing" AnyEvent::Fork |
|
|
1139 | just to exec external programs can easily beat using "fork" and |
|
|
1140 | "exec" (or even "system") in most programs. |
1116 | |
1141 | |
1117 | AnyEvent::Filesys::Notify |
1142 | AnyEvent::Filesys::Notify |
1118 | AnyEvent is good for non-blocking stuff, but it can't detect file or |
1143 | AnyEvent is good for non-blocking stuff, but it can't detect file or |
1119 | path changes (e.g. "watch this directory for new files", "watch this |
1144 | path changes (e.g. "watch this directory for new files", "watch this |
1120 | file for changes"). The AnyEvent::Filesys::Notify module promises to |
1145 | file for changes"). The AnyEvent::Filesys::Notify module promises to |
… | |
… | |
1122 | and some weird, without doubt broken, stuff on OS X to monitor |
1147 | and some weird, without doubt broken, stuff on OS X to monitor |
1123 | files. It can fall back to blocking scans at regular intervals |
1148 | files. It can fall back to blocking scans at regular intervals |
1124 | transparently on other platforms, so it's about as portable as it |
1149 | transparently on other platforms, so it's about as portable as it |
1125 | gets. |
1150 | gets. |
1126 | |
1151 | |
1127 | (I haven't used it myself, but I haven't heard anybody complaining |
1152 | (I haven't used it myself, but it seems the biggest problem with it |
1128 | about it yet). |
1153 | is it quite bad performance). |
1129 | |
1154 | |
1130 | AnyEvent::DBI |
1155 | AnyEvent::DBI |
1131 | Executes DBI requests asynchronously in a proxy process for you, |
1156 | Executes DBI requests asynchronously in a proxy process for you, |
1132 | notifying you in an event-based way when the operation is finished. |
1157 | notifying you in an event-based way when the operation is finished. |
1133 | |
|
|
1134 | AnyEvent::HTTPD |
|
|
1135 | A simple embedded webserver. |
|
|
1136 | |
1158 | |
1137 | AnyEvent::FastPing |
1159 | AnyEvent::FastPing |
1138 | The fastest ping in the west. |
1160 | The fastest ping in the west. |
1139 | |
1161 | |
1140 | Coro |
1162 | Coro |
… | |
… | |
2001 | This module is part of perl since release 5.008. It will be used |
2023 | This module is part of perl since release 5.008. It will be used |
2002 | when the chosen event library does not come with a timing source of |
2024 | when the chosen event library does not come with a timing source of |
2003 | its own. The pure-perl event loop (AnyEvent::Loop) will additionally |
2025 | its own. The pure-perl event loop (AnyEvent::Loop) will additionally |
2004 | load it to try to use a monotonic clock for timing stability. |
2026 | load it to try to use a monotonic clock for timing stability. |
2005 | |
2027 | |
|
|
2028 | AnyEvent::AIO (and IO::AIO) |
|
|
2029 | The default implementation of AnyEvent::IO is to do I/O |
|
|
2030 | synchronously, stopping programs while they access the disk, which |
|
|
2031 | is fine for a lot of programs. |
|
|
2032 | |
|
|
2033 | Installing AnyEvent::AIO (and its IO::AIO dependency) makes it |
|
|
2034 | switch to a true asynchronous implementation, so event processing |
|
|
2035 | can continue even while waiting for disk I/O. |
|
|
2036 | |
2006 | FORK |
2037 | FORK |
2007 | Most event libraries are not fork-safe. The ones who are usually are |
2038 | Most event libraries are not fork-safe. The ones who are usually are |
2008 | because they rely on inefficient but fork-safe "select" or "poll" calls |
2039 | because they rely on inefficient but fork-safe "select" or "poll" calls |
2009 | - higher performance APIs such as BSD's kqueue or the dreaded Linux |
2040 | - higher performance APIs such as BSD's kqueue or the dreaded Linux |
2010 | epoll are usually badly thought-out hacks that are incompatible with |
2041 | epoll are usually badly thought-out hacks that are incompatible with |
… | |
… | |
2017 | usually happens when the first AnyEvent watcher is created, or the |
2048 | usually happens when the first AnyEvent watcher is created, or the |
2018 | library is loaded). |
2049 | library is loaded). |
2019 | |
2050 | |
2020 | If you have to fork, you must either do so *before* creating your first |
2051 | If you have to fork, you must either do so *before* creating your first |
2021 | watcher OR you must not use AnyEvent at all in the child OR you must do |
2052 | watcher OR you must not use AnyEvent at all in the child OR you must do |
2022 | something completely out of the scope of AnyEvent. |
2053 | something completely out of the scope of AnyEvent (see below). |
2023 | |
2054 | |
2024 | The problem of doing event processing in the parent *and* the child is |
2055 | The problem of doing event processing in the parent *and* the child is |
2025 | much more complicated: even for backends that *are* fork-aware or |
2056 | much more complicated: even for backends that *are* fork-aware or |
2026 | fork-safe, their behaviour is not usually what you want: fork clones all |
2057 | fork-safe, their behaviour is not usually what you want: fork clones all |
2027 | watchers, that means all timers, I/O watchers etc. are active in both |
2058 | watchers, that means all timers, I/O watchers etc. are active in both |
2028 | parent and child, which is almost never what you want. USing "exec" to |
2059 | parent and child, which is almost never what you want. Using "exec" to |
2029 | start worker children from some kind of manage rprocess is usually |
2060 | start worker children from some kind of manage prrocess is usually |
2030 | preferred, because it is much easier and cleaner, at the expense of |
2061 | preferred, because it is much easier and cleaner, at the expense of |
2031 | having to have another binary. |
2062 | having to have another binary. |
|
|
2063 | |
|
|
2064 | In addition to logical problems with fork, there are also implementation |
|
|
2065 | problems. For example, on POSIX systems, you cannot fork at all in Perl |
|
|
2066 | code if a thread (I am talking of pthreads here) was ever created in the |
|
|
2067 | process, and this is just the tip of the iceberg. In general, using fork |
|
|
2068 | from Perl is difficult, and attempting to use fork without an exec to |
|
|
2069 | implement some kind of parallel processing is almost certainly doomed. |
|
|
2070 | |
|
|
2071 | To safely fork and exec, you should use a module such as Proc::FastSpawn |
|
|
2072 | that let's you safely fork and exec new processes. |
|
|
2073 | |
|
|
2074 | If you want to do multiprocessing using processes, you can look at the |
|
|
2075 | AnyEvent::Fork module (and some related modules such as |
|
|
2076 | AnyEvent::Fork::RPC, AnyEvent::Fork::Pool and AnyEvent::Fork::Remote). |
|
|
2077 | This module allows you to safely create subprocesses without any |
|
|
2078 | limitations - you can use X11 toolkits or AnyEvent in the children |
|
|
2079 | created by AnyEvent::Fork safely and without any special precautions. |
2032 | |
2080 | |
2033 | SECURITY CONSIDERATIONS |
2081 | SECURITY CONSIDERATIONS |
2034 | AnyEvent can be forced to load any event model via |
2082 | AnyEvent can be forced to load any event model via |
2035 | $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used |
2083 | $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used |
2036 | to execute arbitrary code or directly gain access, it can easily be used |
2084 | to execute arbitrary code or directly gain access, it can easily be used |