… | |
… | |
48 | isn't itself. What's worse, all the potential users of your module are |
48 | isn't itself. What's worse, all the potential users of your module are |
49 | I<also> forced to use the same event loop you use. |
49 | I<also> forced to use the same event loop you use. |
50 | |
50 | |
51 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
51 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
52 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
52 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
53 | with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if |
53 | with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if |
54 | your module uses one of those, every user of your module has to use it, |
54 | your module uses one of those, every user of your module has to use it, |
55 | too. But if your module uses AnyEvent, it works transparently with all |
55 | too. But if your module uses AnyEvent, it works transparently with all |
56 | event models it supports (including stuff like POE and IO::Async, as long |
56 | event models it supports (including stuff like POE and IO::Async, as long |
57 | as those use one of the supported event loops. It is trivial to add new |
57 | as those use one of the supported event loops. It is trivial to add new |
58 | event loops to AnyEvent, too, so it is future-proof). |
58 | event loops to AnyEvent, too, so it is future-proof). |
… | |
… | |
62 | modules, you get an enormous amount of code and strict rules you have to |
62 | modules, you get an enormous amount of code and strict rules you have to |
63 | follow. AnyEvent, on the other hand, is lean and up to the point, by only |
63 | follow. AnyEvent, on the other hand, is lean and up to the point, by only |
64 | offering the functionality that is necessary, in as thin as a wrapper as |
64 | offering the functionality that is necessary, in as thin as a wrapper as |
65 | technically possible. |
65 | technically possible. |
66 | |
66 | |
|
|
67 | Of course, AnyEvent comes with a big (and fully optional!) toolbox |
|
|
68 | of useful functionality, such as an asynchronous DNS resolver, 100% |
|
|
69 | non-blocking connects (even with TLS/SSL, IPv6 and on broken platforms |
|
|
70 | such as Windows) and lots of real-world knowledge and workarounds for |
|
|
71 | platform bugs and differences. |
|
|
72 | |
67 | Of course, if you want lots of policy (this can arguably be somewhat |
73 | Now, if you I<do want> lots of policy (this can arguably be somewhat |
68 | useful) and you want to force your users to use the one and only event |
74 | useful) and you want to force your users to use the one and only event |
69 | model, you should I<not> use this module. |
75 | model, you should I<not> use this module. |
70 | |
76 | |
71 | =head1 DESCRIPTION |
77 | =head1 DESCRIPTION |
72 | |
78 | |
… | |
… | |
102 | starts using it, all bets are off. Maybe you should tell their authors to |
108 | starts using it, all bets are off. Maybe you should tell their authors to |
103 | use AnyEvent so their modules work together with others seamlessly... |
109 | use AnyEvent so their modules work together with others seamlessly... |
104 | |
110 | |
105 | The pure-perl implementation of AnyEvent is called |
111 | The pure-perl implementation of AnyEvent is called |
106 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
112 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
107 | explicitly. |
113 | explicitly and enjoy the high availability of that event loop :) |
108 | |
114 | |
109 | =head1 WATCHERS |
115 | =head1 WATCHERS |
110 | |
116 | |
111 | AnyEvent has the central concept of a I<watcher>, which is an object that |
117 | AnyEvent has the central concept of a I<watcher>, which is an object that |
112 | stores relevant data for each kind of event you are waiting for, such as |
118 | stores relevant data for each kind of event you are waiting for, such as |
… | |
… | |
226 | on true relative time) and absolute (ev_periodic, based on wallclock time) |
232 | on true relative time) and absolute (ev_periodic, based on wallclock time) |
227 | timers. |
233 | timers. |
228 | |
234 | |
229 | AnyEvent always prefers relative timers, if available, matching the |
235 | AnyEvent always prefers relative timers, if available, matching the |
230 | AnyEvent API. |
236 | AnyEvent API. |
|
|
237 | |
|
|
238 | AnyEvent has two additional methods that return the "current time": |
|
|
239 | |
|
|
240 | =over 4 |
|
|
241 | |
|
|
242 | =item AnyEvent->time |
|
|
243 | |
|
|
244 | This returns the "current wallclock time" as a fractional number of |
|
|
245 | seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time> |
|
|
246 | return, and the result is guaranteed to be compatible with those). |
|
|
247 | |
|
|
248 | It progresses independently of any event loop processing, i.e. each call |
|
|
249 | will check the system clock, which usually gets updated frequently. |
|
|
250 | |
|
|
251 | =item AnyEvent->now |
|
|
252 | |
|
|
253 | This also returns the "current wallclock time", but unlike C<time>, above, |
|
|
254 | this value might change only once per event loop iteration, depending on |
|
|
255 | the event loop (most return the same time as C<time>, above). This is the |
|
|
256 | time that AnyEvent's timers get scheduled against. |
|
|
257 | |
|
|
258 | I<In almost all cases (in all cases if you don't care), this is the |
|
|
259 | function to call when you want to know the current time.> |
|
|
260 | |
|
|
261 | This function is also often faster then C<< AnyEvent->time >>, and |
|
|
262 | thus the preferred method if you want some timestamp (for example, |
|
|
263 | L<AnyEvent::Handle> uses this to update it's activity timeouts). |
|
|
264 | |
|
|
265 | The rest of this section is only of relevance if you try to be very exact |
|
|
266 | with your timing, you can skip it without bad conscience. |
|
|
267 | |
|
|
268 | For a practical example of when these times differ, consider L<Event::Lib> |
|
|
269 | and L<EV> and the following set-up: |
|
|
270 | |
|
|
271 | The event loop is running and has just invoked one of your callback at |
|
|
272 | time=500 (assume no other callbacks delay processing). In your callback, |
|
|
273 | you wait a second by executing C<sleep 1> (blocking the process for a |
|
|
274 | second) and then (at time=501) you create a relative timer that fires |
|
|
275 | after three seconds. |
|
|
276 | |
|
|
277 | With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will |
|
|
278 | both return C<501>, because that is the current time, and the timer will |
|
|
279 | be scheduled to fire at time=504 (C<501> + C<3>). |
|
|
280 | |
|
|
281 | With L<EV>, C<< AnyEvent->time >> returns C<501> (as that is the current |
|
|
282 | time), but C<< AnyEvent->now >> returns C<500>, as that is the time the |
|
|
283 | last event processing phase started. With L<EV>, your timer gets scheduled |
|
|
284 | to run at time=503 (C<500> + C<3>). |
|
|
285 | |
|
|
286 | In one sense, L<Event::Lib> is more exact, as it uses the current time |
|
|
287 | regardless of any delays introduced by event processing. However, most |
|
|
288 | callbacks do not expect large delays in processing, so this causes a |
|
|
289 | higher drift (and a lot more system calls to get the current time). |
|
|
290 | |
|
|
291 | In another sense, L<EV> is more exact, as your timer will be scheduled at |
|
|
292 | the same time, regardless of how long event processing actually took. |
|
|
293 | |
|
|
294 | In either case, if you care (and in most cases, you don't), then you |
|
|
295 | can get whatever behaviour you want with any event loop, by taking the |
|
|
296 | difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into |
|
|
297 | account. |
|
|
298 | |
|
|
299 | =back |
231 | |
300 | |
232 | =head2 SIGNAL WATCHERS |
301 | =head2 SIGNAL WATCHERS |
233 | |
302 | |
234 | You can watch for signals using a signal watcher, C<signal> is the signal |
303 | You can watch for signals using a signal watcher, C<signal> is the signal |
235 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
304 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
… | |
… | |
731 | no warnings; |
800 | no warnings; |
732 | use strict; |
801 | use strict; |
733 | |
802 | |
734 | use Carp; |
803 | use Carp; |
735 | |
804 | |
736 | our $VERSION = '4.03'; |
805 | our $VERSION = '4.05'; |
737 | our $MODEL; |
806 | our $MODEL; |
738 | |
807 | |
739 | our $AUTOLOAD; |
808 | our $AUTOLOAD; |
740 | our @ISA; |
809 | our @ISA; |
741 | |
810 | |
… | |
… | |
755 | { |
824 | { |
756 | my $idx; |
825 | my $idx; |
757 | $PROTOCOL{$_} = ++$idx |
826 | $PROTOCOL{$_} = ++$idx |
758 | for reverse split /\s*,\s*/, |
827 | for reverse split /\s*,\s*/, |
759 | $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; |
828 | $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; |
760 | } |
|
|
761 | |
|
|
762 | sub import { |
|
|
763 | shift; |
|
|
764 | return unless @_; |
|
|
765 | |
|
|
766 | my $pkg = caller; |
|
|
767 | |
|
|
768 | no strict 'refs'; |
|
|
769 | |
|
|
770 | for (@_) { |
|
|
771 | *{"$pkg\::WIN32"} = *WIN32 if $_ eq "WIN32"; |
|
|
772 | } |
|
|
773 | } |
829 | } |
774 | |
830 | |
775 | my @models = ( |
831 | my @models = ( |
776 | [EV:: => AnyEvent::Impl::EV::], |
832 | [EV:: => AnyEvent::Impl::EV::], |
777 | [Event:: => AnyEvent::Impl::Event::], |
833 | [Event:: => AnyEvent::Impl::Event::], |
… | |
… | |
786 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
842 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
787 | [Wx:: => AnyEvent::Impl::POE::], |
843 | [Wx:: => AnyEvent::Impl::POE::], |
788 | [Prima:: => AnyEvent::Impl::POE::], |
844 | [Prima:: => AnyEvent::Impl::POE::], |
789 | ); |
845 | ); |
790 | |
846 | |
791 | our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); |
847 | our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY); |
792 | |
848 | |
793 | our @post_detect; |
849 | our @post_detect; |
794 | |
850 | |
795 | sub post_detect(&) { |
851 | sub post_detect(&) { |
796 | my ($cb) = @_; |
852 | my ($cb) = @_; |
… | |
… | |
880 | $class->$func (@_); |
936 | $class->$func (@_); |
881 | } |
937 | } |
882 | |
938 | |
883 | package AnyEvent::Base; |
939 | package AnyEvent::Base; |
884 | |
940 | |
|
|
941 | # default implementation for now and time |
|
|
942 | |
|
|
943 | use Time::HiRes (); |
|
|
944 | |
|
|
945 | sub time { Time::HiRes::time } |
|
|
946 | sub now { Time::HiRes::time } |
|
|
947 | |
885 | # default implementation for ->condvar |
948 | # default implementation for ->condvar |
886 | |
949 | |
887 | sub condvar { |
950 | sub condvar { |
888 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
951 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
889 | } |
952 | } |
… | |
… | |
1135 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1198 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1136 | default. |
1199 | default. |
1137 | |
1200 | |
1138 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1201 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1139 | EDNS0 in its DNS requests. |
1202 | EDNS0 in its DNS requests. |
|
|
1203 | |
|
|
1204 | =item C<PERL_ANYEVENT_MAX_FORKS> |
|
|
1205 | |
|
|
1206 | The maximum number of child processes that C<AnyEvent::Util::fork_call> |
|
|
1207 | will create in parallel. |
1140 | |
1208 | |
1141 | =back |
1209 | =back |
1142 | |
1210 | |
1143 | =head1 EXAMPLE PROGRAM |
1211 | =head1 EXAMPLE PROGRAM |
1144 | |
1212 | |