| … | |
… | |
| 54 | |
54 | |
| 55 | DESCRIPTION |
55 | DESCRIPTION |
| 56 | This module provides an interface to libev |
56 | This module provides an interface to libev |
| 57 | (<http://software.schmorp.de/pkg/libev.html>). While the documentation |
57 | (<http://software.schmorp.de/pkg/libev.html>). While the documentation |
| 58 | below is comprehensive, one might also consult the documentation of |
58 | below is comprehensive, one might also consult the documentation of |
| 59 | libev itself (<http://cvs.schmorp.de/libev/ev.html>) for more subtle |
59 | libev itself (<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>) |
| 60 | details on watcher semantics or some discussion on the available |
60 | for more subtle details on watcher semantics or some discussion on the |
| 61 | backends, or how to force a specific backend with "LIBEV_FLAGS", or just |
61 | available backends, or how to force a specific backend with |
| 62 | about in any case because it has much more detailed information. |
62 | "LIBEV_FLAGS", or just about in any case because it has much more |
|
|
63 | detailed information. |
|
|
64 | |
|
|
65 | This module is very fast and scalable. It is actually so fast that you |
|
|
66 | can use it through the AnyEvent module, stay portable to other event |
|
|
67 | loops (if you don't rely on any watcher types not available through it) |
|
|
68 | and still be faster than with any other event loop currently supported |
|
|
69 | in Perl. |
| 63 | |
70 | |
| 64 | EVENT LOOPS |
71 | EVENT LOOPS |
| 65 | EV supports multiple event loops: There is a single "default event loop" |
72 | EV supports multiple event loops: There is a single "default event loop" |
| 66 | that can handle everything including signals and child watchers, and any |
73 | that can handle everything including signals and child watchers, and any |
| 67 | number of "dynamic event loops" that can use different backends (with |
74 | number of "dynamic event loops" that can use different backends (with |
| … | |
… | |
| 785 | |
792 | |
| 786 | It is, however, possible to use them from the XS level. |
793 | It is, however, possible to use them from the XS level. |
| 787 | |
794 | |
| 788 | Please see the libev documentation for further details. |
795 | Please see the libev documentation for further details. |
| 789 | |
796 | |
|
|
797 | $w = EV::async $callback |
|
|
798 | $w = EV::async_ns $callback |
|
|
799 | $w->send |
|
|
800 | $bool = $w->async_pending |
|
|
801 | |
| 790 | PERL SIGNALS |
802 | PERL SIGNALS |
| 791 | While Perl signal handling (%SIG) is not affected by EV, the behaviour |
803 | While Perl signal handling (%SIG) is not affected by EV, the behaviour |
| 792 | with EV is as the same as any other C library: Perl-signals will only be |
804 | with EV is as the same as any other C library: Perl-signals will only be |
| 793 | handled when Perl runs, which means your signal handler might be invoked |
805 | handled when Perl runs, which means your signal handler might be invoked |
| 794 | only the next time an event callback is invoked. |
806 | only the next time an event callback is invoked. |
| … | |
… | |
| 828 | course. |
840 | course. |
| 829 | |
841 | |
| 830 | SEE ALSO |
842 | SEE ALSO |
| 831 | EV::ADNS (asynchronous DNS), Glib::EV (makes Glib/Gtk2 use EV as event |
843 | EV::ADNS (asynchronous DNS), Glib::EV (makes Glib/Gtk2 use EV as event |
| 832 | loop), EV::Glib (embed Glib into EV), Coro::EV (efficient coroutines |
844 | loop), EV::Glib (embed Glib into EV), Coro::EV (efficient coroutines |
| 833 | with EV), Net::SNMP::EV (asynchronous SNMP). |
845 | with EV), Net::SNMP::EV (asynchronous SNMP), AnyEvent for event-loop |
|
|
846 | agnostic and portable event driven programming. |
| 834 | |
847 | |
| 835 | AUTHOR |
848 | AUTHOR |
| 836 | Marc Lehmann <schmorp@schmorp.de> |
849 | Marc Lehmann <schmorp@schmorp.de> |
| 837 | http://home.schmorp.de/ |
850 | http://home.schmorp.de/ |
| 838 | |
851 | |
