| … | |
… | |
| 17 | }); |
17 | }); |
| 18 | |
18 | |
| 19 | my $w = AnyEvent->condvar; # stores wether a condition was flagged |
19 | my $w = AnyEvent->condvar; # stores wether a condition was flagged |
| 20 | $w->wait; # enters "main loop" till $condvar gets ->broadcast |
20 | $w->wait; # enters "main loop" till $condvar gets ->broadcast |
| 21 | $w->broadcast; # wake up current and all future wait's |
21 | $w->broadcast; # wake up current and all future wait's |
|
|
22 | |
|
|
23 | =head1 WHY YOU SHOULD USE THIS MODULE |
|
|
24 | |
|
|
25 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
|
|
26 | nowadays. So what is different about AnyEvent? |
|
|
27 | |
|
|
28 | Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of |
|
|
29 | policy> and AnyEvent is I<small and efficient>. |
|
|
30 | |
|
|
31 | First and foremost, I<AnyEvent is not an event model> itself, it only |
|
|
32 | interfaces to whatever event model the main program happens to use in a |
|
|
33 | pragmatic way. For event models and certain classes of immortals alike, |
|
|
34 | the statement "there can only be one" is a bitter reality, and AnyEvent |
|
|
35 | helps hiding the differences. |
|
|
36 | |
|
|
37 | The goal of AnyEvent is to offer module authors the ability to do event |
|
|
38 | programming (waiting for I/O or timer events) without subscribing to a |
|
|
39 | religion, a way of living, and most importantly: without forcing your |
|
|
40 | module users into the same thing by forcing them to use the same event |
|
|
41 | model you use. |
|
|
42 | |
|
|
43 | For modules like POE or IO::Async (the latter of which is actually |
|
|
44 | named confusingly, as it does neither do I/O nor does it do anything |
|
|
45 | asynchronously...), using them in your module is like joining a |
|
|
46 | cult: After you joined, you are dependent on them and you cannot use |
|
|
47 | anything else, as it is simply incompatible to everything that isn't |
|
|
48 | itself. |
|
|
49 | |
|
|
50 | AnyEvent + POE works fine. AnyEvent + Glib works fine. AnyEvent + Tk |
|
|
51 | works fine etc. etc. but none of these work together with the rest: POE |
|
|
52 | + IO::Async? no go. Tk + Event? no go. If your module uses one of |
|
|
53 | those, every user of your module has to use it, too. If your module |
|
|
54 | uses AnyEvent, it works transparently with all event models it supports |
|
|
55 | (including stuff like POE and IO::Async). |
|
|
56 | |
|
|
57 | In addition of being free of having to use I<the one and only true event |
|
|
58 | model>, AnyEvent also is free of bloat and policy: with POE or similar |
|
|
59 | modules, you get an enourmous amount of code and strict rules you have |
|
|
60 | to follow. AnyEvent, on the other hand, is lean and to the point by only |
|
|
61 | offering the functionality that is useful, in as thin as a wrapper as |
|
|
62 | technically possible. |
|
|
63 | |
| 22 | |
64 | |
| 23 | =head1 DESCRIPTION |
65 | =head1 DESCRIPTION |
| 24 | |
66 | |
| 25 | L<AnyEvent> provides an identical interface to multiple event loops. This |
67 | L<AnyEvent> provides an identical interface to multiple event loops. This |
| 26 | allows module authors to utilise an event loop without forcing module |
68 | allows module authors to utilise an event loop without forcing module |
| … | |
… | |
| 119 | method without any arguments. |
161 | method without any arguments. |
| 120 | |
162 | |
| 121 | A condition watcher watches for a condition - precisely that the C<< |
163 | A condition watcher watches for a condition - precisely that the C<< |
| 122 | ->broadcast >> method has been called. |
164 | ->broadcast >> method has been called. |
| 123 | |
165 | |
|
|
166 | Note that condition watchers recurse into the event loop - if you have |
|
|
167 | two watchers that call C<< ->wait >> in a round-robbin fashion, you |
|
|
168 | lose. Therefore, condition watchers are good to export to your caller, but |
|
|
169 | you should avoid making a blocking wait, at least in callbacks, as this |
|
|
170 | usually asks for trouble. |
|
|
171 | |
| 124 | The watcher has only two methods: |
172 | The watcher has only two methods: |
| 125 | |
173 | |
| 126 | =over 4 |
174 | =over 4 |
| 127 | |
175 | |
| 128 | =item $cv->wait |
176 | =item $cv->wait |
| … | |
… | |
| 252 | no warnings; |
300 | no warnings; |
| 253 | use strict; |
301 | use strict; |
| 254 | |
302 | |
| 255 | use Carp; |
303 | use Carp; |
| 256 | |
304 | |
| 257 | our $VERSION = '2.9'; |
305 | our $VERSION = '3.0'; |
| 258 | our $MODEL; |
306 | our $MODEL; |
| 259 | |
307 | |
| 260 | our $AUTOLOAD; |
308 | our $AUTOLOAD; |
| 261 | our @ISA; |
309 | our @ISA; |
| 262 | |
310 | |
