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

Comparing AnyEvent/README (file contents):
Revision 1.63 by root, Wed Oct 13 19:49:46 2010 UTC vs.
Revision 1.66 by root, Sun Aug 21 03:02:32 2011 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, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async,
5 Qt and POE are various supported event loops/environments. 5 Qt, FLTK and POE are various supported event loops/environments.
6 6
7SYNOPSIS 7SYNOPSIS
8 use AnyEvent; 8 use AnyEvent;
9 9
10 # if you prefer function calls, look at the AE manpage for 10 # if you prefer function calls, look at the AE manpage for
… …
80 that isn't them. What's worse, all the potential users of your module 80 that isn't them. What's worse, all the potential users of your module
81 are *also* forced to use the same event loop you use. 81 are *also* forced to use the same event loop you use.
82 82
83 AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works 83 AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
84 fine. AnyEvent + Tk works fine etc. etc. but none of these work together 84 fine. AnyEvent + Tk works fine etc. etc. but none of these work together
85 with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if your 85 with the rest: POE + EV? No go. Tk + Event? No go. Again: if your module
86 module uses one of those, every user of your module has to use it, too. 86 uses one of those, every user of your module has to use it, too. But if
87 But if your module uses AnyEvent, it works transparently with all event 87 your module uses AnyEvent, it works transparently with all event models
88 models it supports (including stuff like IO::Async, as long as those use 88 it supports (including stuff like IO::Async, as long as those use one of
89 one of the supported event loops. It is easy to add new event loops to 89 the supported event loops. It is easy to add new event loops to
90 AnyEvent, too, so it is future-proof). 90 AnyEvent, too, so it is future-proof).
91 91
92 In addition to being free of having to use *the one and only true event 92 In addition to being free of having to use *the one and only true event
93 model*, AnyEvent also is free of bloat and policy: with POE or similar 93 model*, AnyEvent also is free of bloat and policy: with POE or similar
94 modules, you get an enormous amount of code and strict rules you have to 94 modules, you get an enormous amount of code and strict rules you have to
… …
115 The interface itself is vaguely similar, but not identical to the Event 115 The interface itself is vaguely similar, but not identical to the Event
116 module. 116 module.
117 117
118 During the first call of any watcher-creation method, the module tries 118 During the first call of any watcher-creation method, the module tries
119 to detect the currently loaded event loop by probing whether one of the 119 to detect the currently loaded event loop by probing whether one of the
120 following modules is already loaded: EV, AnyEvent::Impl::Perl, Event, 120 following modules is already loaded: EV, AnyEvent::Loop, Event, Glib,
121 Glib, Tk, Event::Lib, Qt, POE. The first one found is used. If none are 121 Tk, Event::Lib, Qt, POE. The first one found is used. If none are
122 detected, the module tries to load the first four modules in the order 122 detected, the module tries to load the first four modules in the order
123 given; but note that if EV is not available, the pure-perl 123 given; but note that if EV is not available, the pure-perl
124 AnyEvent::Impl::Perl should always work, so the other two are not 124 AnyEvent::Loop should always work, so the other two are not normally
125 normally tried. 125 tried.
126 126
127 Because AnyEvent first checks for modules that are already loaded, 127 Because AnyEvent first checks for modules that are already loaded,
128 loading an event model explicitly before first using AnyEvent will 128 loading an event model explicitly before first using AnyEvent will
129 likely make that model the default. For example: 129 likely make that model the default. For example:
130 130
… …
136 The *likely* means that, if any module loads another event model and 136 The *likely* means that, if any module loads another event model and
137 starts using it, all bets are off - this case should be very rare 137 starts using it, all bets are off - this case should be very rare
138 though, as very few modules hardcode event loops without announcing this 138 though, as very few modules hardcode event loops without announcing this
139 very loudly. 139 very loudly.
140 140
141 The pure-perl implementation of AnyEvent is called 141 The pure-perl implementation of AnyEvent is called "AnyEvent::Loop".
142 "AnyEvent::Impl::Perl". Like other event modules you can load it 142 Like other event modules you can load it explicitly and enjoy the high
143 explicitly and enjoy the high availability of that event loop :) 143 availability of that event loop :)
144 144
145WATCHERS 145WATCHERS
146 AnyEvent has the central concept of a *watcher*, which is an object that 146 AnyEvent has the central concept of a *watcher*, which is an object that
147 stores relevant data for each kind of event you are waiting for, such as 147 stores relevant data for each kind of event you are waiting for, such as
148 the callback to call, the file handle to watch, etc. 148 the callback to call, the file handle to watch, etc.
… …
347 can get whatever behaviour you want with any event loop, by taking 347 can get whatever behaviour you want with any event loop, by taking
348 the difference between "AnyEvent->time" and "AnyEvent->now" into 348 the difference between "AnyEvent->time" and "AnyEvent->now" into
349 account. 349 account.
350 350
351 AnyEvent->now_update 351 AnyEvent->now_update
352 Some event loops (such as EV or AnyEvent::Impl::Perl) cache the 352 Some event loops (such as EV or AnyEvent::Loop) cache the current
353 current time for each loop iteration (see the discussion of 353 time for each loop iteration (see the discussion of AnyEvent->now,
354 AnyEvent->now, above). 354 above).
355 355
356 When a callback runs for a long time (or when the process sleeps), 356 When a callback runs for a long time (or when the process sleeps),
357 then this "current" time will differ substantially from the real 357 then this "current" time will differ substantially from the real
358 time, which might affect timers and time-outs. 358 time, which might affect timers and time-outs.
359 359
… …
466 This means you cannot create a child watcher as the very first thing in 466 This means you cannot create a child watcher as the very first thing in
467 an AnyEvent program, you *have* to create at least one watcher before 467 an AnyEvent program, you *have* to create at least one watcher before
468 you "fork" the child (alternatively, you can call "AnyEvent::detect"). 468 you "fork" the child (alternatively, you can call "AnyEvent::detect").
469 469
470 As most event loops do not support waiting for child events, they will 470 As most event loops do not support waiting for child events, they will
471 be emulated by AnyEvent in most cases, in which the latency and race 471 be emulated by AnyEvent in most cases, in which case the latency and
472 problems mentioned in the description of signal watchers apply. 472 race problems mentioned in the description of signal watchers apply.
473 473
474 Example: fork a process and wait for it 474 Example: fork a process and wait for it
475 475
476 my $done = AnyEvent->condvar; 476 my $done = AnyEvent->condvar;
477 477
… …
821 use. If EV is not installed, then AnyEvent will fall back to its own 821 use. If EV is not installed, then AnyEvent will fall back to its own
822 pure-perl implementation, which is available everywhere as it comes 822 pure-perl implementation, which is available everywhere as it comes
823 with AnyEvent itself. 823 with AnyEvent itself.
824 824
825 AnyEvent::Impl::EV based on EV (interface to libev, best choice). 825 AnyEvent::Impl::EV based on EV (interface to libev, best choice).
826 AnyEvent::Impl::Perl pure-perl implementation, fast and portable. 826 AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
827 827
828 Backends that are transparently being picked up when they are used. 828 Backends that are transparently being picked up when they are used.
829 These will be used if they are already loaded when the first watcher 829 These will be used if they are already loaded when the first watcher
830 is created, in which case it is assumed that the application is 830 is created, in which case it is assumed that the application is
831 using them. This means that AnyEvent will automatically pick the 831 using them. This means that AnyEvent will automatically pick the
… …
837 AnyEvent::Impl::Glib based on Glib, slow but very stable. 837 AnyEvent::Impl::Glib based on Glib, slow but very stable.
838 AnyEvent::Impl::Tk based on Tk, very broken. 838 AnyEvent::Impl::Tk based on Tk, very broken.
839 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. 839 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
840 AnyEvent::Impl::POE based on POE, very slow, some limitations. 840 AnyEvent::Impl::POE based on POE, very slow, some limitations.
841 AnyEvent::Impl::Irssi used when running within irssi. 841 AnyEvent::Impl::Irssi used when running within irssi.
842 AnyEvent::Impl::IOAsync based on IO::Async.
843 AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
844 AnyEvent::Impl::FLTK2 based on FLTK (fltk 2 binding).
842 845
843 Backends with special needs. 846 Backends with special needs.
844 Qt requires the Qt::Application to be instantiated first, but will 847 Qt requires the Qt::Application to be instantiated first, but will
845 otherwise be picked up automatically. As long as the main program 848 otherwise be picked up automatically. As long as the main program
846 instantiates the application before any AnyEvent watchers are 849 instantiates the application before any AnyEvent watchers are
847 created, everything should just work. 850 created, everything should just work.
848 851
849 AnyEvent::Impl::Qt based on Qt. 852 AnyEvent::Impl::Qt based on Qt.
850
851 Support for IO::Async can only be partial, as it is too broken and
852 architecturally limited to even support the AnyEvent API. It also is
853 the only event loop that needs the loop to be set explicitly, so it
854 can only be used by a main program knowing about AnyEvent. See
855 AnyEvent::Impl::IOAsync for the gory details.
856
857 AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
858 853
859 Event loops that are indirectly supported via other backends. 854 Event loops that are indirectly supported via other backends.
860 Some event loops can be supported via other modules: 855 Some event loops can be supported via other modules:
861 856
862 There is no direct support for WxWidgets (Wx) or Prima. 857 There is no direct support for WxWidgets (Wx) or Prima.
… …
891 Returns $AnyEvent::MODEL, forcing autodetection of the event model 886 Returns $AnyEvent::MODEL, forcing autodetection of the event model
892 if necessary. You should only call this function right before you 887 if necessary. You should only call this function right before you
893 would have created an AnyEvent watcher anyway, that is, as late as 888 would have created an AnyEvent watcher anyway, that is, as late as
894 possible at runtime, and not e.g. during initialisation of your 889 possible at runtime, and not e.g. during initialisation of your
895 module. 890 module.
891
892 The effect of calling this function is as if a watcher had been
893 created (specifically, actions that happen "when the first watcher
894 is created" happen when calling detetc as well).
896 895
897 If you need to do some initialisation before AnyEvent watchers are 896 If you need to do some initialisation before AnyEvent watchers are
898 created, use "post_detect". 897 created, use "post_detect".
899 898
900 $guard = AnyEvent::post_detect { BLOCK } 899 $guard = AnyEvent::post_detect { BLOCK }
… …
962 # AnyEvent not yet initialised, so make sure to load Coro::AnyEvent 961 # AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
963 # as soon as it is 962 # as soon as it is
964 push @AnyEvent::post_detect, sub { require Coro::AnyEvent }; 963 push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
965 } 964 }
966 965
966 AnyEvent::postpone { BLOCK }
967 Arranges for the block to be executed as soon as possible, but not
968 before the call itself returns. In practise, the block will be
969 executed just before the event loop polls for new events, or shortly
970 afterwards.
971
972 This function never returns anything (to make the "return postpone {
973 ... }" idiom more useful.
974
975 To understand the usefulness of this function, consider a function
976 that asynchronously does something for you and returns some
977 transaction object or guard to let you cancel the operation. For
978 example, "AnyEvent::Socket::tcp_connect":
979
980 # start a conenction attempt unless one is active
981 $self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
982 delete $self->{connect_guard};
983 ...
984 };
985
986 Imagine that this function could instantly call the callback, for
987 example, because it detects an obvious error such as a negative port
988 number. Invoking the callback before the function returns causes
989 problems however: the callback will be called and will try to delete
990 the guard object. But since the function hasn't returned yet, there
991 is nothing to delete. When the function eventually returns it will
992 assign the guard object to "$self->{connect_guard}", where it will
993 likely never be deleted, so the program thinks it is still trying to
994 connect.
995
996 This is where "AnyEvent::postpone" should be used. Instead of
997 calling the callback directly on error:
998
999 $cb->(undef), return # signal error to callback, BAD!
1000 if $some_error_condition;
1001
1002 It should use "postpone":
1003
1004 AnyEvent::postpone { $cb->(undef) }, return # signal error to callback, later
1005 if $some_error_condition;
1006
1007 AnyEvent::log $level, $msg[, @args]
1008 Log the given $msg at the given $level.
1009
1010 Loads AnyEvent::Log on first use and calls "AnyEvent::Log::log" -
1011 consequently, look at the AnyEvent::Log documentation for details.
1012
1013 If you want to sprinkle loads of logging calls around your code,
1014 consider creating a logger callback with the "AnyEvent::Log::logger"
1015 function.
1016
967WHAT TO DO IN A MODULE 1017WHAT TO DO IN A MODULE
968 As a module author, you should "use AnyEvent" and call AnyEvent methods 1018 As a module author, you should "use AnyEvent" and call AnyEvent methods
969 freely, but you should not load a specific event module or rely on it. 1019 freely, but you should not load a specific event module or rely on it.
970 1020
971 Be careful when you create watchers in the module body - AnyEvent will 1021 Be careful when you create watchers in the module body - AnyEvent will
… …
1001 will decide on the event model to use as soon as it creates watchers, 1051 will decide on the event model to use as soon as it creates watchers,
1002 and it might choose the wrong one unless you load the correct one 1052 and it might choose the wrong one unless you load the correct one
1003 yourself. 1053 yourself.
1004 1054
1005 You can chose to use a pure-perl implementation by loading the 1055 You can chose to use a pure-perl implementation by loading the
1006 "AnyEvent::Impl::Perl" module, which gives you similar behaviour 1056 "AnyEvent::Loop" module, which gives you similar behaviour everywhere,
1007 everywhere, but letting AnyEvent chose the model is generally better. 1057 but letting AnyEvent chose the model is generally better.
1008 1058
1009 MAINLOOP EMULATION 1059 MAINLOOP EMULATION
1010 Sometimes (often for short test scripts, or even standalone programs who 1060 Sometimes (often for short test scripts, or even standalone programs who
1011 only want to use AnyEvent), you do not want to run a specific event 1061 only want to use AnyEvent), you do not want to run a specific event
1012 loop. 1062 loop.
… …
1024 1074
1025OTHER MODULES 1075OTHER MODULES
1026 The following is a non-exhaustive list of additional modules that use 1076 The following is a non-exhaustive list of additional modules that use
1027 AnyEvent as a client and can therefore be mixed easily with other 1077 AnyEvent as a client and can therefore be mixed easily with other
1028 AnyEvent modules and other event loops in the same program. Some of the 1078 AnyEvent modules and other event loops in the same program. Some of the
1029 modules come as part of AnyEvent, the others are available via CPAN. 1079 modules come as part of AnyEvent, the others are available via CPAN (see
1080 <http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for a longer
1081 non-exhaustive list), and the list is heavily biased towards modules of
1082 the AnyEvent author himself :)
1030 1083
1031 AnyEvent::Util 1084 AnyEvent::Util
1032 Contains various utility functions that replace often-used blocking 1085 Contains various utility functions that replace often-used blocking
1033 functions such as "inet_aton" with event/callback-based versions. 1086 functions such as "inet_aton" with event/callback-based versions.
1034 1087
… …
1122 "PERL_ANYEVENT_VERBOSE" 1175 "PERL_ANYEVENT_VERBOSE"
1123 By default, AnyEvent will be completely silent except in fatal 1176 By default, AnyEvent will be completely silent except in fatal
1124 conditions. You can set this environment variable to make AnyEvent 1177 conditions. You can set this environment variable to make AnyEvent
1125 more talkative. 1178 more talkative.
1126 1179
1127 When set to 1 or higher, causes AnyEvent to warn about unexpected 1180 When set to 5 or higher, causes AnyEvent to warn about unexpected
1128 conditions, such as not being able to load the event model specified 1181 conditions, such as not being able to load the event model specified
1129 by "PERL_ANYEVENT_MODEL". 1182 by "PERL_ANYEVENT_MODEL".
1130 1183
1131 When set to 2 or higher, cause AnyEvent to report to STDERR which 1184 When set to 7 or higher, cause AnyEvent to report to STDERR which
1132 event model it chooses. 1185 event model it chooses.
1133 1186
1134 When set to 8 or higher, then AnyEvent will report extra information 1187 When set to 8 or higher, then AnyEvent will report extra information
1135 on which optional modules it loads and how it implements certain 1188 on which optional modules it loads and how it implements certain
1136 features. 1189 features.
… …
1147 Unlike "use strict" (or its modern cousin, "use common::sense", it 1200 Unlike "use strict" (or its modern cousin, "use common::sense", it
1148 is definitely recommended to keep it off in production. Keeping 1201 is definitely recommended to keep it off in production. Keeping
1149 "PERL_ANYEVENT_STRICT=1" in your environment while developing 1202 "PERL_ANYEVENT_STRICT=1" in your environment while developing
1150 programs can be very useful, however. 1203 programs can be very useful, however.
1151 1204
1205 "PERL_ANYEVENT_DEBUG_SHELL"
1206 If this env variable is set, then its contents will be interpreted
1207 by "AnyEvent::Socket::parse_hostport" (after replacing every
1208 occurance of $$ by the process pid) and an "AnyEvent::Debug::shell"
1209 is bound on that port. The shell object is saved in
1210 $AnyEvent::Debug::SHELL.
1211
1212 This takes place when the first watcher is created.
1213
1214 For example, to bind a debug shell on a unix domain socket in
1215 /tmp/debug<pid>.sock, you could use this:
1216
1217 PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog
1218
1219 Note that creating sockets in /tmp is very unsafe on multiuser
1220 systems.
1221
1222 "PERL_ANYEVENT_DEBUG_WRAP"
1223 Can be set to 0, 1 or 2 and enables wrapping of all watchers for
1224 debugging purposes. See "AnyEvent::Debug::wrap" for details.
1225
1152 "PERL_ANYEVENT_MODEL" 1226 "PERL_ANYEVENT_MODEL"
1153 This can be used to specify the event model to be used by AnyEvent, 1227 This can be used to specify the event model to be used by AnyEvent,
1154 before auto detection and -probing kicks in. It must be a string 1228 before auto detection and -probing kicks in.
1155 consisting entirely of ASCII letters. The string "AnyEvent::Impl::" 1229
1156 gets prepended and the resulting module name is loaded and if the 1230 It normally is a string consisting entirely of ASCII letters (e.g.
1157 load was successful, used as event model. If it fails to load 1231 "EV" or "IOAsync"). The string "AnyEvent::Impl::" gets prepended and
1232 the resulting module name is loaded and - if the load was successful
1233 - used as event model backend. If it fails to load then AnyEvent
1158 AnyEvent will proceed with auto detection and -probing. 1234 will proceed with auto detection and -probing.
1159 1235
1160 This functionality might change in future versions. 1236 If the string ends with "::" instead (e.g. "AnyEvent::Impl::EV::")
1237 then nothing gets prepended and the module name is used as-is (hint:
1238 "::" at the end of a string designates a module name and quotes it
1239 appropriately).
1161 1240
1162 For example, to force the pure perl model (AnyEvent::Impl::Perl) you 1241 For example, to force the pure perl model (AnyEvent::Loop::Perl) you
1163 could start your program like this: 1242 could start your program like this:
1164 1243
1165 PERL_ANYEVENT_MODEL=Perl perl ... 1244 PERL_ANYEVENT_MODEL=Perl perl ...
1166 1245
1167 "PERL_ANYEVENT_PROTOCOLS" 1246 "PERL_ANYEVENT_PROTOCOLS"
… …
1540 when used without AnyEvent), but most event loops have acceptable 1619 when used without AnyEvent), but most event loops have acceptable
1541 performance with or without AnyEvent. 1620 performance with or without AnyEvent.
1542 1621
1543 * The overhead AnyEvent adds is usually much smaller than the overhead 1622 * The overhead AnyEvent adds is usually much smaller than the overhead
1544 of the actual event loop, only with extremely fast event loops such 1623 of the actual event loop, only with extremely fast event loops such
1545 as EV adds AnyEvent significant overhead. 1624 as EV does AnyEvent add significant overhead.
1546 1625
1547 * You should avoid POE like the plague if you want performance or 1626 * You should avoid POE like the plague if you want performance or
1548 reasonable memory usage. 1627 reasonable memory usage.
1549 1628
1550 BENCHMARKING THE LARGE SERVER CASE 1629 BENCHMARKING THE LARGE SERVER CASE
… …
1810 the help of AnyEvent::TLS), gains the ability to do TLS/SSL. 1889 the help of AnyEvent::TLS), gains the ability to do TLS/SSL.
1811 1890
1812 Time::HiRes 1891 Time::HiRes
1813 This module is part of perl since release 5.008. It will be used 1892 This module is part of perl since release 5.008. It will be used
1814 when the chosen event library does not come with a timing source of 1893 when the chosen event library does not come with a timing source of
1815 its own. The pure-perl event loop (AnyEvent::Impl::Perl) will 1894 its own. The pure-perl event loop (AnyEvent::Loop) will additionally
1816 additionally use it to try to use a monotonic clock for timing 1895 load it to try to use a monotonic clock for timing stability.
1817 stability.
1818 1896
1819FORK 1897FORK
1820 Most event libraries are not fork-safe. The ones who are usually are 1898 Most event libraries are not fork-safe. The ones who are usually are
1821 because they rely on inefficient but fork-safe "select" or "poll" calls 1899 because they rely on inefficient but fork-safe "select" or "poll" calls
1822 - higher performance APIs such as BSD's kqueue or the dreaded Linux 1900 - higher performance APIs such as BSD's kqueue or the dreaded Linux
… …
1877SEE ALSO 1955SEE ALSO
1878 Tutorial/Introduction: AnyEvent::Intro. 1956 Tutorial/Introduction: AnyEvent::Intro.
1879 1957
1880 FAQ: AnyEvent::FAQ. 1958 FAQ: AnyEvent::FAQ.
1881 1959
1882 Utility functions: AnyEvent::Util. 1960 Utility functions: AnyEvent::Util (misc. grab-bag), AnyEvent::Log
1961 (simply logging).
1883 1962
1884 Event modules: EV, EV::Glib, Glib::EV, Event, Glib::Event, Glib, Tk, 1963 Development/Debugging: AnyEvent::Strict (stricter checking),
1885 Event::Lib, Qt, POE. 1964 AnyEvent::Debug (interactive shell, watcher tracing).
1965
1966 Supported event modules: AnyEvent::Loop, EV, EV::Glib, Glib::EV, Event,
1967 Glib::Event, Glib, Tk, Event::Lib, Qt, POE, FLTK.
1886 1968
1887 Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event, 1969 Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event,
1888 AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl, 1970 AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl,
1889 AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE, 1971 AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE,
1890 AnyEvent::Impl::IOAsync, Anyevent::Impl::Irssi. 1972 AnyEvent::Impl::IOAsync, Anyevent::Impl::Irssi, AnyEvent::Impl::FLTK.
1891 1973
1892 Non-blocking file handles, sockets, TCP clients and servers: 1974 Non-blocking handles, pipes, stream sockets, TCP clients and servers:
1893 AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS. 1975 AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS.
1894 1976
1895 Asynchronous DNS: AnyEvent::DNS. 1977 Asynchronous DNS: AnyEvent::DNS.
1896 1978
1897 Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event. 1979 Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event.

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines