1 | NAME |
1 | NAME |
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 | |
7 | SYNOPSIS |
8 | SYNOPSIS |
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 |
… | |
… | |
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; |
… | |
… | |
807 | $bool = $cv->ready |
812 | $bool = $cv->ready |
808 | Returns true when the condition is "true", i.e. whether "send" or |
813 | Returns true when the condition is "true", i.e. whether "send" or |
809 | "croak" have been called. |
814 | "croak" have been called. |
810 | |
815 | |
811 | $cb = $cv->cb ($cb->($cv)) |
816 | $cb = $cv->cb ($cb->($cv)) |
812 | This is a mutator function that returns the callback set and |
817 | This is a mutator function that returns the callback set (or "undef" |
813 | optionally replaces it before doing so. |
818 | if not) and optionally replaces it before doing so. |
814 | |
819 | |
815 | The callback will be called when the condition becomes "true", i.e. |
820 | The callback will be called when the condition becomes "true", i.e. |
816 | when "send" or "croak" are called, with the only argument being the |
821 | when "send" or "croak" are called, with the only argument being the |
817 | condition variable itself. If the condition is already true, the |
822 | condition variable itself. If the condition is already true, the |
818 | callback is called immediately when it is set. Calling "recv" inside |
823 | callback is called immediately when it is set. Calling "recv" inside |
819 | the callback or at any later time is guaranteed not to block. |
824 | the callback or at any later time is guaranteed not to block. |
820 | |
825 | |
|
|
826 | Additionally, when the callback is invoked, it is also removed from |
|
|
827 | the condvar (reset to "undef"), so the condvar does not keep a |
|
|
828 | reference to the callback after invocation. |
|
|
829 | |
821 | SUPPORTED EVENT LOOPS/BACKENDS |
830 | SUPPORTED EVENT LOOPS/BACKENDS |
822 | The available backend classes are (every class has its own manpage): |
831 | The following backend classes are part of the AnyEvent distribution |
|
|
832 | (every class has its own manpage): |
823 | |
833 | |
824 | Backends that are autoprobed when no other event loop can be found. |
834 | Backends that are autoprobed when no other event loop can be found. |
825 | EV is the preferred backend when no other event loop seems to be in |
835 | EV is the preferred backend when no other event loop seems to be in |
826 | use. If EV is not installed, then AnyEvent will fall back to its own |
836 | use. If EV is not installed, then AnyEvent will fall back to its own |
827 | pure-perl implementation, which is available everywhere as it comes |
837 | pure-perl implementation, which is available everywhere as it comes |
… | |
… | |
839 | by the main program. |
849 | by the main program. |
840 | |
850 | |
841 | AnyEvent::Impl::Event based on Event, very stable, few glitches. |
851 | AnyEvent::Impl::Event based on Event, very stable, few glitches. |
842 | AnyEvent::Impl::Glib based on Glib, slow but very stable. |
852 | AnyEvent::Impl::Glib based on Glib, slow but very stable. |
843 | AnyEvent::Impl::Tk based on Tk, very broken. |
853 | AnyEvent::Impl::Tk based on Tk, very broken. |
|
|
854 | AnyEvent::Impl::UV based on UV, innovated square wheels. |
844 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
855 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
845 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
856 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
846 | AnyEvent::Impl::Irssi used when running within irssi. |
857 | AnyEvent::Impl::Irssi used when running within irssi. |
847 | AnyEvent::Impl::IOAsync based on IO::Async. |
858 | AnyEvent::Impl::IOAsync based on IO::Async. |
848 | AnyEvent::Impl::Cocoa based on Cocoa::EventLoop. |
859 | AnyEvent::Impl::Cocoa based on Cocoa::EventLoop. |
… | |
… | |
871 | |
882 | |
872 | AnyEvent knows about both Prima and Wx, however, and will try to |
883 | AnyEvent knows about both Prima and Wx, however, and will try to |
873 | load POE when detecting them, in the hope that POE will pick them |
884 | load POE when detecting them, in the hope that POE will pick them |
874 | up, in which case everything will be automatic. |
885 | up, in which case everything will be automatic. |
875 | |
886 | |
|
|
887 | Known event loops outside the AnyEvent distribution |
|
|
888 | The following event loops or programs support AnyEvent by providing |
|
|
889 | their own AnyEvent backend. They will be picked up automatically. |
|
|
890 | |
|
|
891 | urxvt::anyevent available to rxvt-unicode extensions |
|
|
892 | |
876 | GLOBAL VARIABLES AND FUNCTIONS |
893 | GLOBAL VARIABLES AND FUNCTIONS |
877 | These are not normally required to use AnyEvent, but can be useful to |
894 | These are not normally required to use AnyEvent, but can be useful to |
878 | write AnyEvent extension modules. |
895 | write AnyEvent extension modules. |
879 | |
896 | |
880 | $AnyEvent::MODEL |
897 | $AnyEvent::MODEL |
… | |
… | |
904 | $guard = AnyEvent::post_detect { BLOCK } |
921 | $guard = AnyEvent::post_detect { BLOCK } |
905 | Arranges for the code block to be executed as soon as the event |
922 | Arranges for the code block to be executed as soon as the event |
906 | model is autodetected (or immediately if that has already happened). |
923 | model is autodetected (or immediately if that has already happened). |
907 | |
924 | |
908 | The block will be executed *after* the actual backend has been |
925 | The block will be executed *after* the actual backend has been |
909 | detected ($AnyEvent::MODEL is set), but *before* any watchers have |
926 | detected ($AnyEvent::MODEL is set), so it is possible to do some |
910 | been created, so it is possible to e.g. patch @AnyEvent::ISA or do |
927 | initialisation only when AnyEvent is actually initialised - see the |
911 | other initialisations - see the sources of AnyEvent::Strict or |
|
|
912 | AnyEvent::AIO to see how this is used. |
928 | sources of AnyEvent::AIO to see how this is used. |
913 | |
929 | |
914 | The most common usage is to create some global watchers, without |
930 | The most common usage is to create some global watchers, without |
915 | forcing event module detection too early, for example, AnyEvent::AIO |
931 | forcing event module detection too early. For example, AnyEvent::AIO |
916 | creates and installs the global IO::AIO watcher in a "post_detect" |
932 | creates and installs the global IO::AIO watcher in a "post_detect" |
917 | block to avoid autodetecting the event module at load time. |
933 | block to avoid autodetecting the event module at load time. |
918 | |
934 | |
919 | If called in scalar or list context, then it creates and returns an |
935 | If called in scalar or list context, then it creates and returns an |
920 | object that automatically removes the callback again when it is |
936 | object that automatically removes the callback again when it is |
… | |
… | |
936 | # able to just C<undef $WATCHER> if the watcher causes them grief. |
952 | # able to just C<undef $WATCHER> if the watcher causes them grief. |
937 | |
953 | |
938 | $WATCHER ||= $guard; |
954 | $WATCHER ||= $guard; |
939 | |
955 | |
940 | @AnyEvent::post_detect |
956 | @AnyEvent::post_detect |
941 | If there are any code references in this array (you can "push" to it |
957 | This is a lower level interface then "AnyEvent::post_detect" (the |
942 | before or after loading AnyEvent), then they will be called directly |
958 | function). This variable is mainly useful for modules that can do |
|
|
959 | something useful when AnyEvent is used and thus want to know when it |
|
|
960 | is initialised, but do not need to even load it by default. This |
|
|
961 | array provides the means to hook into AnyEvent passively, without |
|
|
962 | loading it. |
|
|
963 | |
|
|
964 | Here is how it works: If there are any code references in this array |
|
|
965 | (you can "push" to it before or after loading AnyEvent), then they |
943 | after the event loop has been chosen. |
966 | will be called directly after the event loop has been chosen. |
944 | |
967 | |
945 | You should check $AnyEvent::MODEL before adding to this array, |
968 | You should check $AnyEvent::MODEL before adding to this array, |
946 | though: if it is defined then the event loop has already been |
969 | though: if it is defined then the event loop has already been |
947 | detected, and the array will be ignored. |
970 | detected, and the array will be ignored. |
948 | |
971 | |
949 | Best use "AnyEvent::post_detect { BLOCK }" when your application |
972 | Best use "AnyEvent::post_detect { BLOCK }" when your application |
950 | allows it, as it takes care of these details. |
973 | allows it, as it takes care of these details. |
951 | |
|
|
952 | This variable is mainly useful for modules that can do something |
|
|
953 | useful when AnyEvent is used and thus want to know when it is |
|
|
954 | initialised, but do not need to even load it by default. This array |
|
|
955 | provides the means to hook into AnyEvent passively, without loading |
|
|
956 | it. |
|
|
957 | |
974 | |
958 | Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used |
975 | Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used |
959 | together, you could put this into Coro (this is the actual code used |
976 | together, you could put this into Coro (this is the actual code used |
960 | by Coro to accomplish this): |
977 | by Coro to accomplish this): |
961 | |
978 | |
… | |
… | |
980 | To understand the usefulness of this function, consider a function |
997 | To understand the usefulness of this function, consider a function |
981 | that asynchronously does something for you and returns some |
998 | that asynchronously does something for you and returns some |
982 | transaction object or guard to let you cancel the operation. For |
999 | transaction object or guard to let you cancel the operation. For |
983 | example, "AnyEvent::Socket::tcp_connect": |
1000 | example, "AnyEvent::Socket::tcp_connect": |
984 | |
1001 | |
985 | # start a conenction attempt unless one is active |
1002 | # start a connection attempt unless one is active |
986 | $self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub { |
1003 | $self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub { |
987 | delete $self->{connect_guard}; |
1004 | delete $self->{connect_guard}; |
988 | ... |
1005 | ... |
989 | }; |
1006 | }; |
990 | |
1007 | |
… | |
… | |
1024 | If you want to sprinkle loads of logging calls around your code, |
1041 | If you want to sprinkle loads of logging calls around your code, |
1025 | consider creating a logger callback with the "AnyEvent::Log::logger" |
1042 | consider creating a logger callback with the "AnyEvent::Log::logger" |
1026 | function, which can reduce typing, codesize and can reduce the |
1043 | function, which can reduce typing, codesize and can reduce the |
1027 | logging overhead enourmously. |
1044 | logging overhead enourmously. |
1028 | |
1045 | |
|
|
1046 | AnyEvent::fh_block $filehandle |
|
|
1047 | AnyEvent::fh_unblock $filehandle |
|
|
1048 | Sets blocking or non-blocking behaviour for the given filehandle. |
|
|
1049 | |
1029 | WHAT TO DO IN A MODULE |
1050 | WHAT TO DO IN A MODULE |
1030 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
1051 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
1031 | freely, but you should not load a specific event module or rely on it. |
1052 | freely, but you should not load a specific event module or rely on it. |
1032 | |
1053 | |
1033 | Be careful when you create watchers in the module body - AnyEvent will |
1054 | Be careful when you create watchers in the module body - AnyEvent will |
… | |
… | |
1120 | AnyEvent::AIO (part of the AnyEvent distribution) |
1141 | AnyEvent::AIO (part of the AnyEvent distribution) |
1121 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1142 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1122 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1143 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1123 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1144 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1124 | event-based file I/O, and much more. |
1145 | event-based file I/O, and much more. |
|
|
1146 | |
|
|
1147 | AnyEvent::Fork, AnyEvent::Fork::RPC, AnyEvent::Fork::Pool, |
|
|
1148 | AnyEvent::Fork::Remote |
|
|
1149 | These let you safely fork new subprocesses, either locally or |
|
|
1150 | remotely (e.g.v ia ssh), using some RPC protocol or not, without the |
|
|
1151 | limitations normally imposed by fork (AnyEvent works fine for |
|
|
1152 | example). Dynamically-resized worker pools are obviously included as |
|
|
1153 | well. |
|
|
1154 | |
|
|
1155 | And they are quite tiny and fast as well - "abusing" AnyEvent::Fork |
|
|
1156 | just to exec external programs can easily beat using "fork" and |
|
|
1157 | "exec" (or even "system") in most programs. |
1125 | |
1158 | |
1126 | AnyEvent::Filesys::Notify |
1159 | AnyEvent::Filesys::Notify |
1127 | AnyEvent is good for non-blocking stuff, but it can't detect file or |
1160 | AnyEvent is good for non-blocking stuff, but it can't detect file or |
1128 | path changes (e.g. "watch this directory for new files", "watch this |
1161 | path changes (e.g. "watch this directory for new files", "watch this |
1129 | file for changes"). The AnyEvent::Filesys::Notify module promises to |
1162 | file for changes"). The AnyEvent::Filesys::Notify module promises to |
… | |
… | |
1131 | and some weird, without doubt broken, stuff on OS X to monitor |
1164 | and some weird, without doubt broken, stuff on OS X to monitor |
1132 | files. It can fall back to blocking scans at regular intervals |
1165 | files. It can fall back to blocking scans at regular intervals |
1133 | transparently on other platforms, so it's about as portable as it |
1166 | transparently on other platforms, so it's about as portable as it |
1134 | gets. |
1167 | gets. |
1135 | |
1168 | |
1136 | (I haven't used it myself, but I haven't heard anybody complaining |
1169 | (I haven't used it myself, but it seems the biggest problem with it |
1137 | about it yet). |
1170 | is it quite bad performance). |
1138 | |
1171 | |
1139 | AnyEvent::DBI |
1172 | AnyEvent::DBI |
1140 | Executes DBI requests asynchronously in a proxy process for you, |
1173 | Executes DBI requests asynchronously in a proxy process for you, |
1141 | notifying you in an event-based way when the operation is finished. |
1174 | notifying you in an event-based way when the operation is finished. |
1142 | |
|
|
1143 | AnyEvent::HTTPD |
|
|
1144 | A simple embedded webserver. |
|
|
1145 | |
1175 | |
1146 | AnyEvent::FastPing |
1176 | AnyEvent::FastPing |
1147 | The fastest ping in the west. |
1177 | The fastest ping in the west. |
1148 | |
1178 | |
1149 | Coro |
1179 | Coro |
… | |
… | |
1345 | mentioned will be used, and preference will be given to protocols |
1375 | mentioned will be used, and preference will be given to protocols |
1346 | mentioned earlier in the list. |
1376 | mentioned earlier in the list. |
1347 | |
1377 | |
1348 | This variable can effectively be used for denial-of-service attacks |
1378 | This variable can effectively be used for denial-of-service attacks |
1349 | against local programs (e.g. when setuid), although the impact is |
1379 | against local programs (e.g. when setuid), although the impact is |
1350 | likely small, as the program has to handle conenction and other |
1380 | likely small, as the program has to handle connection and other |
1351 | failures anyways. |
1381 | failures anyways. |
1352 | |
1382 | |
1353 | Examples: "PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6" - prefer IPv4 over |
1383 | Examples: "PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6" - prefer IPv4 over |
1354 | IPv6, but support both and try to use both. |
1384 | IPv6, but support both and try to use both. |
1355 | "PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to |
1385 | "PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to |
… | |
… | |
1589 | my $txn = shift; |
1619 | my $txn = shift; |
1590 | my $data = $txn->result; |
1620 | my $data = $txn->result; |
1591 | ... |
1621 | ... |
1592 | }); |
1622 | }); |
1593 | |
1623 | |
1594 | EV::loop; |
1624 | EV::run; |
1595 | |
1625 | |
1596 | 3b. The module user could use AnyEvent, too: |
1626 | 3b. The module user could use AnyEvent, too: |
1597 | |
1627 | |
1598 | use AnyEvent; |
1628 | use AnyEvent; |
1599 | |
1629 | |
… | |
… | |
2035 | usually happens when the first AnyEvent watcher is created, or the |
2065 | usually happens when the first AnyEvent watcher is created, or the |
2036 | library is loaded). |
2066 | library is loaded). |
2037 | |
2067 | |
2038 | If you have to fork, you must either do so *before* creating your first |
2068 | If you have to fork, you must either do so *before* creating your first |
2039 | watcher OR you must not use AnyEvent at all in the child OR you must do |
2069 | watcher OR you must not use AnyEvent at all in the child OR you must do |
2040 | something completely out of the scope of AnyEvent. |
2070 | something completely out of the scope of AnyEvent (see below). |
2041 | |
2071 | |
2042 | The problem of doing event processing in the parent *and* the child is |
2072 | The problem of doing event processing in the parent *and* the child is |
2043 | much more complicated: even for backends that *are* fork-aware or |
2073 | much more complicated: even for backends that *are* fork-aware or |
2044 | fork-safe, their behaviour is not usually what you want: fork clones all |
2074 | fork-safe, their behaviour is not usually what you want: fork clones all |
2045 | watchers, that means all timers, I/O watchers etc. are active in both |
2075 | watchers, that means all timers, I/O watchers etc. are active in both |
2046 | parent and child, which is almost never what you want. USing "exec" to |
2076 | parent and child, which is almost never what you want. Using "exec" to |
2047 | start worker children from some kind of manage rprocess is usually |
2077 | start worker children from some kind of manage prrocess is usually |
2048 | preferred, because it is much easier and cleaner, at the expense of |
2078 | preferred, because it is much easier and cleaner, at the expense of |
2049 | having to have another binary. |
2079 | having to have another binary. |
|
|
2080 | |
|
|
2081 | In addition to logical problems with fork, there are also implementation |
|
|
2082 | problems. For example, on POSIX systems, you cannot fork at all in Perl |
|
|
2083 | code if a thread (I am talking of pthreads here) was ever created in the |
|
|
2084 | process, and this is just the tip of the iceberg. In general, using fork |
|
|
2085 | from Perl is difficult, and attempting to use fork without an exec to |
|
|
2086 | implement some kind of parallel processing is almost certainly doomed. |
|
|
2087 | |
|
|
2088 | To safely fork and exec, you should use a module such as Proc::FastSpawn |
|
|
2089 | that let's you safely fork and exec new processes. |
|
|
2090 | |
|
|
2091 | If you want to do multiprocessing using processes, you can look at the |
|
|
2092 | AnyEvent::Fork module (and some related modules such as |
|
|
2093 | AnyEvent::Fork::RPC, AnyEvent::Fork::Pool and AnyEvent::Fork::Remote). |
|
|
2094 | This module allows you to safely create subprocesses without any |
|
|
2095 | limitations - you can use X11 toolkits or AnyEvent in the children |
|
|
2096 | created by AnyEvent::Fork safely and without any special precautions. |
2050 | |
2097 | |
2051 | SECURITY CONSIDERATIONS |
2098 | SECURITY CONSIDERATIONS |
2052 | AnyEvent can be forced to load any event model via |
2099 | AnyEvent can be forced to load any event model via |
2053 | $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used |
2100 | $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used |
2054 | to execute arbitrary code or directly gain access, it can easily be used |
2101 | to execute arbitrary code or directly gain access, it can easily be used |
… | |
… | |
2089 | |
2136 | |
2090 | Development/Debugging: AnyEvent::Strict (stricter checking), |
2137 | Development/Debugging: AnyEvent::Strict (stricter checking), |
2091 | AnyEvent::Debug (interactive shell, watcher tracing). |
2138 | AnyEvent::Debug (interactive shell, watcher tracing). |
2092 | |
2139 | |
2093 | Supported event modules: AnyEvent::Loop, EV, EV::Glib, Glib::EV, Event, |
2140 | Supported event modules: AnyEvent::Loop, EV, EV::Glib, Glib::EV, Event, |
2094 | Glib::Event, Glib, Tk, Event::Lib, Qt, POE, FLTK. |
2141 | Glib::Event, Glib, Tk, Event::Lib, Qt, POE, FLTK, Cocoa::EventLoop, UV. |
2095 | |
2142 | |
2096 | Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event, |
2143 | Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event, |
2097 | AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl, |
2144 | AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl, |
2098 | AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE, |
2145 | AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE, |
2099 | AnyEvent::Impl::IOAsync, Anyevent::Impl::Irssi, AnyEvent::Impl::FLTK. |
2146 | AnyEvent::Impl::IOAsync, AnyEvent::Impl::Irssi, AnyEvent::Impl::FLTK, |
|
|
2147 | AnyEvent::Impl::Cocoa, AnyEvent::Impl::UV. |
2100 | |
2148 | |
2101 | Non-blocking handles, pipes, stream sockets, TCP clients and servers: |
2149 | Non-blocking handles, pipes, stream sockets, TCP clients and servers: |
2102 | AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS. |
2150 | AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS. |
2103 | |
2151 | |
2104 | Asynchronous File I/O: AnyEvent::IO. |
2152 | Asynchronous File I/O: AnyEvent::IO. |