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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.38 by root, Sun Nov 25 14:08:12 2007 UTC vs.
Revision 1.44 by root, Mon Apr 7 19:42:18 2008 UTC

… …
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 (OR NOT)
24
25Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26nowadays. So what is different about AnyEvent?
27
28Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
29policy> and AnyEvent is I<small and efficient>.
30
31First and foremost, I<AnyEvent is not an event model> itself, it only
32interfaces to whatever event model the main program happens to use in a
33pragmatic way. For event models and certain classes of immortals alike,
34the statement "there can only be one" is a bitter reality, and AnyEvent
35helps hiding the differences.
36
37The goal of AnyEvent is to offer module authors the ability to do event
38programming (waiting for I/O or timer events) without subscribing to a
39religion, a way of living, and most importantly: without forcing your
40module users into the same thing by forcing them to use the same event
41model you use.
42
43For modules like POE or IO::Async (which is actually doing all I/O
44I<synchronously>...), using them in your module is like joining a
45cult: After you joined, you are dependent on them and you cannot use
46anything else, as it is simply incompatible to everything that isn't
47itself.
48
49AnyEvent + POE works fine. AnyEvent + Glib works fine. AnyEvent + Tk
50works fine etc. etc. but none of these work together with the rest: POE
51+ IO::Async? no go. Tk + Event? no go. If your module uses one of
52those, every user of your module has to use it, too. If your module
53uses AnyEvent, it works transparently with all event models it supports
54(including stuff like POE and IO::Async).
55
56In addition of being free of having to use I<the one and only true event
57model>, AnyEvent also is free of bloat and policy: with POE or similar
58modules, you get an enourmous amount of code and strict rules you have
59to follow. AnyEvent, on the other hand, is lean and to the point by only
60offering the functionality that is useful, in as thin as a wrapper as
61technically possible.
62
63Of course, if you want lots of policy (this is arguably somewhat useful
64in many cases) and you want to force your users to the one and only event
65model your module forces on them, you should I<not> use this module.
66
22 67
23=head1 DESCRIPTION 68=head1 DESCRIPTION
24 69
25L<AnyEvent> provides an identical interface to multiple event loops. This 70L<AnyEvent> provides an identical interface to multiple event loops. This
26allows module authors to utilise an event loop without forcing module 71allows module authors to utilise an event loop without forcing module
… …
119method without any arguments. 164method without any arguments.
120 165
121A condition watcher watches for a condition - precisely that the C<< 166A condition watcher watches for a condition - precisely that the C<<
122->broadcast >> method has been called. 167->broadcast >> method has been called.
123 168
169Note that condition watchers recurse into the event loop - if you have
170two watchers that call C<< ->wait >> in a round-robbin fashion, you
171lose. Therefore, condition watchers are good to export to your caller, but
172you should avoid making a blocking wait, at least in callbacks, as this
173usually asks for trouble.
174
124The watcher has only two methods: 175The watcher has only two methods:
125 176
126=over 4 177=over 4
127 178
128=item $cv->wait 179=item $cv->wait
… …
199 250
200The known classes so far are: 251The known classes so far are:
201 252
202 AnyEvent::Impl::CoroEV based on Coro::EV, best choice. 253 AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
203 AnyEvent::Impl::EV based on EV (an interface to libev, also best choice). 254 AnyEvent::Impl::EV based on EV (an interface to libev, also best choice).
204 AnyEvent::Impl::Coro based on Coro::Event, second best choice. 255 AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
205 AnyEvent::Impl::Event based on Event, also second best choice :) 256 AnyEvent::Impl::Event based on Event, also second best choice :)
206 AnyEvent::Impl::Glib based on Glib, second-best choice. 257 AnyEvent::Impl::Glib based on Glib, second-best choice.
207 AnyEvent::Impl::Tk based on Tk, very bad choice. 258 AnyEvent::Impl::Tk based on Tk, very bad choice.
208 AnyEvent::Impl::Perl pure-perl implementation, inefficient. 259 AnyEvent::Impl::Perl pure-perl implementation, inefficient.
209 260
… …
252no warnings; 303no warnings;
253use strict; 304use strict;
254 305
255use Carp; 306use Carp;
256 307
257our $VERSION = '2.8'; 308our $VERSION = '3.0';
258our $MODEL; 309our $MODEL;
259 310
260our $AUTOLOAD; 311our $AUTOLOAD;
261our @ISA; 312our @ISA;
262 313
… …
265our @REGISTRY; 316our @REGISTRY;
266 317
267my @models = ( 318my @models = (
268 [Coro::EV:: => AnyEvent::Impl::CoroEV::], 319 [Coro::EV:: => AnyEvent::Impl::CoroEV::],
269 [EV:: => AnyEvent::Impl::EV::], 320 [EV:: => AnyEvent::Impl::EV::],
270 [Coro::Event:: => AnyEvent::Impl::Coro::], 321 [Coro::Event:: => AnyEvent::Impl::CoroEvent::],
271 [Event:: => AnyEvent::Impl::Event::], 322 [Event:: => AnyEvent::Impl::Event::],
272 [Glib:: => AnyEvent::Impl::Glib::], 323 [Glib:: => AnyEvent::Impl::Glib::],
273 [Tk:: => AnyEvent::Impl::Tk::], 324 [Tk:: => AnyEvent::Impl::Tk::],
274 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], 325 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
275); 326);

Diff Legend

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