1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | AnyEvent - provide framework for multiple event loops |
3 | AnyEvent - provide framework for multiple event loops |
4 | |
4 | |
5 | EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops |
5 | EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops |
6 | |
6 | |
7 | =head1 SYNOPSIS |
7 | =head1 SYNOPSIS |
8 | |
8 | |
9 | use AnyEvent; |
9 | use AnyEvent; |
10 | |
10 | |
… | |
… | |
15 | my $w = AnyEvent->timer (after => $seconds, cb => sub { |
15 | my $w = AnyEvent->timer (after => $seconds, cb => sub { |
16 | ... |
16 | ... |
17 | }); |
17 | }); |
18 | |
18 | |
19 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
19 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
|
|
20 | $w->send; # wake up current and all future recv's |
20 | $w->wait; # enters "main loop" till $condvar gets ->broadcast |
21 | $w->recv; # enters "main loop" till $condvar gets ->send |
21 | $w->broadcast; # wake up current and all future wait's |
|
|
22 | |
22 | |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
24 | |
24 | |
25 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
25 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
26 | nowadays. So what is different about AnyEvent? |
26 | nowadays. So what is different about AnyEvent? |
… | |
… | |
66 | |
66 | |
67 | Of course, if you want lots of policy (this can arguably be somewhat |
67 | Of course, if you 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 |
68 | useful) and you want to force your users to use the one and only event |
69 | model, you should I<not> use this module. |
69 | model, you should I<not> use this module. |
70 | |
70 | |
71 | |
|
|
72 | =head1 DESCRIPTION |
71 | =head1 DESCRIPTION |
73 | |
72 | |
74 | L<AnyEvent> provides an identical interface to multiple event loops. This |
73 | L<AnyEvent> provides an identical interface to multiple event loops. This |
75 | allows module authors to utilise an event loop without forcing module |
74 | allows module authors to utilise an event loop without forcing module |
76 | users to use the same event loop (as only a single event loop can coexist |
75 | users to use the same event loop (as only a single event loop can coexist |
… | |
… | |
79 | The interface itself is vaguely similar, but not identical to the L<Event> |
78 | The interface itself is vaguely similar, but not identical to the L<Event> |
80 | module. |
79 | module. |
81 | |
80 | |
82 | During the first call of any watcher-creation method, the module tries |
81 | During the first call of any watcher-creation method, the module tries |
83 | to detect the currently loaded event loop by probing whether one of the |
82 | to detect the currently loaded event loop by probing whether one of the |
84 | following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>, |
83 | following modules is already loaded: L<EV>, |
85 | L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>, |
84 | L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>, |
86 | L<POE>. The first one found is used. If none are found, the module tries |
85 | L<POE>. The first one found is used. If none are found, the module tries |
87 | to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl |
86 | to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl |
88 | adaptor should always succeed) in the order given. The first one that can |
87 | adaptor should always succeed) in the order given. The first one that can |
89 | be successfully loaded will be used. If, after this, still none could be |
88 | be successfully loaded will be used. If, after this, still none could be |
… | |
… | |
280 | |
279 | |
281 | Example: fork a process and wait for it |
280 | Example: fork a process and wait for it |
282 | |
281 | |
283 | my $done = AnyEvent->condvar; |
282 | my $done = AnyEvent->condvar; |
284 | |
283 | |
285 | AnyEvent::detect; # force event module to be initialised |
|
|
286 | |
|
|
287 | my $pid = fork or exit 5; |
284 | my $pid = fork or exit 5; |
288 | |
285 | |
289 | my $w = AnyEvent->child ( |
286 | my $w = AnyEvent->child ( |
290 | pid => $pid, |
287 | pid => $pid, |
291 | cb => sub { |
288 | cb => sub { |
292 | my ($pid, $status) = @_; |
289 | my ($pid, $status) = @_; |
293 | warn "pid $pid exited with status $status"; |
290 | warn "pid $pid exited with status $status"; |
294 | $done->broadcast; |
291 | $done->send; |
295 | }, |
292 | }, |
296 | ); |
293 | ); |
297 | |
294 | |
298 | # do something else, then wait for process exit |
295 | # do something else, then wait for process exit |
299 | $done->wait; |
296 | $done->recv; |
300 | |
297 | |
301 | =head2 CONDITION VARIABLES |
298 | =head2 CONDITION VARIABLES |
302 | |
299 | |
|
|
300 | If you are familiar with some event loops you will know that all of them |
|
|
301 | require you to run some blocking "loop", "run" or similar function that |
|
|
302 | will actively watch for new events and call your callbacks. |
|
|
303 | |
|
|
304 | AnyEvent is different, it expects somebody else to run the event loop and |
|
|
305 | will only block when necessary (usually when told by the user). |
|
|
306 | |
|
|
307 | The instrument to do that is called a "condition variable", so called |
|
|
308 | because they represent a condition that must become true. |
|
|
309 | |
303 | Condition variables can be created by calling the C<< AnyEvent->condvar >> |
310 | Condition variables can be created by calling the C<< AnyEvent->condvar |
304 | method without any arguments. |
311 | >> method, usually without arguments. The only argument pair allowed is |
|
|
312 | C<cb>, which specifies a callback to be called when the condition variable |
|
|
313 | becomes true. |
305 | |
314 | |
306 | A condition variable waits for a condition - precisely that the C<< |
315 | After creation, the conditon variable is "false" until it becomes "true" |
307 | ->broadcast >> method has been called. |
316 | by calling the C<send> method. |
308 | |
317 | |
309 | They are very useful to signal that a condition has been fulfilled, for |
318 | Condition variables are similar to callbacks, except that you can |
|
|
319 | optionally wait for them. They can also be called merge points - points |
|
|
320 | in time where multiple outstandign events have been processed. And yet |
|
|
321 | another way to call them is transations - each condition variable can be |
|
|
322 | used to represent a transaction, which finishes at some point and delivers |
|
|
323 | a result. |
|
|
324 | |
|
|
325 | Condition variables are very useful to signal that something has finished, |
310 | example, if you write a module that does asynchronous http requests, |
326 | for example, if you write a module that does asynchronous http requests, |
311 | then a condition variable would be the ideal candidate to signal the |
327 | then a condition variable would be the ideal candidate to signal the |
312 | availability of results. |
328 | availability of results. The user can either act when the callback is |
|
|
329 | called or can synchronously C<< ->recv >> for the results. |
313 | |
330 | |
314 | You can also use condition variables to block your main program until |
331 | You can also use them to simulate traditional event loops - for example, |
315 | an event occurs - for example, you could C<< ->wait >> in your main |
332 | you can block your main program until an event occurs - for example, you |
316 | program until the user clicks the Quit button in your app, which would C<< |
333 | could C<< ->recv >> in your main program until the user clicks the Quit |
317 | ->broadcast >> the "quit" event. |
334 | button of your app, which would C<< ->send >> the "quit" event. |
318 | |
335 | |
319 | Note that condition variables recurse into the event loop - if you have |
336 | Note that condition variables recurse into the event loop - if you have |
320 | two pirces of code that call C<< ->wait >> in a round-robbin fashion, you |
337 | two pieces of code that call C<< ->recv >> in a round-robbin fashion, you |
321 | lose. Therefore, condition variables are good to export to your caller, but |
338 | lose. Therefore, condition variables are good to export to your caller, but |
322 | you should avoid making a blocking wait yourself, at least in callbacks, |
339 | you should avoid making a blocking wait yourself, at least in callbacks, |
323 | as this asks for trouble. |
340 | as this asks for trouble. |
324 | |
341 | |
325 | This object has two methods: |
342 | Condition variables are represented by hash refs in perl, and the keys |
|
|
343 | used by AnyEvent itself are all named C<_ae_XXX> to make subclassing |
|
|
344 | easy (it is often useful to build your own transaction class on top of |
|
|
345 | AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call |
|
|
346 | it's C<new> method in your own C<new> method. |
|
|
347 | |
|
|
348 | There are two "sides" to a condition variable - the "producer side" which |
|
|
349 | eventually calls C<< -> send >>, and the "consumer side", which waits |
|
|
350 | for the send to occur. |
|
|
351 | |
|
|
352 | Example: |
|
|
353 | |
|
|
354 | # wait till the result is ready |
|
|
355 | my $result_ready = AnyEvent->condvar; |
|
|
356 | |
|
|
357 | # do something such as adding a timer |
|
|
358 | # or socket watcher the calls $result_ready->send |
|
|
359 | # when the "result" is ready. |
|
|
360 | # in this case, we simply use a timer: |
|
|
361 | my $w = AnyEvent->timer ( |
|
|
362 | after => 1, |
|
|
363 | cb => sub { $result_ready->send }, |
|
|
364 | ); |
|
|
365 | |
|
|
366 | # this "blocks" (while handling events) till the callback |
|
|
367 | # calls send |
|
|
368 | $result_ready->recv; |
|
|
369 | |
|
|
370 | =head3 METHODS FOR PRODUCERS |
|
|
371 | |
|
|
372 | These methods should only be used by the producing side, i.e. the |
|
|
373 | code/module that eventually sends the signal. Note that it is also |
|
|
374 | the producer side which creates the condvar in most cases, but it isn't |
|
|
375 | uncommon for the consumer to create it as well. |
326 | |
376 | |
327 | =over 4 |
377 | =over 4 |
328 | |
378 | |
|
|
379 | =item $cv->send (...) |
|
|
380 | |
|
|
381 | Flag the condition as ready - a running C<< ->recv >> and all further |
|
|
382 | calls to C<recv> will (eventually) return after this method has been |
|
|
383 | called. If nobody is waiting the send will be remembered. |
|
|
384 | |
|
|
385 | If a callback has been set on the condition variable, it is called |
|
|
386 | immediately from within send. |
|
|
387 | |
|
|
388 | Any arguments passed to the C<send> call will be returned by all |
|
|
389 | future C<< ->recv >> calls. |
|
|
390 | |
|
|
391 | =item $cv->croak ($error) |
|
|
392 | |
|
|
393 | Similar to send, but causes all call's to C<< ->recv >> to invoke |
|
|
394 | C<Carp::croak> with the given error message/object/scalar. |
|
|
395 | |
|
|
396 | This can be used to signal any errors to the condition variable |
|
|
397 | user/consumer. |
|
|
398 | |
|
|
399 | =item $cv->begin ([group callback]) |
|
|
400 | |
329 | =item $cv->wait |
401 | =item $cv->end |
330 | |
402 | |
331 | Wait (blocking if necessary) until the C<< ->broadcast >> method has been |
403 | These two methods are EXPERIMENTAL and MIGHT CHANGE. |
|
|
404 | |
|
|
405 | These two methods can be used to combine many transactions/events into |
|
|
406 | one. For example, a function that pings many hosts in parallel might want |
|
|
407 | to use a condition variable for the whole process. |
|
|
408 | |
|
|
409 | Every call to C<< ->begin >> will increment a counter, and every call to |
|
|
410 | C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end |
|
|
411 | >>, the (last) callback passed to C<begin> will be executed. That callback |
|
|
412 | is I<supposed> to call C<< ->send >>, but that is not required. If no |
|
|
413 | callback was set, C<send> will be called without any arguments. |
|
|
414 | |
|
|
415 | Let's clarify this with the ping example: |
|
|
416 | |
|
|
417 | my $cv = AnyEvent->condvar; |
|
|
418 | |
|
|
419 | my %result; |
|
|
420 | $cv->begin (sub { $cv->send (\%result) }); |
|
|
421 | |
|
|
422 | for my $host (@list_of_hosts) { |
|
|
423 | $cv->begin; |
|
|
424 | ping_host_then_call_callback $host, sub { |
|
|
425 | $result{$host} = ...; |
|
|
426 | $cv->end; |
|
|
427 | }; |
|
|
428 | } |
|
|
429 | |
|
|
430 | $cv->end; |
|
|
431 | |
|
|
432 | This code fragment supposedly pings a number of hosts and calls |
|
|
433 | C<send> after results for all then have have been gathered - in any |
|
|
434 | order. To achieve this, the code issues a call to C<begin> when it starts |
|
|
435 | each ping request and calls C<end> when it has received some result for |
|
|
436 | it. Since C<begin> and C<end> only maintain a counter, the order in which |
|
|
437 | results arrive is not relevant. |
|
|
438 | |
|
|
439 | There is an additional bracketing call to C<begin> and C<end> outside the |
|
|
440 | loop, which serves two important purposes: first, it sets the callback |
|
|
441 | to be called once the counter reaches C<0>, and second, it ensures that |
|
|
442 | C<send> is called even when C<no> hosts are being pinged (the loop |
|
|
443 | doesn't execute once). |
|
|
444 | |
|
|
445 | This is the general pattern when you "fan out" into multiple subrequests: |
|
|
446 | use an outer C<begin>/C<end> pair to set the callback and ensure C<end> |
|
|
447 | is called at least once, and then, for each subrequest you start, call |
|
|
448 | C<begin> and for eahc subrequest you finish, call C<end>. |
|
|
449 | |
|
|
450 | =back |
|
|
451 | |
|
|
452 | =head3 METHODS FOR CONSUMERS |
|
|
453 | |
|
|
454 | These methods should only be used by the consuming side, i.e. the |
|
|
455 | code awaits the condition. |
|
|
456 | |
|
|
457 | =over 4 |
|
|
458 | |
|
|
459 | =item $cv->recv |
|
|
460 | |
|
|
461 | Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak |
332 | called on c<$cv>, while servicing other watchers normally. |
462 | >> methods have been called on c<$cv>, while servicing other watchers |
|
|
463 | normally. |
333 | |
464 | |
334 | You can only wait once on a condition - additional calls will return |
465 | You can only wait once on a condition - additional calls are valid but |
335 | immediately. |
466 | will return immediately. |
|
|
467 | |
|
|
468 | If an error condition has been set by calling C<< ->croak >>, then this |
|
|
469 | function will call C<croak>. |
|
|
470 | |
|
|
471 | In list context, all parameters passed to C<send> will be returned, |
|
|
472 | in scalar context only the first one will be returned. |
336 | |
473 | |
337 | Not all event models support a blocking wait - some die in that case |
474 | Not all event models support a blocking wait - some die in that case |
338 | (programs might want to do that to stay interactive), so I<if you are |
475 | (programs might want to do that to stay interactive), so I<if you are |
339 | using this from a module, never require a blocking wait>, but let the |
476 | using this from a module, never require a blocking wait>, but let the |
340 | caller decide whether the call will block or not (for example, by coupling |
477 | caller decide whether the call will block or not (for example, by coupling |
341 | condition variables with some kind of request results and supporting |
478 | condition variables with some kind of request results and supporting |
342 | callbacks so the caller knows that getting the result will not block, |
479 | callbacks so the caller knows that getting the result will not block, |
343 | while still suppporting blocking waits if the caller so desires). |
480 | while still suppporting blocking waits if the caller so desires). |
344 | |
481 | |
345 | Another reason I<never> to C<< ->wait >> in a module is that you cannot |
482 | Another reason I<never> to C<< ->recv >> in a module is that you cannot |
346 | sensibly have two C<< ->wait >>'s in parallel, as that would require |
483 | sensibly have two C<< ->recv >>'s in parallel, as that would require |
347 | multiple interpreters or coroutines/threads, none of which C<AnyEvent> |
484 | multiple interpreters or coroutines/threads, none of which C<AnyEvent> |
348 | can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and |
485 | can supply. |
349 | L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s |
|
|
350 | from different coroutines, however). |
|
|
351 | |
486 | |
352 | =item $cv->broadcast |
487 | The L<Coro> module, however, I<can> and I<does> supply coroutines and, in |
|
|
488 | fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe |
|
|
489 | versions and also integrates coroutines into AnyEvent, making blocking |
|
|
490 | C<< ->recv >> calls perfectly safe as long as they are done from another |
|
|
491 | coroutine (one that doesn't run the event loop). |
353 | |
492 | |
354 | Flag the condition as ready - a running C<< ->wait >> and all further |
493 | You can ensure that C<< -recv >> never blocks by setting a callback and |
355 | calls to C<wait> will (eventually) return after this method has been |
494 | only calling C<< ->recv >> from within that callback (or at a later |
356 | called. If nobody is waiting the broadcast will be remembered.. |
495 | time). This will work even when the event loop does not support blocking |
|
|
496 | waits otherwise. |
|
|
497 | |
|
|
498 | =item $bool = $cv->ready |
|
|
499 | |
|
|
500 | Returns true when the condition is "true", i.e. whether C<send> or |
|
|
501 | C<croak> have been called. |
|
|
502 | |
|
|
503 | =item $cb = $cv->cb ([new callback]) |
|
|
504 | |
|
|
505 | This is a mutator function that returns the callback set and optionally |
|
|
506 | replaces it before doing so. |
|
|
507 | |
|
|
508 | The callback will be called when the condition becomes "true", i.e. when |
|
|
509 | C<send> or C<croak> are called. Calling C<recv> inside the callback |
|
|
510 | or at any later time is guaranteed not to block. |
357 | |
511 | |
358 | =back |
512 | =back |
359 | |
|
|
360 | Example: |
|
|
361 | |
|
|
362 | # wait till the result is ready |
|
|
363 | my $result_ready = AnyEvent->condvar; |
|
|
364 | |
|
|
365 | # do something such as adding a timer |
|
|
366 | # or socket watcher the calls $result_ready->broadcast |
|
|
367 | # when the "result" is ready. |
|
|
368 | # in this case, we simply use a timer: |
|
|
369 | my $w = AnyEvent->timer ( |
|
|
370 | after => 1, |
|
|
371 | cb => sub { $result_ready->broadcast }, |
|
|
372 | ); |
|
|
373 | |
|
|
374 | # this "blocks" (while handling events) till the watcher |
|
|
375 | # calls broadcast |
|
|
376 | $result_ready->wait; |
|
|
377 | |
513 | |
378 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
514 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
379 | |
515 | |
380 | =over 4 |
516 | =over 4 |
381 | |
517 | |
… | |
… | |
387 | C<AnyEvent::Impl:xxx> modules, but can be any other class in the case |
523 | C<AnyEvent::Impl:xxx> modules, but can be any other class in the case |
388 | AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). |
524 | AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). |
389 | |
525 | |
390 | The known classes so far are: |
526 | The known classes so far are: |
391 | |
527 | |
392 | AnyEvent::Impl::CoroEV based on Coro::EV, best choice. |
|
|
393 | AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice. |
|
|
394 | AnyEvent::Impl::EV based on EV (an interface to libev, best choice). |
528 | AnyEvent::Impl::EV based on EV (an interface to libev, best choice). |
395 | AnyEvent::Impl::Event based on Event, second best choice. |
529 | AnyEvent::Impl::Event based on Event, second best choice. |
|
|
530 | AnyEvent::Impl::Perl pure-perl implementation, fast and portable. |
396 | AnyEvent::Impl::Glib based on Glib, third-best choice. |
531 | AnyEvent::Impl::Glib based on Glib, third-best choice. |
397 | AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable. |
|
|
398 | AnyEvent::Impl::Tk based on Tk, very bad choice. |
532 | AnyEvent::Impl::Tk based on Tk, very bad choice. |
399 | AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs). |
533 | AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs). |
400 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
534 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
401 | AnyEvent::Impl::POE based on POE, not generic enough for full support. |
535 | AnyEvent::Impl::POE based on POE, not generic enough for full support. |
402 | |
536 | |
… | |
… | |
415 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model |
549 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model |
416 | if necessary. You should only call this function right before you would |
550 | if necessary. You should only call this function right before you would |
417 | have created an AnyEvent watcher anyway, that is, as late as possible at |
551 | have created an AnyEvent watcher anyway, that is, as late as possible at |
418 | runtime. |
552 | runtime. |
419 | |
553 | |
|
|
554 | =item $guard = AnyEvent::post_detect { BLOCK } |
|
|
555 | |
|
|
556 | Arranges for the code block to be executed as soon as the event model is |
|
|
557 | autodetected (or immediately if this has already happened). |
|
|
558 | |
|
|
559 | If called in scalar or list context, then it creates and returns an object |
|
|
560 | that automatically removes the callback again when it is destroyed. See |
|
|
561 | L<Coro::BDB> for a case where this is useful. |
|
|
562 | |
|
|
563 | =item @AnyEvent::post_detect |
|
|
564 | |
|
|
565 | If there are any code references in this array (you can C<push> to it |
|
|
566 | before or after loading AnyEvent), then they will called directly after |
|
|
567 | the event loop has been chosen. |
|
|
568 | |
|
|
569 | You should check C<$AnyEvent::MODEL> before adding to this array, though: |
|
|
570 | if it contains a true value then the event loop has already been detected, |
|
|
571 | and the array will be ignored. |
|
|
572 | |
|
|
573 | Best use C<AnyEvent::post_detect { BLOCK }> instead. |
|
|
574 | |
420 | =back |
575 | =back |
421 | |
576 | |
422 | =head1 WHAT TO DO IN A MODULE |
577 | =head1 WHAT TO DO IN A MODULE |
423 | |
578 | |
424 | As a module author, you should C<use AnyEvent> and call AnyEvent methods |
579 | As a module author, you should C<use AnyEvent> and call AnyEvent methods |
… | |
… | |
427 | Be careful when you create watchers in the module body - AnyEvent will |
582 | Be careful when you create watchers in the module body - AnyEvent will |
428 | decide which event module to use as soon as the first method is called, so |
583 | decide which event module to use as soon as the first method is called, so |
429 | by calling AnyEvent in your module body you force the user of your module |
584 | by calling AnyEvent in your module body you force the user of your module |
430 | to load the event module first. |
585 | to load the event module first. |
431 | |
586 | |
432 | Never call C<< ->wait >> on a condition variable unless you I<know> that |
587 | Never call C<< ->recv >> on a condition variable unless you I<know> that |
433 | the C<< ->broadcast >> method has been called on it already. This is |
588 | the C<< ->send >> method has been called on it already. This is |
434 | because it will stall the whole program, and the whole point of using |
589 | because it will stall the whole program, and the whole point of using |
435 | events is to stay interactive. |
590 | events is to stay interactive. |
436 | |
591 | |
437 | It is fine, however, to call C<< ->wait >> when the user of your module |
592 | It is fine, however, to call C<< ->recv >> when the user of your module |
438 | requests it (i.e. if you create a http request object ad have a method |
593 | requests it (i.e. if you create a http request object ad have a method |
439 | called C<results> that returns the results, it should call C<< ->wait >> |
594 | called C<results> that returns the results, it should call C<< ->recv >> |
440 | freely, as the user of your module knows what she is doing. always). |
595 | freely, as the user of your module knows what she is doing. always). |
441 | |
596 | |
442 | =head1 WHAT TO DO IN THE MAIN PROGRAM |
597 | =head1 WHAT TO DO IN THE MAIN PROGRAM |
443 | |
598 | |
444 | There will always be a single main program - the only place that should |
599 | There will always be a single main program - the only place that should |
… | |
… | |
458 | |
613 | |
459 | You can chose to use a rather inefficient pure-perl implementation by |
614 | You can chose to use a rather inefficient pure-perl implementation by |
460 | loading the C<AnyEvent::Impl::Perl> module, which gives you similar |
615 | loading the C<AnyEvent::Impl::Perl> module, which gives you similar |
461 | behaviour everywhere, but letting AnyEvent chose is generally better. |
616 | behaviour everywhere, but letting AnyEvent chose is generally better. |
462 | |
617 | |
|
|
618 | =head1 OTHER MODULES |
|
|
619 | |
|
|
620 | The following is a non-exhaustive list of additional modules that use |
|
|
621 | AnyEvent and can therefore be mixed easily with other AnyEvent modules |
|
|
622 | in the same program. Some of the modules come with AnyEvent, some are |
|
|
623 | available via CPAN. |
|
|
624 | |
|
|
625 | =over 4 |
|
|
626 | |
|
|
627 | =item L<AnyEvent::Util> |
|
|
628 | |
|
|
629 | Contains various utility functions that replace often-used but blocking |
|
|
630 | functions such as C<inet_aton> by event-/callback-based versions. |
|
|
631 | |
|
|
632 | =item L<AnyEvent::Handle> |
|
|
633 | |
|
|
634 | Provide read and write buffers and manages watchers for reads and writes. |
|
|
635 | |
|
|
636 | =item L<AnyEvent::HTTPD> |
|
|
637 | |
|
|
638 | Provides a simple web application server framework. |
|
|
639 | |
|
|
640 | =item L<AnyEvent::DNS> |
|
|
641 | |
|
|
642 | Provides asynchronous DNS resolver capabilities, beyond what |
|
|
643 | L<AnyEvent::Util> offers. |
|
|
644 | |
|
|
645 | =item L<AnyEvent::FastPing> |
|
|
646 | |
|
|
647 | The fastest ping in the west. |
|
|
648 | |
|
|
649 | =item L<Net::IRC3> |
|
|
650 | |
|
|
651 | AnyEvent based IRC client module family. |
|
|
652 | |
|
|
653 | =item L<Net::XMPP2> |
|
|
654 | |
|
|
655 | AnyEvent based XMPP (Jabber protocol) module family. |
|
|
656 | |
|
|
657 | =item L<Net::FCP> |
|
|
658 | |
|
|
659 | AnyEvent-based implementation of the Freenet Client Protocol, birthplace |
|
|
660 | of AnyEvent. |
|
|
661 | |
|
|
662 | =item L<Event::ExecFlow> |
|
|
663 | |
|
|
664 | High level API for event-based execution flow control. |
|
|
665 | |
|
|
666 | =item L<Coro> |
|
|
667 | |
|
|
668 | Has special support for AnyEvent via L<Coro::AnyEvent>. |
|
|
669 | |
|
|
670 | =item L<AnyEvent::AIO>, L<IO::AIO> |
|
|
671 | |
|
|
672 | Truly asynchronous I/O, should be in the toolbox of every event |
|
|
673 | programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent |
|
|
674 | together. |
|
|
675 | |
|
|
676 | =item L<AnyEvent::BDB>, L<BDB> |
|
|
677 | |
|
|
678 | Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses |
|
|
679 | IO::AIO and AnyEvent together. |
|
|
680 | |
|
|
681 | =item L<IO::Lambda> |
|
|
682 | |
|
|
683 | The lambda approach to I/O - don't ask, look there. Can use AnyEvent. |
|
|
684 | |
|
|
685 | =back |
|
|
686 | |
463 | =cut |
687 | =cut |
464 | |
688 | |
465 | package AnyEvent; |
689 | package AnyEvent; |
466 | |
690 | |
467 | no warnings; |
691 | no warnings; |
468 | use strict; |
692 | use strict; |
469 | |
693 | |
470 | use Carp; |
694 | use Carp; |
471 | |
695 | |
472 | our $VERSION = '3.3'; |
696 | our $VERSION = '3.4'; |
473 | our $MODEL; |
697 | our $MODEL; |
474 | |
698 | |
475 | our $AUTOLOAD; |
699 | our $AUTOLOAD; |
476 | our @ISA; |
700 | our @ISA; |
477 | |
701 | |
478 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
702 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
479 | |
703 | |
480 | our @REGISTRY; |
704 | our @REGISTRY; |
481 | |
705 | |
482 | my @models = ( |
706 | my @models = ( |
483 | [Coro::EV:: => AnyEvent::Impl::CoroEV::], |
|
|
484 | [Coro::Event:: => AnyEvent::Impl::CoroEvent::], |
|
|
485 | [EV:: => AnyEvent::Impl::EV::], |
707 | [EV:: => AnyEvent::Impl::EV::], |
486 | [Event:: => AnyEvent::Impl::Event::], |
708 | [Event:: => AnyEvent::Impl::Event::], |
487 | [Glib:: => AnyEvent::Impl::Glib::], |
|
|
488 | [Tk:: => AnyEvent::Impl::Tk::], |
709 | [Tk:: => AnyEvent::Impl::Tk::], |
489 | [Wx:: => AnyEvent::Impl::POE::], |
710 | [Wx:: => AnyEvent::Impl::POE::], |
490 | [Prima:: => AnyEvent::Impl::POE::], |
711 | [Prima:: => AnyEvent::Impl::POE::], |
491 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
712 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
492 | # everything below here will not be autoprobed as the pureperl backend should work everywhere |
713 | # everything below here will not be autoprobed as the pureperl backend should work everywhere |
|
|
714 | [Glib:: => AnyEvent::Impl::Glib::], |
493 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
715 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
494 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
716 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
495 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
717 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
496 | ); |
718 | ); |
497 | |
719 | |
498 | our %method = map +($_ => 1), qw(io timer signal child condvar broadcast wait one_event DESTROY); |
720 | our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); |
|
|
721 | |
|
|
722 | our @post_detect; |
|
|
723 | |
|
|
724 | sub post_detect(&) { |
|
|
725 | my ($cb) = @_; |
|
|
726 | |
|
|
727 | if ($MODEL) { |
|
|
728 | $cb->(); |
|
|
729 | |
|
|
730 | 1 |
|
|
731 | } else { |
|
|
732 | push @post_detect, $cb; |
|
|
733 | |
|
|
734 | defined wantarray |
|
|
735 | ? bless \$cb, "AnyEvent::Util::Guard" |
|
|
736 | : () |
|
|
737 | } |
|
|
738 | } |
|
|
739 | |
|
|
740 | sub AnyEvent::Util::Guard::DESTROY { |
|
|
741 | @post_detect = grep $_ != ${$_[0]}, @post_detect; |
|
|
742 | } |
499 | |
743 | |
500 | sub detect() { |
744 | sub detect() { |
501 | unless ($MODEL) { |
745 | unless ($MODEL) { |
502 | no strict 'refs'; |
746 | no strict 'refs'; |
503 | |
747 | |
… | |
… | |
537 | last; |
781 | last; |
538 | } |
782 | } |
539 | } |
783 | } |
540 | |
784 | |
541 | $MODEL |
785 | $MODEL |
542 | or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event) or Glib."; |
786 | or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib."; |
543 | } |
787 | } |
544 | } |
788 | } |
545 | |
789 | |
546 | unshift @ISA, $MODEL; |
790 | unshift @ISA, $MODEL; |
547 | push @{"$MODEL\::ISA"}, "AnyEvent::Base"; |
791 | push @{"$MODEL\::ISA"}, "AnyEvent::Base"; |
|
|
792 | |
|
|
793 | (shift @post_detect)->() while @post_detect; |
548 | } |
794 | } |
549 | |
795 | |
550 | $MODEL |
796 | $MODEL |
551 | } |
797 | } |
552 | |
798 | |
… | |
… | |
562 | $class->$func (@_); |
808 | $class->$func (@_); |
563 | } |
809 | } |
564 | |
810 | |
565 | package AnyEvent::Base; |
811 | package AnyEvent::Base; |
566 | |
812 | |
567 | # default implementation for ->condvar, ->wait, ->broadcast |
813 | # default implementation for ->condvar |
568 | |
814 | |
569 | sub condvar { |
815 | sub condvar { |
570 | bless \my $flag, "AnyEvent::Base::CondVar" |
816 | bless {}, "AnyEvent::Base::CondVar" |
571 | } |
|
|
572 | |
|
|
573 | sub AnyEvent::Base::CondVar::broadcast { |
|
|
574 | ${$_[0]}++; |
|
|
575 | } |
|
|
576 | |
|
|
577 | sub AnyEvent::Base::CondVar::wait { |
|
|
578 | AnyEvent->one_event while !${$_[0]}; |
|
|
579 | } |
817 | } |
580 | |
818 | |
581 | # default implementation for ->signal |
819 | # default implementation for ->signal |
582 | |
820 | |
583 | our %SIG_CB; |
821 | our %SIG_CB; |
… | |
… | |
656 | delete $PID_CB{$pid}{$cb}; |
894 | delete $PID_CB{$pid}{$cb}; |
657 | delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; |
895 | delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; |
658 | |
896 | |
659 | undef $CHLD_W unless keys %PID_CB; |
897 | undef $CHLD_W unless keys %PID_CB; |
660 | } |
898 | } |
|
|
899 | |
|
|
900 | package AnyEvent::Base::CondVar; |
|
|
901 | |
|
|
902 | # wake up the waiter |
|
|
903 | sub _send { |
|
|
904 | &{ $_[0]{_ae_cb} } if $_[0]{_ae_cb}; |
|
|
905 | } |
|
|
906 | |
|
|
907 | sub send { |
|
|
908 | $_[0]{_ae_sent} = [@_]; |
|
|
909 | $_[0]->_send; |
|
|
910 | } |
|
|
911 | |
|
|
912 | sub croak { |
|
|
913 | $_[0]{_ae_croak} = $_[0]; |
|
|
914 | $_[0]->send; |
|
|
915 | } |
|
|
916 | |
|
|
917 | sub ready { |
|
|
918 | $_[0]{_ae_sent} |
|
|
919 | } |
|
|
920 | |
|
|
921 | sub recv { |
|
|
922 | AnyEvent->one_event while !$_[0]{_ae_sent}; |
|
|
923 | |
|
|
924 | Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak}; |
|
|
925 | wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0] |
|
|
926 | } |
|
|
927 | |
|
|
928 | sub cb { |
|
|
929 | $_[0]{_ae_cb} = $_[1] if @_ > 1; |
|
|
930 | $_[0]{_ae_cb} |
|
|
931 | } |
|
|
932 | |
|
|
933 | sub begin { |
|
|
934 | ++$_[0]{_ae_counter}; |
|
|
935 | $_[0]{_ae_end_cb} = $_[1] if @_ > 1; |
|
|
936 | } |
|
|
937 | |
|
|
938 | sub end { |
|
|
939 | return if --$_[0]{_ae_counter}; |
|
|
940 | &{ $_[0]{_ae_end_cb} } if $_[0]{_ae_end_cb}; |
|
|
941 | } |
|
|
942 | |
|
|
943 | # undocumented/compatibility with pre-3.4 |
|
|
944 | *broadcast = \&send; |
|
|
945 | *wait = \&recv; |
661 | |
946 | |
662 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
947 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
663 | |
948 | |
664 | This is an advanced topic that you do not normally need to use AnyEvent in |
949 | This is an advanced topic that you do not normally need to use AnyEvent in |
665 | a module. This section is only of use to event loop authors who want to |
950 | a module. This section is only of use to event loop authors who want to |
… | |
… | |
944 | EV/EV 400000 244 0.56 0.46 0.31 EV native interface |
1229 | EV/EV 400000 244 0.56 0.46 0.31 EV native interface |
945 | EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers |
1230 | EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers |
946 | CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal |
1231 | CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal |
947 | Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation |
1232 | Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation |
948 | Event/Event 16000 516 31.88 31.30 0.85 Event native interface |
1233 | Event/Event 16000 516 31.88 31.30 0.85 Event native interface |
949 | Event/Any 16000 936 39.17 33.63 1.43 Event + AnyEvent watchers |
1234 | Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers |
950 | Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour |
1235 | Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour |
951 | Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers |
1236 | Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers |
952 | POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event |
1237 | POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event |
953 | POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select |
1238 | POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select |
954 | |
1239 | |
… | |
… | |
1000 | file descriptor is dup()ed for each watcher. This shows that the dup() |
1285 | file descriptor is dup()ed for each watcher. This shows that the dup() |
1001 | employed by some adaptors is not a big performance issue (it does incur a |
1286 | employed by some adaptors is not a big performance issue (it does incur a |
1002 | hidden memory cost inside the kernel which is not reflected in the figures |
1287 | hidden memory cost inside the kernel which is not reflected in the figures |
1003 | above). |
1288 | above). |
1004 | |
1289 | |
1005 | C<POE>, regardless of underlying event loop (whether using its pure |
1290 | C<POE>, regardless of underlying event loop (whether using its pure perl |
1006 | perl select-based backend or the Event module, the POE-EV backend |
1291 | select-based backend or the Event module, the POE-EV backend couldn't |
1007 | couldn't be tested because it wasn't working) shows abysmal performance |
1292 | be tested because it wasn't working) shows abysmal performance and |
1008 | and memory usage: Watchers use almost 30 times as much memory as |
1293 | memory usage with AnyEvent: Watchers use almost 30 times as much memory |
1009 | EV watchers, and 10 times as much memory as Event (the high memory |
1294 | as EV watchers, and 10 times as much memory as Event (the high memory |
1010 | requirements are caused by requiring a session for each watcher). Watcher |
1295 | requirements are caused by requiring a session for each watcher). Watcher |
1011 | invocation speed is almost 900 times slower than with AnyEvent's pure perl |
1296 | invocation speed is almost 900 times slower than with AnyEvent's pure perl |
|
|
1297 | implementation. |
|
|
1298 | |
1012 | implementation. The design of the POE adaptor class in AnyEvent can not |
1299 | The design of the POE adaptor class in AnyEvent can not really account |
1013 | really account for this, as session creation overhead is small compared |
1300 | for the performance issues, though, as session creation overhead is |
1014 | to execution of the state machine, which is coded pretty optimally within |
1301 | small compared to execution of the state machine, which is coded pretty |
1015 | L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow. |
1302 | optimally within L<AnyEvent::Impl::POE> (and while everybody agrees that |
|
|
1303 | using multiple sessions is not a good approach, especially regarding |
|
|
1304 | memory usage, even the author of POE could not come up with a faster |
|
|
1305 | design). |
1016 | |
1306 | |
1017 | =head3 Summary |
1307 | =head3 Summary |
1018 | |
1308 | |
1019 | =over 4 |
1309 | =over 4 |
1020 | |
1310 | |
… | |
… | |
1067 | |
1357 | |
1068 | =head3 Results |
1358 | =head3 Results |
1069 | |
1359 | |
1070 | name sockets create request |
1360 | name sockets create request |
1071 | EV 20000 69.01 11.16 |
1361 | EV 20000 69.01 11.16 |
1072 | Perl 20000 75.28 112.76 |
1362 | Perl 20000 73.32 35.87 |
1073 | Event 20000 212.62 257.32 |
1363 | Event 20000 212.62 257.32 |
1074 | Glib 20000 651.16 1896.30 |
1364 | Glib 20000 651.16 1896.30 |
1075 | POE 20000 349.67 12317.24 uses POE::Loop::Event |
1365 | POE 20000 349.67 12317.24 uses POE::Loop::Event |
1076 | |
1366 | |
1077 | =head3 Discussion |
1367 | =head3 Discussion |
… | |
… | |
1099 | |
1389 | |
1100 | =head3 Summary |
1390 | =head3 Summary |
1101 | |
1391 | |
1102 | =over 4 |
1392 | =over 4 |
1103 | |
1393 | |
1104 | =item * The pure perl implementation performs extremely well, considering |
1394 | =item * The pure perl implementation performs extremely well. |
1105 | that it uses select. |
|
|
1106 | |
1395 | |
1107 | =item * Avoid Glib or POE in large projects where performance matters. |
1396 | =item * Avoid Glib or POE in large projects where performance matters. |
1108 | |
1397 | |
1109 | =back |
1398 | =back |
1110 | |
1399 | |
… | |
… | |
1123 | |
1412 | |
1124 | =head3 Results |
1413 | =head3 Results |
1125 | |
1414 | |
1126 | name sockets create request |
1415 | name sockets create request |
1127 | EV 16 20.00 6.54 |
1416 | EV 16 20.00 6.54 |
|
|
1417 | Perl 16 25.75 12.62 |
1128 | Event 16 81.27 35.86 |
1418 | Event 16 81.27 35.86 |
1129 | Glib 16 32.63 15.48 |
1419 | Glib 16 32.63 15.48 |
1130 | Perl 16 24.62 162.37 |
|
|
1131 | POE 16 261.87 276.28 uses POE::Loop::Event |
1420 | POE 16 261.87 276.28 uses POE::Loop::Event |
1132 | |
1421 | |
1133 | =head3 Discussion |
1422 | =head3 Discussion |
1134 | |
1423 | |
1135 | The benchmark tries to test the performance of a typical small |
1424 | The benchmark tries to test the performance of a typical small |
1136 | server. While knowing how various event loops perform is interesting, keep |
1425 | server. While knowing how various event loops perform is interesting, keep |
1137 | in mind that their overhead in this case is usually not as important, due |
1426 | in mind that their overhead in this case is usually not as important, due |
1138 | to the small absolute number of watchers. |
1427 | to the small absolute number of watchers (that is, you need efficiency and |
|
|
1428 | speed most when you have lots of watchers, not when you only have a few of |
|
|
1429 | them). |
1139 | |
1430 | |
1140 | EV is again fastest. |
1431 | EV is again fastest. |
1141 | |
1432 | |
1142 | The C-based event loops Event and Glib come in second this time, as the |
1433 | Perl again comes second. It is noticably faster than the C-based event |
1143 | overhead of running an iteration is much smaller in C than in Perl (little |
1434 | loops Event and Glib, although the difference is too small to really |
1144 | code to execute in the inner loop, and perl's function calling overhead is |
1435 | matter. |
1145 | high, and updating all the data structures is costly). |
|
|
1146 | |
1436 | |
1147 | The pure perl event loop is much slower, but still competitive. |
|
|
1148 | |
|
|
1149 | POE also performs much better in this case, but is is stillf ar behind the |
1437 | POE also performs much better in this case, but is is still far behind the |
1150 | others. |
1438 | others. |
1151 | |
1439 | |
1152 | =head3 Summary |
1440 | =head3 Summary |
1153 | |
1441 | |
1154 | =over 4 |
1442 | =over 4 |
… | |
… | |
1160 | |
1448 | |
1161 | |
1449 | |
1162 | =head1 FORK |
1450 | =head1 FORK |
1163 | |
1451 | |
1164 | Most event libraries are not fork-safe. The ones who are usually are |
1452 | Most event libraries are not fork-safe. The ones who are usually are |
1165 | because they are so inefficient. Only L<EV> is fully fork-aware. |
1453 | because they rely on inefficient but fork-safe C<select> or C<poll> |
|
|
1454 | calls. Only L<EV> is fully fork-aware. |
1166 | |
1455 | |
1167 | If you have to fork, you must either do so I<before> creating your first |
1456 | If you have to fork, you must either do so I<before> creating your first |
1168 | watcher OR you must not use AnyEvent at all in the child. |
1457 | watcher OR you must not use AnyEvent at all in the child. |
1169 | |
1458 | |
1170 | |
1459 | |
… | |
… | |
1182 | |
1471 | |
1183 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
1472 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
1184 | |
1473 | |
1185 | use AnyEvent; |
1474 | use AnyEvent; |
1186 | |
1475 | |
|
|
1476 | Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can |
|
|
1477 | be used to probe what backend is used and gain other information (which is |
|
|
1478 | probably even less useful to an attacker than PERL_ANYEVENT_MODEL). |
|
|
1479 | |
1187 | |
1480 | |
1188 | =head1 SEE ALSO |
1481 | =head1 SEE ALSO |
1189 | |
1482 | |
1190 | Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>, |
1483 | Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>, |
1191 | L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>, |
|
|
1192 | L<Event::Lib>, L<Qt>, L<POE>. |
1484 | L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. |
1193 | |
1485 | |
1194 | Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>, |
1486 | Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, |
1195 | L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>, |
1487 | L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, |
1196 | L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, L<AnyEvent::Impl::EventLib>, |
1488 | L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, |
1197 | L<AnyEvent::Impl::Qt>, L<AnyEvent::Impl::POE>. |
1489 | L<AnyEvent::Impl::POE>. |
|
|
1490 | |
|
|
1491 | Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>, |
1198 | |
1492 | |
1199 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>. |
1493 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>. |
1200 | |
1494 | |
1201 | |
1495 | |
1202 | =head1 AUTHOR |
1496 | =head1 AUTHOR |