… | |
… | |
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"). |
… | |
… | |
403 | will not restart syscalls (that includes Async::Interrupt and AnyEvent's |
403 | will not restart syscalls (that includes Async::Interrupt and AnyEvent's |
404 | pure perl implementation). |
404 | pure perl implementation). |
405 | |
405 | |
406 | Safe/Unsafe Signals |
406 | Safe/Unsafe Signals |
407 | Perl signals can be either "safe" (synchronous to opcode handling) or |
407 | Perl signals can be either "safe" (synchronous to opcode handling) or |
408 | "unsafe" (asynchronous) - the former might get delayed indefinitely, the |
408 | "unsafe" (asynchronous) - the former might delay signal delivery |
409 | latter might corrupt your memory. |
409 | indefinitely, the latter might corrupt your memory. |
410 | |
410 | |
411 | AnyEvent signal handlers are, in addition, synchronous to the event |
411 | AnyEvent signal handlers are, in addition, synchronous to the event |
412 | loop, i.e. they will not interrupt your running perl program but will |
412 | loop, i.e. they will not interrupt your running perl program but will |
413 | only be called as part of the normal event handling (just like timer, |
413 | only be called as part of the normal event handling (just like timer, |
414 | I/O etc. callbacks, too). |
414 | I/O etc. callbacks, too). |
… | |
… | |
416 | Signal Races, Delays and Workarounds |
416 | Signal Races, Delays and Workarounds |
417 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
417 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
418 | callbacks to signals in a generic way, which is a pity, as you cannot do |
418 | callbacks to signals in a generic way, which is a pity, as you cannot do |
419 | race-free signal handling in perl, requiring C libraries for this. |
419 | race-free signal handling in perl, requiring C libraries for this. |
420 | AnyEvent will try to do its best, which means in some cases, signals |
420 | AnyEvent will try to do its best, which means in some cases, signals |
421 | will be delayed. The maximum time a signal might be delayed is specified |
421 | will be delayed. The maximum time a signal might be delayed is 10 |
422 | in $AnyEvent::MAX_SIGNAL_LATENCY (default: 10 seconds). This variable |
422 | seconds by default, but can be overriden via |
423 | can be changed only before the first signal watcher is created, and |
423 | $ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY} or $AnyEvent::MAX_SIGNAL_LATENCY |
424 | should be left alone otherwise. This variable determines how often |
424 | - see the "ENVIRONMENT VARIABLES" section for details. |
425 | AnyEvent polls for signals (in case a wake-up was missed). Higher values |
|
|
426 | will cause fewer spurious wake-ups, which is better for power and CPU |
|
|
427 | saving. |
|
|
428 | |
425 | |
429 | All these problems can be avoided by installing the optional |
426 | All these problems can be avoided by installing the optional |
430 | Async::Interrupt module, which works with most event loops. It will not |
427 | Async::Interrupt module, which works with most event loops. It will not |
431 | work with inherently broken event loops such as Event or Event::Lib (and |
428 | work with inherently broken event loops such as Event or Event::Lib (and |
432 | not with POE currently, as POE does its own workaround with one-second |
|
|
433 | latency). For those, you just have to suffer the delays. |
429 | not with POE currently). For those, you just have to suffer the delays. |
434 | |
430 | |
435 | CHILD PROCESS WATCHERS |
431 | CHILD PROCESS WATCHERS |
436 | $w = AnyEvent->child (pid => <process id>, cb => <callback>); |
432 | $w = AnyEvent->child (pid => <process id>, cb => <callback>); |
437 | |
433 | |
438 | You can also watch for a child process exit and catch its exit status. |
434 | You can also watch for a child process exit and catch its exit status. |
… | |
… | |
740 | }; |
736 | }; |
741 | } |
737 | } |
742 | |
738 | |
743 | $cv->end; |
739 | $cv->end; |
744 | |
740 | |
|
|
741 | ... |
|
|
742 | |
|
|
743 | my $results = $cv->recv; |
|
|
744 | |
745 | This code fragment supposedly pings a number of hosts and calls |
745 | This code fragment supposedly pings a number of hosts and calls |
746 | "send" after results for all then have have been gathered - in any |
746 | "send" after results for all then have have been gathered - in any |
747 | order. To achieve this, the code issues a call to "begin" when it |
747 | order. To achieve this, the code issues a call to "begin" when it |
748 | starts each ping request and calls "end" when it has received some |
748 | starts each ping request and calls "end" when it has received some |
749 | result for it. Since "begin" and "end" only maintain a counter, the |
749 | result for it. Since "begin" and "end" only maintain a counter, the |
… | |
… | |
778 | In list context, all parameters passed to "send" will be returned, |
778 | In list context, all parameters passed to "send" will be returned, |
779 | in scalar context only the first one will be returned. |
779 | in scalar context only the first one will be returned. |
780 | |
780 | |
781 | Note that doing a blocking wait in a callback is not supported by |
781 | Note that doing a blocking wait in a callback is not supported by |
782 | any event loop, that is, recursive invocation of a blocking "->recv" |
782 | any event loop, that is, recursive invocation of a blocking "->recv" |
783 | is not allowed, and the "recv" call will "croak" if such a condition |
783 | is not allowed and the "recv" call will "croak" if such a condition |
784 | is detected. This condition can be slightly loosened by using |
784 | is detected. This requirement can be dropped by relying on |
785 | Coro::AnyEvent, which allows you to do a blocking "->recv" from any |
785 | Coro::AnyEvent , which allows you to do a blocking "->recv" from any |
786 | thread that doesn't run the event loop itself. |
786 | thread that doesn't run the event loop itself. Coro::AnyEvent is |
|
|
787 | loaded automatically when Coro is used with AnyEvent, so code does |
|
|
788 | not need to do anything special to take advantage of that: any code |
|
|
789 | that would normally block your program because it calls "recv", be |
|
|
790 | executed in an "async" thread instead without blocking other |
|
|
791 | threads. |
787 | |
792 | |
788 | Not all event models support a blocking wait - some die in that case |
793 | Not all event models support a blocking wait - some die in that case |
789 | (programs might want to do that to stay interactive), so *if you are |
794 | (programs might want to do that to stay interactive), so *if you are |
790 | using this from a module, never require a blocking wait*. Instead, |
795 | using this from a module, never require a blocking wait*. Instead, |
791 | let the caller decide whether the call will block or not (for |
796 | let the caller decide whether the call will block or not (for |
… | |
… | |
839 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
844 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
840 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
845 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
841 | AnyEvent::Impl::Irssi used when running within irssi. |
846 | AnyEvent::Impl::Irssi used when running within irssi. |
842 | AnyEvent::Impl::IOAsync based on IO::Async. |
847 | AnyEvent::Impl::IOAsync based on IO::Async. |
843 | AnyEvent::Impl::Cocoa based on Cocoa::EventLoop. |
848 | AnyEvent::Impl::Cocoa based on Cocoa::EventLoop. |
844 | AnyEvent::Impl::FLTK2 based on FLTK (fltk 2 binding). |
849 | AnyEvent::Impl::FLTK based on FLTK (fltk 2 binding). |
845 | |
850 | |
846 | Backends with special needs. |
851 | Backends with special needs. |
847 | Qt requires the Qt::Application to be instantiated first, but will |
852 | Qt requires the Qt::Application to be instantiated first, but will |
848 | otherwise be picked up automatically. As long as the main program |
853 | otherwise be picked up automatically. As long as the main program |
849 | instantiates the application before any AnyEvent watchers are |
854 | instantiates the application before any AnyEvent watchers are |
… | |
… | |
1010 | If AnyEvent::Log is not loaded then this function makes a simple |
1015 | If AnyEvent::Log is not loaded then this function makes a simple |
1011 | test to see whether the message will be logged. If the test succeeds |
1016 | test to see whether the message will be logged. If the test succeeds |
1012 | it will load AnyEvent::Log and call "AnyEvent::Log::log" - |
1017 | it will load AnyEvent::Log and call "AnyEvent::Log::log" - |
1013 | consequently, look at the AnyEvent::Log documentation for details. |
1018 | consequently, look at the AnyEvent::Log documentation for details. |
1014 | |
1019 | |
1015 | If the test fails it will simply return. |
1020 | If the test fails it will simply return. Right now this happens when |
|
|
1021 | a numerical loglevel is used and it is larger than the level |
|
|
1022 | specified via $ENV{PERL_ANYEVENT_VERBOSE}. |
1016 | |
1023 | |
1017 | If you want to sprinkle loads of logging calls around your code, |
1024 | If you want to sprinkle loads of logging calls around your code, |
1018 | consider creating a logger callback with the "AnyEvent::Log::logger" |
1025 | consider creating a logger callback with the "AnyEvent::Log::logger" |
1019 | function, which can reduce typing, codesize and can reduce the |
1026 | function, which can reduce typing, codesize and can reduce the |
1020 | logging overhead enourmously. |
1027 | logging overhead enourmously. |
… | |
… | |
1084 | modules come as part of AnyEvent, the others are available via CPAN (see |
1091 | modules come as part of AnyEvent, the others are available via CPAN (see |
1085 | <http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for a longer |
1092 | <http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for a longer |
1086 | non-exhaustive list), and the list is heavily biased towards modules of |
1093 | non-exhaustive list), and the list is heavily biased towards modules of |
1087 | the AnyEvent author himself :) |
1094 | the AnyEvent author himself :) |
1088 | |
1095 | |
1089 | AnyEvent::Util |
1096 | AnyEvent::Util (part of the AnyEvent distribution) |
1090 | Contains various utility functions that replace often-used blocking |
1097 | Contains various utility functions that replace often-used blocking |
1091 | functions such as "inet_aton" with event/callback-based versions. |
1098 | functions such as "inet_aton" with event/callback-based versions. |
1092 | |
1099 | |
1093 | AnyEvent::Socket |
1100 | AnyEvent::Socket (part of the AnyEvent distribution) |
1094 | Provides various utility functions for (internet protocol) sockets, |
1101 | Provides various utility functions for (internet protocol) sockets, |
1095 | addresses and name resolution. Also functions to create non-blocking |
1102 | addresses and name resolution. Also functions to create non-blocking |
1096 | tcp connections or tcp servers, with IPv6 and SRV record support and |
1103 | tcp connections or tcp servers, with IPv6 and SRV record support and |
1097 | more. |
1104 | more. |
1098 | |
1105 | |
1099 | AnyEvent::Handle |
1106 | AnyEvent::Handle (part of the AnyEvent distribution) |
1100 | Provide read and write buffers, manages watchers for reads and |
1107 | Provide read and write buffers, manages watchers for reads and |
1101 | writes, supports raw and formatted I/O, I/O queued and fully |
1108 | writes, supports raw and formatted I/O, I/O queued and fully |
1102 | transparent and non-blocking SSL/TLS (via AnyEvent::TLS). |
1109 | transparent and non-blocking SSL/TLS (via AnyEvent::TLS). |
1103 | |
1110 | |
1104 | AnyEvent::DNS |
1111 | AnyEvent::DNS (part of the AnyEvent distribution) |
1105 | Provides rich asynchronous DNS resolver capabilities. |
1112 | Provides rich asynchronous DNS resolver capabilities. |
1106 | |
1113 | |
1107 | AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD, |
1114 | AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD, |
1108 | AnyEvent::IGS, AnyEvent::FCP |
1115 | AnyEvent::IGS, AnyEvent::FCP |
1109 | Implement event-based interfaces to the protocols of the same name |
1116 | Implement event-based interfaces to the protocols of the same name |
1110 | (for the curious, IGS is the International Go Server and FCP is the |
1117 | (for the curious, IGS is the International Go Server and FCP is the |
1111 | Freenet Client Protocol). |
1118 | Freenet Client Protocol). |
1112 | |
1119 | |
1113 | AnyEvent::AIO |
1120 | AnyEvent::AIO (part of the AnyEvent distribution) |
1114 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1121 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1115 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1122 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1116 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1123 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1117 | event-based file I/O, and much more. |
1124 | event-based file I/O, and much more. |
1118 | |
1125 | |
… | |
… | |
1216 | This ensures that child processes will not see the "AE_" variables. |
1223 | This ensures that child processes will not see the "AE_" variables. |
1217 | |
1224 | |
1218 | The following environment variables are currently known to AnyEvent: |
1225 | The following environment variables are currently known to AnyEvent: |
1219 | |
1226 | |
1220 | "PERL_ANYEVENT_VERBOSE" |
1227 | "PERL_ANYEVENT_VERBOSE" |
1221 | By default, AnyEvent will be completely silent except in fatal |
1228 | By default, AnyEvent will log messages with loglevel 4 ("error") or |
1222 | conditions. You can set this environment variable to make AnyEvent |
1229 | higher (see AnyEvent::Log). You can set this environment variable to |
1223 | more talkative. If you want to do more than just set the global |
1230 | a numerical loglevel to make AnyEvent more (or less) talkative. |
|
|
1231 | |
|
|
1232 | If you want to do more than just set the global logging level you |
1224 | logging level you should have a look at "PERL_ANYEVENT_LOG", which |
1233 | should have a look at "PERL_ANYEVENT_LOG", which allows much more |
1225 | allows much more complex specifications. |
1234 | complex specifications. |
1226 | |
1235 | |
|
|
1236 | When set to 0 ("off"), then no messages whatsoever will be logged |
|
|
1237 | with everything else at defaults. |
|
|
1238 | |
1227 | When set to 5 or higher (warn), causes AnyEvent to warn about |
1239 | When set to 5 or higher ("warn"), AnyEvent warns about unexpected |
1228 | unexpected conditions, such as not being able to load the event |
1240 | conditions, such as not being able to load the event model specified |
1229 | model specified by "PERL_ANYEVENT_MODEL", or a guard callback |
1241 | by "PERL_ANYEVENT_MODEL", or a guard callback throwing an exception |
1230 | throwing an exception - this is the minimum recommended level. |
1242 | - this is the minimum recommended level for use during development. |
1231 | |
1243 | |
1232 | When set to 7 or higher (info), cause AnyEvent to report which event |
1244 | When set to 7 or higher (info), AnyEvent reports which event model |
1233 | model it chooses. |
1245 | it chooses. |
1234 | |
1246 | |
1235 | When set to 8 or higher (debug), then AnyEvent will report extra |
1247 | When set to 8 or higher (debug), then AnyEvent will report extra |
1236 | information on which optional modules it loads and how it implements |
1248 | information on which optional modules it loads and how it implements |
1237 | certain features. |
1249 | certain features. |
1238 | |
1250 | |
… | |
… | |
1250 | itself. |
1262 | itself. |
1251 | |
1263 | |
1252 | Note that specifying this environment variable causes the |
1264 | Note that specifying this environment variable causes the |
1253 | AnyEvent::Log module to be loaded, while "PERL_ANYEVENT_VERBOSE" |
1265 | AnyEvent::Log module to be loaded, while "PERL_ANYEVENT_VERBOSE" |
1254 | does not, so only using the latter saves a few hundred kB of memory |
1266 | does not, so only using the latter saves a few hundred kB of memory |
1255 | until the first message is being logged. |
1267 | unless a module explicitly needs the extra features of |
|
|
1268 | AnyEvent::Log. |
1256 | |
1269 | |
1257 | "PERL_ANYEVENT_STRICT" |
1270 | "PERL_ANYEVENT_STRICT" |
1258 | AnyEvent does not do much argument checking by default, as thorough |
1271 | AnyEvent does not do much argument checking by default, as thorough |
1259 | argument checking is very costly. Setting this variable to a true |
1272 | argument checking is very costly. Setting this variable to a true |
1260 | value will cause AnyEvent to load "AnyEvent::Strict" and then to |
1273 | value will cause AnyEvent to load "AnyEvent::Strict" and then to |
… | |
… | |
1267 | is definitely recommended to keep it off in production. Keeping |
1280 | is definitely recommended to keep it off in production. Keeping |
1268 | "PERL_ANYEVENT_STRICT=1" in your environment while developing |
1281 | "PERL_ANYEVENT_STRICT=1" in your environment while developing |
1269 | programs can be very useful, however. |
1282 | programs can be very useful, however. |
1270 | |
1283 | |
1271 | "PERL_ANYEVENT_DEBUG_SHELL" |
1284 | "PERL_ANYEVENT_DEBUG_SHELL" |
1272 | If this env variable is set, then its contents will be interpreted |
1285 | If this env variable is nonempty, then its contents will be |
1273 | by "AnyEvent::Socket::parse_hostport" (after replacing every |
1286 | interpreted by "AnyEvent::Socket::parse_hostport" and |
1274 | occurance of $$ by the process pid) and an "AnyEvent::Debug::shell" |
1287 | "AnyEvent::Debug::shell" (after replacing every occurance of $$ by |
1275 | is bound on that port. The shell object is saved in |
1288 | the process pid). The shell object is saved in |
1276 | $AnyEvent::Debug::SHELL. |
1289 | $AnyEvent::Debug::SHELL. |
1277 | |
1290 | |
1278 | This happens when the first watcher is created. |
1291 | This happens when the first watcher is created. |
1279 | |
1292 | |
1280 | For example, to bind a debug shell on a unix domain socket in |
1293 | For example, to bind a debug shell on a unix domain socket in |
1281 | /tmp/debug<pid>.sock, you could use this: |
1294 | /tmp/debug<pid>.sock, you could use this: |
1282 | |
1295 | |
1283 | PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog |
1296 | PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog |
|
|
1297 | # connect with e.g.: socat readline /tmp/debug123.sock |
1284 | |
1298 | |
|
|
1299 | Or to bind to tcp port 4545 on localhost: |
|
|
1300 | |
|
|
1301 | PERL_ANYEVENT_DEBUG_SHELL=127.0.0.1:4545 perlprog |
|
|
1302 | # connect with e.g.: telnet localhost 4545 |
|
|
1303 | |
1285 | Note that creating sockets in /tmp is very unsafe on multiuser |
1304 | Note that creating sockets in /tmp or on localhost is very unsafe on |
1286 | systems. |
1305 | multiuser systems. |
1287 | |
1306 | |
1288 | "PERL_ANYEVENT_DEBUG_WRAP" |
1307 | "PERL_ANYEVENT_DEBUG_WRAP" |
1289 | Can be set to 0, 1 or 2 and enables wrapping of all watchers for |
1308 | Can be set to 0, 1 or 2 and enables wrapping of all watchers for |
1290 | debugging purposes. See "AnyEvent::Debug::wrap" for details. |
1309 | debugging purposes. See "AnyEvent::Debug::wrap" for details. |
1291 | |
1310 | |
… | |
… | |
1306 | |
1325 | |
1307 | For example, to force the pure perl model (AnyEvent::Loop::Perl) you |
1326 | For example, to force the pure perl model (AnyEvent::Loop::Perl) you |
1308 | could start your program like this: |
1327 | could start your program like this: |
1309 | |
1328 | |
1310 | PERL_ANYEVENT_MODEL=Perl perl ... |
1329 | PERL_ANYEVENT_MODEL=Perl perl ... |
|
|
1330 | |
|
|
1331 | "PERL_ANYEVENT_IO_MODEL" |
|
|
1332 | The current file I/O model - see AnyEvent::IO for more info. |
|
|
1333 | |
|
|
1334 | At the moment, only "Perl" (small, pure-perl, synchronous) and |
|
|
1335 | "IOAIO" (truly asynchronous) are supported. The default is "IOAIO" |
|
|
1336 | if AnyEvent::AIO can be loaded, otherwise it is "Perl". |
1311 | |
1337 | |
1312 | "PERL_ANYEVENT_PROTOCOLS" |
1338 | "PERL_ANYEVENT_PROTOCOLS" |
1313 | Used by both AnyEvent::DNS and AnyEvent::Socket to determine |
1339 | Used by both AnyEvent::DNS and AnyEvent::Socket to determine |
1314 | preferences for IPv4 or IPv6. The default is unspecified (and might |
1340 | preferences for IPv4 or IPv6. The default is unspecified (and might |
1315 | change, or be the result of auto probing). |
1341 | change, or be the result of auto probing). |
… | |
… | |
1351 | |
1377 | |
1352 | "PERL_ANYEVENT_MAX_OUTSTANDING_DNS" |
1378 | "PERL_ANYEVENT_MAX_OUTSTANDING_DNS" |
1353 | The default value for the "max_outstanding" parameter for the |
1379 | The default value for the "max_outstanding" parameter for the |
1354 | default DNS resolver - this is the maximum number of parallel DNS |
1380 | default DNS resolver - this is the maximum number of parallel DNS |
1355 | requests that are sent to the DNS server. |
1381 | requests that are sent to the DNS server. |
|
|
1382 | |
|
|
1383 | "PERL_ANYEVENT_MAX_SIGNAL_LATENCY" |
|
|
1384 | Perl has inherently racy signal handling (you can basically choose |
|
|
1385 | between losing signals and memory corruption) - pure perl event |
|
|
1386 | loops (including "AnyEvent::Loop", when "Async::Interrupt" isn't |
|
|
1387 | available) therefore have to poll regularly to avoid losing signals. |
|
|
1388 | |
|
|
1389 | Some event loops are racy, but don't poll regularly, and some event |
|
|
1390 | loops are written in C but are still racy. For those event loops, |
|
|
1391 | AnyEvent installs a timer that regularly wakes up the event loop. |
|
|
1392 | |
|
|
1393 | By default, the interval for this timer is 10 seconds, but you can |
|
|
1394 | override this delay with this environment variable (or by setting |
|
|
1395 | the $AnyEvent::MAX_SIGNAL_LATENCY variable before creating signal |
|
|
1396 | watchers). |
|
|
1397 | |
|
|
1398 | Lower values increase CPU (and energy) usage, higher values can |
|
|
1399 | introduce long delays when reaping children or waiting for signals. |
|
|
1400 | |
|
|
1401 | The AnyEvent::Async module, if available, will be used to avoid this |
|
|
1402 | polling (with most event loops). |
1356 | |
1403 | |
1357 | "PERL_ANYEVENT_RESOLV_CONF" |
1404 | "PERL_ANYEVENT_RESOLV_CONF" |
1358 | The absolute path to a resolv.conf-style file to use instead of |
1405 | The absolute path to a resolv.conf-style file to use instead of |
1359 | /etc/resolv.conf (or the OS-specific configuration) in the default |
1406 | /etc/resolv.conf (or the OS-specific configuration) in the default |
1360 | resolver, or the empty string to select the default configuration. |
1407 | resolver, or the empty string to select the default configuration. |
… | |
… | |
1963 | This module is part of perl since release 5.008. It will be used |
2010 | This module is part of perl since release 5.008. It will be used |
1964 | when the chosen event library does not come with a timing source of |
2011 | when the chosen event library does not come with a timing source of |
1965 | its own. The pure-perl event loop (AnyEvent::Loop) will additionally |
2012 | its own. The pure-perl event loop (AnyEvent::Loop) will additionally |
1966 | load it to try to use a monotonic clock for timing stability. |
2013 | load it to try to use a monotonic clock for timing stability. |
1967 | |
2014 | |
|
|
2015 | AnyEvent::AIO (and IO::AIO) |
|
|
2016 | The default implementation of AnyEvent::IO is to do I/O |
|
|
2017 | synchronously, stopping programs while they access the disk, which |
|
|
2018 | is fine for a lot of programs. |
|
|
2019 | |
|
|
2020 | Installing AnyEvent::AIO (and its IO::AIO dependency) makes it |
|
|
2021 | switch to a true asynchronous implementation, so event processing |
|
|
2022 | can continue even while waiting for disk I/O. |
|
|
2023 | |
1968 | FORK |
2024 | FORK |
1969 | Most event libraries are not fork-safe. The ones who are usually are |
2025 | Most event libraries are not fork-safe. The ones who are usually are |
1970 | because they rely on inefficient but fork-safe "select" or "poll" calls |
2026 | because they rely on inefficient but fork-safe "select" or "poll" calls |
1971 | - higher performance APIs such as BSD's kqueue or the dreaded Linux |
2027 | - higher performance APIs such as BSD's kqueue or the dreaded Linux |
1972 | epoll are usually badly thought-out hacks that are incompatible with |
2028 | epoll are usually badly thought-out hacks that are incompatible with |
… | |
… | |
2043 | AnyEvent::Impl::IOAsync, Anyevent::Impl::Irssi, AnyEvent::Impl::FLTK. |
2099 | AnyEvent::Impl::IOAsync, Anyevent::Impl::Irssi, AnyEvent::Impl::FLTK. |
2044 | |
2100 | |
2045 | Non-blocking handles, pipes, stream sockets, TCP clients and servers: |
2101 | Non-blocking handles, pipes, stream sockets, TCP clients and servers: |
2046 | AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS. |
2102 | AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS. |
2047 | |
2103 | |
|
|
2104 | Asynchronous File I/O: AnyEvent::IO. |
|
|
2105 | |
2048 | Asynchronous DNS: AnyEvent::DNS. |
2106 | Asynchronous DNS: AnyEvent::DNS. |
2049 | |
2107 | |
2050 | Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event. |
2108 | Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event. |
2051 | |
2109 | |
2052 | Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::IRC, |
2110 | Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::IRC, |
2053 | AnyEvent::HTTP. |
2111 | AnyEvent::HTTP. |
2054 | |
2112 | |
2055 | AUTHOR |
2113 | AUTHOR |
2056 | Marc Lehmann <schmorp@schmorp.de> |
2114 | Marc Lehmann <schmorp@schmorp.de> |
2057 | http://home.schmorp.de/ |
2115 | http://anyevent.schmorp.de |
2058 | |
2116 | |