ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/README
(Generate patch)

Comparing AnyEvent/README (file contents):
Revision 1.69 by root, Tue Oct 4 17:45:04 2011 UTC vs.
Revision 1.75 by root, Thu Jul 16 12:48:38 2015 UTC

1NAME 1NAME
2 AnyEvent - the DBI of event loop programming 2 AnyEvent - the DBI of event loop programming
3 3
4 EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, 4 EV, Event, Glib, Tk, UV, Perl, Event::Lib, Irssi, rxvt-unicode,
5 Qt, FLTK and POE are various supported event loops/environments. 5 IO::Async, Qt, FLTK and POE are various supported event
6 loops/environments.
6 7
7SYNOPSIS 8SYNOPSIS
8 use AnyEvent; 9 use AnyEvent;
9 10
10 # if you prefer function calls, look at the AE manpage for 11 # if you prefer function calls, look at the AE manpage for
262 263
263 Example 2: fire an event after 0.5 seconds, then roughly every second. 264 Example 2: fire an event after 0.5 seconds, then roughly every second.
264 265
265 my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub { 266 my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
266 warn "timeout\n"; 267 warn "timeout\n";
267 }; 268 });
268 269
269 TIMING ISSUES 270 TIMING ISSUES
270 There are two ways to handle timers: based on real time (relative, "fire 271 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 272 in 10 seconds") and based on wallclock time (absolute, "fire at 12
272 o'clock"). 273 o'clock").
419 race-free signal handling in perl, requiring C libraries for this. 420 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 421 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 10 422 will be delayed. The maximum time a signal might be delayed is 10
422 seconds by default, but can be overriden via 423 seconds by default, but can be overriden via
423 $ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY} or $AnyEvent::MAX_SIGNAL_LATENCY 424 $ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY} or $AnyEvent::MAX_SIGNAL_LATENCY
424 - see the Ö<ENVIRONMENT VARIABLES> section for details. 425 - see the "ENVIRONMENT VARIABLES" section for details.
425 426
426 All these problems can be avoided by installing the optional 427 All these problems can be avoided by installing the optional
427 Async::Interrupt module, which works with most event loops. It will not 428 Async::Interrupt module, which works with most event loops. It will not
428 work with inherently broken event loops such as Event or Event::Lib (and 429 work with inherently broken event loops such as Event or Event::Lib (and
429 not with POE currently). For those, you just have to suffer the delays. 430 not with POE currently). For those, you just have to suffer the delays.
469 470
470 Example: fork a process and wait for it 471 Example: fork a process and wait for it
471 472
472 my $done = AnyEvent->condvar; 473 my $done = AnyEvent->condvar;
473 474
475 # this forks and immediately calls exit in the child. this
476 # normally has all sorts of bad consequences for your parent,
477 # so take this as an example only. always fork and exec,
478 # or call POSIX::_exit, in real code.
474 my $pid = fork or exit 5; 479 my $pid = fork or exit 5;
475 480
476 my $w = AnyEvent->child ( 481 my $w = AnyEvent->child (
477 pid => $pid, 482 pid => $pid,
478 cb => sub { 483 cb => sub {
718 This works because for every event source (EOF on file handle), 723 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 724 there is one call to "begin", so the condvar waits for all calls to
720 "end" before sending. 725 "end" before sending.
721 726
722 The ping example mentioned above is slightly more complicated, as 727 The ping example mentioned above is slightly more complicated, as
723 the there are results to be passwd back, and the number of tasks 728 the there are results to be passed back, and the number of tasks
724 that are begun can potentially be zero: 729 that are begun can potentially be zero:
725 730
726 my $cv = AnyEvent->condvar; 731 my $cv = AnyEvent->condvar;
727 732
728 my %result; 733 my %result;
736 }; 741 };
737 } 742 }
738 743
739 $cv->end; 744 $cv->end;
740 745
746 ...
747
748 my $results = $cv->recv;
749
741 This code fragment supposedly pings a number of hosts and calls 750 This code fragment supposedly pings a number of hosts and calls
742 "send" after results for all then have have been gathered - in any 751 "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 752 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 753 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 754 result for it. Since "begin" and "end" only maintain a counter, the
774 In list context, all parameters passed to "send" will be returned, 783 In list context, all parameters passed to "send" will be returned,
775 in scalar context only the first one will be returned. 784 in scalar context only the first one will be returned.
776 785
777 Note that doing a blocking wait in a callback is not supported by 786 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" 787 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 788 is not allowed and the "recv" call will "croak" if such a condition
780 is detected. This condition can be slightly loosened by using 789 is detected. This requirement can be dropped by relying on
781 Coro::AnyEvent, which allows you to do a blocking "->recv" from any 790 Coro::AnyEvent , which allows you to do a blocking "->recv" from any
782 thread that doesn't run the event loop itself. 791 thread that doesn't run the event loop itself. Coro::AnyEvent is
792 loaded automatically when Coro is used with AnyEvent, so code does
793 not need to do anything special to take advantage of that: any code
794 that would normally block your program because it calls "recv", be
795 executed in an "async" thread instead without blocking other
796 threads.
783 797
784 Not all event models support a blocking wait - some die in that case 798 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 799 (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, 800 using this from a module, never require a blocking wait*. Instead,
787 let the caller decide whether the call will block or not (for 801 let the caller decide whether the call will block or not (for
830 by the main program. 844 by the main program.
831 845
832 AnyEvent::Impl::Event based on Event, very stable, few glitches. 846 AnyEvent::Impl::Event based on Event, very stable, few glitches.
833 AnyEvent::Impl::Glib based on Glib, slow but very stable. 847 AnyEvent::Impl::Glib based on Glib, slow but very stable.
834 AnyEvent::Impl::Tk based on Tk, very broken. 848 AnyEvent::Impl::Tk based on Tk, very broken.
849 AnyEvent::Impl::UV based on UV, innovated square wheels.
835 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. 850 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
836 AnyEvent::Impl::POE based on POE, very slow, some limitations. 851 AnyEvent::Impl::POE based on POE, very slow, some limitations.
837 AnyEvent::Impl::Irssi used when running within irssi. 852 AnyEvent::Impl::Irssi used when running within irssi.
838 AnyEvent::Impl::IOAsync based on IO::Async. 853 AnyEvent::Impl::IOAsync based on IO::Async.
839 AnyEvent::Impl::Cocoa based on Cocoa::EventLoop. 854 AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
971 To understand the usefulness of this function, consider a function 986 To understand the usefulness of this function, consider a function
972 that asynchronously does something for you and returns some 987 that asynchronously does something for you and returns some
973 transaction object or guard to let you cancel the operation. For 988 transaction object or guard to let you cancel the operation. For
974 example, "AnyEvent::Socket::tcp_connect": 989 example, "AnyEvent::Socket::tcp_connect":
975 990
976 # start a conenction attempt unless one is active 991 # start a connection attempt unless one is active
977 $self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub { 992 $self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
978 delete $self->{connect_guard}; 993 delete $self->{connect_guard};
979 ... 994 ...
980 }; 995 };
981 996
1015 If you want to sprinkle loads of logging calls around your code, 1030 If you want to sprinkle loads of logging calls around your code,
1016 consider creating a logger callback with the "AnyEvent::Log::logger" 1031 consider creating a logger callback with the "AnyEvent::Log::logger"
1017 function, which can reduce typing, codesize and can reduce the 1032 function, which can reduce typing, codesize and can reduce the
1018 logging overhead enourmously. 1033 logging overhead enourmously.
1019 1034
1035 AnyEvent::fh_block $filehandle
1036 AnyEvent::fh_unblock $filehandle
1037 Sets blocking or non-blocking behaviour for the given filehandle.
1038
1020WHAT TO DO IN A MODULE 1039WHAT TO DO IN A MODULE
1021 As a module author, you should "use AnyEvent" and call AnyEvent methods 1040 As a module author, you should "use AnyEvent" and call AnyEvent methods
1022 freely, but you should not load a specific event module or rely on it. 1041 freely, but you should not load a specific event module or rely on it.
1023 1042
1024 Be careful when you create watchers in the module body - AnyEvent will 1043 Be careful when you create watchers in the module body - AnyEvent will
1082 modules come as part of AnyEvent, the others are available via CPAN (see 1101 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 1102 <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 1103 non-exhaustive list), and the list is heavily biased towards modules of
1085 the AnyEvent author himself :) 1104 the AnyEvent author himself :)
1086 1105
1087 AnyEvent::Util 1106 AnyEvent::Util (part of the AnyEvent distribution)
1088 Contains various utility functions that replace often-used blocking 1107 Contains various utility functions that replace often-used blocking
1089 functions such as "inet_aton" with event/callback-based versions. 1108 functions such as "inet_aton" with event/callback-based versions.
1090 1109
1091 AnyEvent::Socket 1110 AnyEvent::Socket (part of the AnyEvent distribution)
1092 Provides various utility functions for (internet protocol) sockets, 1111 Provides various utility functions for (internet protocol) sockets,
1093 addresses and name resolution. Also functions to create non-blocking 1112 addresses and name resolution. Also functions to create non-blocking
1094 tcp connections or tcp servers, with IPv6 and SRV record support and 1113 tcp connections or tcp servers, with IPv6 and SRV record support and
1095 more. 1114 more.
1096 1115
1097 AnyEvent::Handle 1116 AnyEvent::Handle (part of the AnyEvent distribution)
1098 Provide read and write buffers, manages watchers for reads and 1117 Provide read and write buffers, manages watchers for reads and
1099 writes, supports raw and formatted I/O, I/O queued and fully 1118 writes, supports raw and formatted I/O, I/O queued and fully
1100 transparent and non-blocking SSL/TLS (via AnyEvent::TLS). 1119 transparent and non-blocking SSL/TLS (via AnyEvent::TLS).
1101 1120
1102 AnyEvent::DNS 1121 AnyEvent::DNS (part of the AnyEvent distribution)
1103 Provides rich asynchronous DNS resolver capabilities. 1122 Provides rich asynchronous DNS resolver capabilities.
1104 1123
1105 AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD, 1124 AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD,
1106 AnyEvent::IGS, AnyEvent::FCP 1125 AnyEvent::IGS, AnyEvent::FCP
1107 Implement event-based interfaces to the protocols of the same name 1126 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 1127 (for the curious, IGS is the International Go Server and FCP is the
1109 Freenet Client Protocol). 1128 Freenet Client Protocol).
1110 1129
1111 AnyEvent::AIO 1130 AnyEvent::AIO (part of the AnyEvent distribution)
1112 Truly asynchronous (as opposed to non-blocking) I/O, should be in 1131 Truly asynchronous (as opposed to non-blocking) I/O, should be in
1113 the toolbox of every event programmer. AnyEvent::AIO transparently 1132 the toolbox of every event programmer. AnyEvent::AIO transparently
1114 fuses IO::AIO and AnyEvent together, giving AnyEvent access to 1133 fuses IO::AIO and AnyEvent together, giving AnyEvent access to
1115 event-based file I/O, and much more. 1134 event-based file I/O, and much more.
1135
1136 AnyEvent::Fork, AnyEvent::Fork::RPC, AnyEvent::Fork::Pool,
1137 AnyEvent::Fork::Remote
1138 These let you safely fork new subprocesses, either locally or
1139 remotely (e.g.v ia ssh), using some RPC protocol or not, without the
1140 limitations normally imposed by fork (AnyEvent works fine for
1141 example). Dynamically-resized worker pools are obviously included as
1142 well.
1143
1144 And they are quite tiny and fast as well - "abusing" AnyEvent::Fork
1145 just to exec external programs can easily beat using "fork" and
1146 "exec" (or even "system") in most programs.
1116 1147
1117 AnyEvent::Filesys::Notify 1148 AnyEvent::Filesys::Notify
1118 AnyEvent is good for non-blocking stuff, but it can't detect file or 1149 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 1150 path changes (e.g. "watch this directory for new files", "watch this
1120 file for changes"). The AnyEvent::Filesys::Notify module promises to 1151 file for changes"). The AnyEvent::Filesys::Notify module promises to
1122 and some weird, without doubt broken, stuff on OS X to monitor 1153 and some weird, without doubt broken, stuff on OS X to monitor
1123 files. It can fall back to blocking scans at regular intervals 1154 files. It can fall back to blocking scans at regular intervals
1124 transparently on other platforms, so it's about as portable as it 1155 transparently on other platforms, so it's about as portable as it
1125 gets. 1156 gets.
1126 1157
1127 (I haven't used it myself, but I haven't heard anybody complaining 1158 (I haven't used it myself, but it seems the biggest problem with it
1128 about it yet). 1159 is it quite bad performance).
1129 1160
1130 AnyEvent::DBI 1161 AnyEvent::DBI
1131 Executes DBI requests asynchronously in a proxy process for you, 1162 Executes DBI requests asynchronously in a proxy process for you,
1132 notifying you in an event-based way when the operation is finished. 1163 notifying you in an event-based way when the operation is finished.
1133
1134 AnyEvent::HTTPD
1135 A simple embedded webserver.
1136 1164
1137 AnyEvent::FastPing 1165 AnyEvent::FastPing
1138 The fastest ping in the west. 1166 The fastest ping in the west.
1139 1167
1140 Coro 1168 Coro
1214 This ensures that child processes will not see the "AE_" variables. 1242 This ensures that child processes will not see the "AE_" variables.
1215 1243
1216 The following environment variables are currently known to AnyEvent: 1244 The following environment variables are currently known to AnyEvent:
1217 1245
1218 "PERL_ANYEVENT_VERBOSE" 1246 "PERL_ANYEVENT_VERBOSE"
1219 By default, AnyEvent will only log messages with loglevel 3 1247 By default, AnyEvent will log messages with loglevel 4 ("error") or
1220 ("critical") or higher (see AnyEvent::Log). You can set this 1248 higher (see AnyEvent::Log). You can set this environment variable to
1221 environment variable to a numerical loglevel to make AnyEvent more 1249 a numerical loglevel to make AnyEvent more (or less) talkative.
1222 (or less) talkative.
1223 1250
1224 If you want to do more than just set the global logging level you 1251 If you want to do more than just set the global logging level you
1225 should have a look at "PERL_ANYEVENT_LOG", which allows much more 1252 should have a look at "PERL_ANYEVENT_LOG", which allows much more
1226 complex specifications. 1253 complex specifications.
1227 1254
1228 When set to 0 ("off"), then no messages whatsoever will be logged 1255 When set to 0 ("off"), then no messages whatsoever will be logged
1229 with the default logging settings. 1256 with everything else at defaults.
1230 1257
1231 When set to 5 or higher ("warn"), causes AnyEvent to warn about 1258 When set to 5 or higher ("warn"), AnyEvent warns about unexpected
1232 unexpected conditions, such as not being able to load the event 1259 conditions, such as not being able to load the event model specified
1233 model specified by "PERL_ANYEVENT_MODEL", or a guard callback 1260 by "PERL_ANYEVENT_MODEL", or a guard callback throwing an exception
1234 throwing an exception - this is the minimum recommended level. 1261 - this is the minimum recommended level for use during development.
1235 1262
1236 When set to 7 or higher (info), cause AnyEvent to report which event 1263 When set to 7 or higher (info), AnyEvent reports which event model
1237 model it chooses. 1264 it chooses.
1238 1265
1239 When set to 8 or higher (debug), then AnyEvent will report extra 1266 When set to 8 or higher (debug), then AnyEvent will report extra
1240 information on which optional modules it loads and how it implements 1267 information on which optional modules it loads and how it implements
1241 certain features. 1268 certain features.
1242 1269
1254 itself. 1281 itself.
1255 1282
1256 Note that specifying this environment variable causes the 1283 Note that specifying this environment variable causes the
1257 AnyEvent::Log module to be loaded, while "PERL_ANYEVENT_VERBOSE" 1284 AnyEvent::Log module to be loaded, while "PERL_ANYEVENT_VERBOSE"
1258 does not, so only using the latter saves a few hundred kB of memory 1285 does not, so only using the latter saves a few hundred kB of memory
1259 until the first message is being logged. 1286 unless a module explicitly needs the extra features of
1287 AnyEvent::Log.
1260 1288
1261 "PERL_ANYEVENT_STRICT" 1289 "PERL_ANYEVENT_STRICT"
1262 AnyEvent does not do much argument checking by default, as thorough 1290 AnyEvent does not do much argument checking by default, as thorough
1263 argument checking is very costly. Setting this variable to a true 1291 argument checking is very costly. Setting this variable to a true
1264 value will cause AnyEvent to load "AnyEvent::Strict" and then to 1292 value will cause AnyEvent to load "AnyEvent::Strict" and then to
1317 For example, to force the pure perl model (AnyEvent::Loop::Perl) you 1345 For example, to force the pure perl model (AnyEvent::Loop::Perl) you
1318 could start your program like this: 1346 could start your program like this:
1319 1347
1320 PERL_ANYEVENT_MODEL=Perl perl ... 1348 PERL_ANYEVENT_MODEL=Perl perl ...
1321 1349
1350 "PERL_ANYEVENT_IO_MODEL"
1351 The current file I/O model - see AnyEvent::IO for more info.
1352
1353 At the moment, only "Perl" (small, pure-perl, synchronous) and
1354 "IOAIO" (truly asynchronous) are supported. The default is "IOAIO"
1355 if AnyEvent::AIO can be loaded, otherwise it is "Perl".
1356
1322 "PERL_ANYEVENT_PROTOCOLS" 1357 "PERL_ANYEVENT_PROTOCOLS"
1323 Used by both AnyEvent::DNS and AnyEvent::Socket to determine 1358 Used by both AnyEvent::DNS and AnyEvent::Socket to determine
1324 preferences for IPv4 or IPv6. The default is unspecified (and might 1359 preferences for IPv4 or IPv6. The default is unspecified (and might
1325 change, or be the result of auto probing). 1360 change, or be the result of auto probing).
1326 1361
1329 mentioned will be used, and preference will be given to protocols 1364 mentioned will be used, and preference will be given to protocols
1330 mentioned earlier in the list. 1365 mentioned earlier in the list.
1331 1366
1332 This variable can effectively be used for denial-of-service attacks 1367 This variable can effectively be used for denial-of-service attacks
1333 against local programs (e.g. when setuid), although the impact is 1368 against local programs (e.g. when setuid), although the impact is
1334 likely small, as the program has to handle conenction and other 1369 likely small, as the program has to handle connection and other
1335 failures anyways. 1370 failures anyways.
1336 1371
1337 Examples: "PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6" - prefer IPv4 over 1372 Examples: "PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6" - prefer IPv4 over
1338 IPv6, but support both and try to use both. 1373 IPv6, but support both and try to use both.
1339 "PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to 1374 "PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to
1994 This module is part of perl since release 5.008. It will be used 2029 This module is part of perl since release 5.008. It will be used
1995 when the chosen event library does not come with a timing source of 2030 when the chosen event library does not come with a timing source of
1996 its own. The pure-perl event loop (AnyEvent::Loop) will additionally 2031 its own. The pure-perl event loop (AnyEvent::Loop) will additionally
1997 load it to try to use a monotonic clock for timing stability. 2032 load it to try to use a monotonic clock for timing stability.
1998 2033
2034 AnyEvent::AIO (and IO::AIO)
2035 The default implementation of AnyEvent::IO is to do I/O
2036 synchronously, stopping programs while they access the disk, which
2037 is fine for a lot of programs.
2038
2039 Installing AnyEvent::AIO (and its IO::AIO dependency) makes it
2040 switch to a true asynchronous implementation, so event processing
2041 can continue even while waiting for disk I/O.
2042
1999FORK 2043FORK
2000 Most event libraries are not fork-safe. The ones who are usually are 2044 Most event libraries are not fork-safe. The ones who are usually are
2001 because they rely on inefficient but fork-safe "select" or "poll" calls 2045 because they rely on inefficient but fork-safe "select" or "poll" calls
2002 - higher performance APIs such as BSD's kqueue or the dreaded Linux 2046 - higher performance APIs such as BSD's kqueue or the dreaded Linux
2003 epoll are usually badly thought-out hacks that are incompatible with 2047 epoll are usually badly thought-out hacks that are incompatible with
2010 usually happens when the first AnyEvent watcher is created, or the 2054 usually happens when the first AnyEvent watcher is created, or the
2011 library is loaded). 2055 library is loaded).
2012 2056
2013 If you have to fork, you must either do so *before* creating your first 2057 If you have to fork, you must either do so *before* creating your first
2014 watcher OR you must not use AnyEvent at all in the child OR you must do 2058 watcher OR you must not use AnyEvent at all in the child OR you must do
2015 something completely out of the scope of AnyEvent. 2059 something completely out of the scope of AnyEvent (see below).
2016 2060
2017 The problem of doing event processing in the parent *and* the child is 2061 The problem of doing event processing in the parent *and* the child is
2018 much more complicated: even for backends that *are* fork-aware or 2062 much more complicated: even for backends that *are* fork-aware or
2019 fork-safe, their behaviour is not usually what you want: fork clones all 2063 fork-safe, their behaviour is not usually what you want: fork clones all
2020 watchers, that means all timers, I/O watchers etc. are active in both 2064 watchers, that means all timers, I/O watchers etc. are active in both
2021 parent and child, which is almost never what you want. USing "exec" to 2065 parent and child, which is almost never what you want. Using "exec" to
2022 start worker children from some kind of manage rprocess is usually 2066 start worker children from some kind of manage prrocess is usually
2023 preferred, because it is much easier and cleaner, at the expense of 2067 preferred, because it is much easier and cleaner, at the expense of
2024 having to have another binary. 2068 having to have another binary.
2069
2070 In addition to logical problems with fork, there are also implementation
2071 problems. For example, on POSIX systems, you cannot fork at all in Perl
2072 code if a thread (I am talking of pthreads here) was ever created in the
2073 process, and this is just the tip of the iceberg. In general, using fork
2074 from Perl is difficult, and attempting to use fork without an exec to
2075 implement some kind of parallel processing is almost certainly doomed.
2076
2077 To safely fork and exec, you should use a module such as Proc::FastSpawn
2078 that let's you safely fork and exec new processes.
2079
2080 If you want to do multiprocessing using processes, you can look at the
2081 AnyEvent::Fork module (and some related modules such as
2082 AnyEvent::Fork::RPC, AnyEvent::Fork::Pool and AnyEvent::Fork::Remote).
2083 This module allows you to safely create subprocesses without any
2084 limitations - you can use X11 toolkits or AnyEvent in the children
2085 created by AnyEvent::Fork safely and without any special precautions.
2025 2086
2026SECURITY CONSIDERATIONS 2087SECURITY CONSIDERATIONS
2027 AnyEvent can be forced to load any event model via 2088 AnyEvent can be forced to load any event model via
2028 $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used 2089 $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used
2029 to execute arbitrary code or directly gain access, it can easily be used 2090 to execute arbitrary code or directly gain access, it can easily be used
2064 2125
2065 Development/Debugging: AnyEvent::Strict (stricter checking), 2126 Development/Debugging: AnyEvent::Strict (stricter checking),
2066 AnyEvent::Debug (interactive shell, watcher tracing). 2127 AnyEvent::Debug (interactive shell, watcher tracing).
2067 2128
2068 Supported event modules: AnyEvent::Loop, EV, EV::Glib, Glib::EV, Event, 2129 Supported event modules: AnyEvent::Loop, EV, EV::Glib, Glib::EV, Event,
2069 Glib::Event, Glib, Tk, Event::Lib, Qt, POE, FLTK. 2130 Glib::Event, Glib, Tk, Event::Lib, Qt, POE, FLTK, Cocoa::EventLoop, UV.
2070 2131
2071 Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event, 2132 Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event,
2072 AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl, 2133 AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl,
2073 AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE, 2134 AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE,
2074 AnyEvent::Impl::IOAsync, Anyevent::Impl::Irssi, AnyEvent::Impl::FLTK. 2135 AnyEvent::Impl::IOAsync, AnyEvent::Impl::Irssi, AnyEvent::Impl::FLTK,
2136 AnyEvent::Impl::Cocoa, AnyEvent::Impl::UV.
2075 2137
2076 Non-blocking handles, pipes, stream sockets, TCP clients and servers: 2138 Non-blocking handles, pipes, stream sockets, TCP clients and servers:
2077 AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS. 2139 AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS.
2078 2140
2141 Asynchronous File I/O: AnyEvent::IO.
2142
2079 Asynchronous DNS: AnyEvent::DNS. 2143 Asynchronous DNS: AnyEvent::DNS.
2080 2144
2081 Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event. 2145 Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event.
2082 2146
2083 Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::IRC, 2147 Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::IRC,
2084 AnyEvent::HTTP. 2148 AnyEvent::HTTP.
2085 2149
2086AUTHOR 2150AUTHOR
2087 Marc Lehmann <schmorp@schmorp.de> 2151 Marc Lehmann <schmorp@schmorp.de>
2088 http://home.schmorp.de/ 2152 http://anyevent.schmorp.de
2089 2153

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines