… | |
… | |
176 | =head2 I/O WATCHERS |
176 | =head2 I/O WATCHERS |
177 | |
177 | |
178 | You can create an I/O watcher by calling the C<< AnyEvent->io >> method |
178 | You can create an I/O watcher by calling the C<< AnyEvent->io >> method |
179 | with the following mandatory key-value pairs as arguments: |
179 | with the following mandatory key-value pairs as arguments: |
180 | |
180 | |
181 | C<fh> is the Perl I<file handle> (I<not> file descriptor) to watch |
181 | C<fh> is the Perl I<file handle> (or a naked file descriptor) to watch |
182 | for events (AnyEvent might or might not keep a reference to this file |
182 | for events (AnyEvent might or might not keep a reference to this file |
183 | handle). Note that only file handles pointing to things for which |
183 | handle). Note that only file handles pointing to things for which |
184 | non-blocking operation makes sense are allowed. This includes sockets, |
184 | non-blocking operation makes sense are allowed. This includes sockets, |
185 | most character devices, pipes, fifos and so on, but not for example files |
185 | most character devices, pipes, fifos and so on, but not for example files |
186 | or block devices. |
186 | or block devices. |
… | |
… | |
599 | |
599 | |
600 | =item $cv->begin ([group callback]) |
600 | =item $cv->begin ([group callback]) |
601 | |
601 | |
602 | =item $cv->end |
602 | =item $cv->end |
603 | |
603 | |
604 | These two methods are EXPERIMENTAL and MIGHT CHANGE. |
|
|
605 | |
|
|
606 | These two methods can be used to combine many transactions/events into |
604 | These two methods can be used to combine many transactions/events into |
607 | one. For example, a function that pings many hosts in parallel might want |
605 | one. For example, a function that pings many hosts in parallel might want |
608 | to use a condition variable for the whole process. |
606 | to use a condition variable for the whole process. |
609 | |
607 | |
610 | Every call to C<< ->begin >> will increment a counter, and every call to |
608 | Every call to C<< ->begin >> will increment a counter, and every call to |
611 | C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end |
609 | C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end |
612 | >>, the (last) callback passed to C<begin> will be executed. That callback |
610 | >>, the (last) callback passed to C<begin> will be executed. That callback |
613 | is I<supposed> to call C<< ->send >>, but that is not required. If no |
611 | is I<supposed> to call C<< ->send >>, but that is not required. If no |
614 | callback was set, C<send> will be called without any arguments. |
612 | callback was set, C<send> will be called without any arguments. |
615 | |
613 | |
616 | Let's clarify this with the ping example: |
614 | You can think of C<< $cv->send >> giving you an OR condition (one call |
|
|
615 | sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND |
|
|
616 | condition (all C<begin> calls must be C<end>'ed before the condvar sends). |
|
|
617 | |
|
|
618 | Let's start with a simple example: you have two I/O watchers (for example, |
|
|
619 | STDOUT and STDERR for a program), and you want to wait for both streams to |
|
|
620 | close before activating a condvar: |
|
|
621 | |
|
|
622 | my $cv = AnyEvent->condvar; |
|
|
623 | |
|
|
624 | $cv->begin; # first watcher |
|
|
625 | my $w1 = AnyEvent->io (fh => $fh1, cb => sub { |
|
|
626 | defined sysread $fh1, my $buf, 4096 |
|
|
627 | or $cv->end; |
|
|
628 | }); |
|
|
629 | |
|
|
630 | $cv->begin; # second watcher |
|
|
631 | my $w2 = AnyEvent->io (fh => $fh2, cb => sub { |
|
|
632 | defined sysread $fh2, my $buf, 4096 |
|
|
633 | or $cv->end; |
|
|
634 | }); |
|
|
635 | |
|
|
636 | $cv->recv; |
|
|
637 | |
|
|
638 | This works because for every event source (EOF on file handle), there is |
|
|
639 | one call to C<begin>, so the condvar waits for all calls to C<end> before |
|
|
640 | sending. |
|
|
641 | |
|
|
642 | The ping example mentioned above is slightly more complicated, as the |
|
|
643 | there are results to be passwd back, and the number of tasks that are |
|
|
644 | begung can potentially be zero: |
617 | |
645 | |
618 | my $cv = AnyEvent->condvar; |
646 | my $cv = AnyEvent->condvar; |
619 | |
647 | |
620 | my %result; |
648 | my %result; |
621 | $cv->begin (sub { $cv->send (\%result) }); |
649 | $cv->begin (sub { $cv->send (\%result) }); |
… | |
… | |
641 | loop, which serves two important purposes: first, it sets the callback |
669 | loop, which serves two important purposes: first, it sets the callback |
642 | to be called once the counter reaches C<0>, and second, it ensures that |
670 | to be called once the counter reaches C<0>, and second, it ensures that |
643 | C<send> is called even when C<no> hosts are being pinged (the loop |
671 | C<send> is called even when C<no> hosts are being pinged (the loop |
644 | doesn't execute once). |
672 | doesn't execute once). |
645 | |
673 | |
646 | This is the general pattern when you "fan out" into multiple subrequests: |
674 | This is the general pattern when you "fan out" into multiple (but |
647 | use an outer C<begin>/C<end> pair to set the callback and ensure C<end> |
675 | potentially none) subrequests: use an outer C<begin>/C<end> pair to set |
648 | is called at least once, and then, for each subrequest you start, call |
676 | the callback and ensure C<end> is called at least once, and then, for each |
649 | C<begin> and for each subrequest you finish, call C<end>. |
677 | subrequest you start, call C<begin> and for each subrequest you finish, |
|
|
678 | call C<end>. |
650 | |
679 | |
651 | =back |
680 | =back |
652 | |
681 | |
653 | =head3 METHODS FOR CONSUMERS |
682 | =head3 METHODS FOR CONSUMERS |
654 | |
683 | |
… | |
… | |
711 | variable itself. Calling C<recv> inside the callback or at any later time |
740 | variable itself. Calling C<recv> inside the callback or at any later time |
712 | is guaranteed not to block. |
741 | is guaranteed not to block. |
713 | |
742 | |
714 | =back |
743 | =back |
715 | |
744 | |
|
|
745 | =head1 SUPPORTED EVENT LOOPS/BACKENDS |
|
|
746 | |
|
|
747 | The available backend classes are (every class has its own manpage): |
|
|
748 | |
|
|
749 | =over 4 |
|
|
750 | |
|
|
751 | =item Backends that are autoprobed when no other event loop can be found. |
|
|
752 | |
|
|
753 | EV is the preferred backend when no other event loop seems to be in |
|
|
754 | use. If EV is not installed, then AnyEvent will try Event, and, failing |
|
|
755 | that, will fall back to its own pure-perl implementation, which is |
|
|
756 | available everywhere as it comes with AnyEvent itself. |
|
|
757 | |
|
|
758 | AnyEvent::Impl::EV based on EV (interface to libev, best choice). |
|
|
759 | AnyEvent::Impl::Event based on Event, very stable, few glitches. |
|
|
760 | AnyEvent::Impl::Perl pure-perl implementation, fast and portable. |
|
|
761 | |
|
|
762 | =item Backends that are transparently being picked up when they are used. |
|
|
763 | |
|
|
764 | These will be used when they are currently loaded when the first watcher |
|
|
765 | is created, in which case it is assumed that the application is using |
|
|
766 | them. This means that AnyEvent will automatically pick the right backend |
|
|
767 | when the main program loads an event module before anything starts to |
|
|
768 | create watchers. Nothing special needs to be done by the main program. |
|
|
769 | |
|
|
770 | AnyEvent::Impl::Glib based on Glib, slow but very stable. |
|
|
771 | AnyEvent::Impl::Tk based on Tk, very broken. |
|
|
772 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
|
|
773 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
|
|
774 | |
|
|
775 | =item Backends with special needs. |
|
|
776 | |
|
|
777 | Qt requires the Qt::Application to be instantiated first, but will |
|
|
778 | otherwise be picked up automatically. As long as the main program |
|
|
779 | instantiates the application before any AnyEvent watchers are created, |
|
|
780 | everything should just work. |
|
|
781 | |
|
|
782 | AnyEvent::Impl::Qt based on Qt. |
|
|
783 | |
|
|
784 | Support for IO::Async can only be partial, as it is too broken and |
|
|
785 | architecturally limited to even support the AnyEvent API. It also |
|
|
786 | is the only event loop that needs the loop to be set explicitly, so |
|
|
787 | it can only be used by a main program knowing about AnyEvent. See |
|
|
788 | L<AnyEvent::Impl::Async> for the gory details. |
|
|
789 | |
|
|
790 | AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed. |
|
|
791 | |
|
|
792 | =item Event loops that are indirectly supported via other backends. |
|
|
793 | |
|
|
794 | Some event loops can be supported via other modules: |
|
|
795 | |
|
|
796 | There is no direct support for WxWidgets (L<Wx>) or L<Prima>. |
|
|
797 | |
|
|
798 | B<WxWidgets> has no support for watching file handles. However, you can |
|
|
799 | use WxWidgets through the POE adaptor, as POE has a Wx backend that simply |
|
|
800 | polls 20 times per second, which was considered to be too horrible to even |
|
|
801 | consider for AnyEvent. |
|
|
802 | |
|
|
803 | B<Prima> is not supported as nobody seems to be using it, but it has a POE |
|
|
804 | backend, so it can be supported through POE. |
|
|
805 | |
|
|
806 | AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to |
|
|
807 | load L<POE> when detecting them, in the hope that POE will pick them up, |
|
|
808 | in which case everything will be automatic. |
|
|
809 | |
|
|
810 | =back |
|
|
811 | |
716 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
812 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
717 | |
813 | |
|
|
814 | These are not normally required to use AnyEvent, but can be useful to |
|
|
815 | write AnyEvent extension modules. |
|
|
816 | |
718 | =over 4 |
817 | =over 4 |
719 | |
818 | |
720 | =item $AnyEvent::MODEL |
819 | =item $AnyEvent::MODEL |
721 | |
820 | |
722 | Contains C<undef> until the first watcher is being created. Then it |
821 | Contains C<undef> until the first watcher is being created, before the |
|
|
822 | backend has been autodetected. |
|
|
823 | |
723 | contains the event model that is being used, which is the name of the |
824 | Afterwards it contains the event model that is being used, which is the |
724 | Perl class implementing the model. This class is usually one of the |
825 | name of the Perl class implementing the model. This class is usually one |
725 | C<AnyEvent::Impl:xxx> modules, but can be any other class in the case |
826 | of the C<AnyEvent::Impl:xxx> modules, but can be any other class in the |
726 | AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). |
827 | case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it |
727 | |
828 | will be C<urxvt::anyevent>). |
728 | The known classes so far are: |
|
|
729 | |
|
|
730 | AnyEvent::Impl::EV based on EV (an interface to libev, best choice). |
|
|
731 | AnyEvent::Impl::Event based on Event, second best choice. |
|
|
732 | AnyEvent::Impl::Perl pure-perl implementation, fast and portable. |
|
|
733 | AnyEvent::Impl::Glib based on Glib, third-best choice. |
|
|
734 | AnyEvent::Impl::Tk based on Tk, very bad choice. |
|
|
735 | AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs). |
|
|
736 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
|
|
737 | AnyEvent::Impl::POE based on POE, not generic enough for full support. |
|
|
738 | |
|
|
739 | # warning, support for IO::Async is only partial, as it is too broken |
|
|
740 | # and limited toe ven support the AnyEvent API. See AnyEvent::Impl::Async. |
|
|
741 | AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed (see its docs). |
|
|
742 | |
|
|
743 | There is no support for WxWidgets, as WxWidgets has no support for |
|
|
744 | watching file handles. However, you can use WxWidgets through the |
|
|
745 | POE Adaptor, as POE has a Wx backend that simply polls 20 times per |
|
|
746 | second, which was considered to be too horrible to even consider for |
|
|
747 | AnyEvent. Likewise, other POE backends can be used by AnyEvent by using |
|
|
748 | it's adaptor. |
|
|
749 | |
|
|
750 | AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when |
|
|
751 | autodetecting them. |
|
|
752 | |
829 | |
753 | =item AnyEvent::detect |
830 | =item AnyEvent::detect |
754 | |
831 | |
755 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model |
832 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model |
756 | if necessary. You should only call this function right before you would |
833 | if necessary. You should only call this function right before you would |
757 | have created an AnyEvent watcher anyway, that is, as late as possible at |
834 | have created an AnyEvent watcher anyway, that is, as late as possible at |
758 | runtime. |
835 | runtime, and not e.g. while initialising of your module. |
|
|
836 | |
|
|
837 | If you need to do some initialisation before AnyEvent watchers are |
|
|
838 | created, use C<post_detect>. |
759 | |
839 | |
760 | =item $guard = AnyEvent::post_detect { BLOCK } |
840 | =item $guard = AnyEvent::post_detect { BLOCK } |
761 | |
841 | |
762 | Arranges for the code block to be executed as soon as the event model is |
842 | Arranges for the code block to be executed as soon as the event model is |
763 | autodetected (or immediately if this has already happened). |
843 | autodetected (or immediately if this has already happened). |
|
|
844 | |
|
|
845 | The block will be executed I<after> the actual backend has been detected |
|
|
846 | (C<$AnyEvent::MODEL> is set), but I<before> any watchers have been |
|
|
847 | created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do |
|
|
848 | other initialisations - see the sources of L<AnyEvent::Strict> or |
|
|
849 | L<AnyEvent::AIO> to see how this is used. |
|
|
850 | |
|
|
851 | The most common usage is to create some global watchers, without forcing |
|
|
852 | event module detection too early, for example, L<AnyEvent::AIO> creates |
|
|
853 | and installs the global L<IO::AIO> watcher in a C<post_detect> block to |
|
|
854 | avoid autodetecting the event module at load time. |
764 | |
855 | |
765 | If called in scalar or list context, then it creates and returns an object |
856 | If called in scalar or list context, then it creates and returns an object |
766 | that automatically removes the callback again when it is destroyed. See |
857 | that automatically removes the callback again when it is destroyed. See |
767 | L<Coro::BDB> for a case where this is useful. |
858 | L<Coro::BDB> for a case where this is useful. |
768 | |
859 | |
… | |
… | |
771 | If there are any code references in this array (you can C<push> to it |
862 | If there are any code references in this array (you can C<push> to it |
772 | before or after loading AnyEvent), then they will called directly after |
863 | before or after loading AnyEvent), then they will called directly after |
773 | the event loop has been chosen. |
864 | the event loop has been chosen. |
774 | |
865 | |
775 | You should check C<$AnyEvent::MODEL> before adding to this array, though: |
866 | You should check C<$AnyEvent::MODEL> before adding to this array, though: |
776 | if it contains a true value then the event loop has already been detected, |
867 | if it is defined then the event loop has already been detected, and the |
777 | and the array will be ignored. |
868 | array will be ignored. |
778 | |
869 | |
779 | Best use C<AnyEvent::post_detect { BLOCK }> instead. |
870 | Best use C<AnyEvent::post_detect { BLOCK }> when your application allows |
|
|
871 | it,as it takes care of these details. |
|
|
872 | |
|
|
873 | This variable is mainly useful for modules that can do something useful |
|
|
874 | when AnyEvent is used and thus want to know when it is initialised, but do |
|
|
875 | not need to even load it by default. This array provides the means to hook |
|
|
876 | into AnyEvent passively, without loading it. |
780 | |
877 | |
781 | =back |
878 | =back |
782 | |
879 | |
783 | =head1 WHAT TO DO IN A MODULE |
880 | =head1 WHAT TO DO IN A MODULE |
784 | |
881 | |
… | |
… | |
839 | |
936 | |
840 | |
937 | |
841 | =head1 OTHER MODULES |
938 | =head1 OTHER MODULES |
842 | |
939 | |
843 | The following is a non-exhaustive list of additional modules that use |
940 | The following is a non-exhaustive list of additional modules that use |
844 | AnyEvent and can therefore be mixed easily with other AnyEvent modules |
941 | AnyEvent as a client and can therefore be mixed easily with other AnyEvent |
845 | in the same program. Some of the modules come with AnyEvent, some are |
942 | modules and other event loops in the same program. Some of the modules |
846 | available via CPAN. |
943 | come with AnyEvent, most are available via CPAN. |
847 | |
944 | |
848 | =over 4 |
945 | =over 4 |
849 | |
946 | |
850 | =item L<AnyEvent::Util> |
947 | =item L<AnyEvent::Util> |
851 | |
948 | |
… | |
… | |
860 | |
957 | |
861 | =item L<AnyEvent::Handle> |
958 | =item L<AnyEvent::Handle> |
862 | |
959 | |
863 | Provide read and write buffers, manages watchers for reads and writes, |
960 | Provide read and write buffers, manages watchers for reads and writes, |
864 | supports raw and formatted I/O, I/O queued and fully transparent and |
961 | supports raw and formatted I/O, I/O queued and fully transparent and |
865 | non-blocking SSL/TLS. |
962 | non-blocking SSL/TLS (via L<AnyEvent::TLS>. |
866 | |
963 | |
867 | =item L<AnyEvent::DNS> |
964 | =item L<AnyEvent::DNS> |
868 | |
965 | |
869 | Provides rich asynchronous DNS resolver capabilities. |
966 | Provides rich asynchronous DNS resolver capabilities. |
870 | |
967 | |
… | |
… | |
898 | |
995 | |
899 | =item L<AnyEvent::GPSD> |
996 | =item L<AnyEvent::GPSD> |
900 | |
997 | |
901 | A non-blocking interface to gpsd, a daemon delivering GPS information. |
998 | A non-blocking interface to gpsd, a daemon delivering GPS information. |
902 | |
999 | |
|
|
1000 | =item L<AnyEvent::IRC> |
|
|
1001 | |
|
|
1002 | AnyEvent based IRC client module family (replacing the older Net::IRC3). |
|
|
1003 | |
|
|
1004 | =item L<AnyEvent::XMPP> |
|
|
1005 | |
|
|
1006 | AnyEvent based XMPP (Jabber protocol) module family (replacing the older |
|
|
1007 | Net::XMPP2>. |
|
|
1008 | |
903 | =item L<AnyEvent::IGS> |
1009 | =item L<AnyEvent::IGS> |
904 | |
1010 | |
905 | A non-blocking interface to the Internet Go Server protocol (used by |
1011 | A non-blocking interface to the Internet Go Server protocol (used by |
906 | L<App::IGS>). |
1012 | L<App::IGS>). |
907 | |
1013 | |
908 | =item L<AnyEvent::IRC> |
|
|
909 | |
|
|
910 | AnyEvent based IRC client module family (replacing the older Net::IRC3). |
|
|
911 | |
|
|
912 | =item L<Net::XMPP2> |
|
|
913 | |
|
|
914 | AnyEvent based XMPP (Jabber protocol) module family. |
|
|
915 | |
|
|
916 | =item L<Net::FCP> |
1014 | =item L<Net::FCP> |
917 | |
1015 | |
918 | AnyEvent-based implementation of the Freenet Client Protocol, birthplace |
1016 | AnyEvent-based implementation of the Freenet Client Protocol, birthplace |
919 | of AnyEvent. |
1017 | of AnyEvent. |
920 | |
1018 | |
… | |
… | |
924 | |
1022 | |
925 | =item L<Coro> |
1023 | =item L<Coro> |
926 | |
1024 | |
927 | Has special support for AnyEvent via L<Coro::AnyEvent>. |
1025 | Has special support for AnyEvent via L<Coro::AnyEvent>. |
928 | |
1026 | |
929 | =item L<IO::Lambda> |
|
|
930 | |
|
|
931 | The lambda approach to I/O - don't ask, look there. Can use AnyEvent. |
|
|
932 | |
|
|
933 | =back |
1027 | =back |
934 | |
1028 | |
935 | =cut |
1029 | =cut |
936 | |
1030 | |
937 | package AnyEvent; |
1031 | package AnyEvent; |
… | |
… | |
939 | no warnings; |
1033 | no warnings; |
940 | use strict qw(vars subs); |
1034 | use strict qw(vars subs); |
941 | |
1035 | |
942 | use Carp; |
1036 | use Carp; |
943 | |
1037 | |
944 | our $VERSION = 4.412; |
1038 | our $VERSION = 4.801; |
945 | our $MODEL; |
1039 | our $MODEL; |
946 | |
1040 | |
947 | our $AUTOLOAD; |
1041 | our $AUTOLOAD; |
948 | our @ISA; |
1042 | our @ISA; |
949 | |
1043 | |
… | |
… | |
975 | [Event:: => AnyEvent::Impl::Event::], |
1069 | [Event:: => AnyEvent::Impl::Event::], |
976 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
1070 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
977 | # everything below here will not be autoprobed |
1071 | # everything below here will not be autoprobed |
978 | # as the pureperl backend should work everywhere |
1072 | # as the pureperl backend should work everywhere |
979 | # and is usually faster |
1073 | # and is usually faster |
980 | [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles |
|
|
981 | [Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers |
1074 | [Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers |
982 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
1075 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
|
|
1076 | [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles |
|
|
1077 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
983 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
1078 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
984 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
|
|
985 | [Wx:: => AnyEvent::Impl::POE::], |
1079 | [Wx:: => AnyEvent::Impl::POE::], |
986 | [Prima:: => AnyEvent::Impl::POE::], |
1080 | [Prima:: => AnyEvent::Impl::POE::], |
987 | # IO::Async is just too broken - we would need workaorunds for its |
1081 | # IO::Async is just too broken - we would need workarounds for its |
988 | # byzantine signal and broken child handling, among others. |
1082 | # byzantine signal and broken child handling, among others. |
989 | # IO::Async is rather hard to detect, as it doesn't have any |
1083 | # IO::Async is rather hard to detect, as it doesn't have any |
990 | # obvious default class. |
1084 | # obvious default class. |
991 | # [IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program |
1085 | # [IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program |
992 | # [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program |
1086 | # [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program |
… | |
… | |
1094 | # allow only one watcher per fd, so we dup it to get a different one). |
1188 | # allow only one watcher per fd, so we dup it to get a different one). |
1095 | sub _dupfh($$;$$) { |
1189 | sub _dupfh($$;$$) { |
1096 | my ($poll, $fh, $r, $w) = @_; |
1190 | my ($poll, $fh, $r, $w) = @_; |
1097 | |
1191 | |
1098 | # cygwin requires the fh mode to be matching, unix doesn't |
1192 | # cygwin requires the fh mode to be matching, unix doesn't |
1099 | my ($rw, $mode) = $poll eq "r" ? ($r, "<") |
1193 | my ($rw, $mode) = $poll eq "r" ? ($r, "<") : ($w, ">"); |
1100 | : $poll eq "w" ? ($w, ">") |
|
|
1101 | : Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'"; |
|
|
1102 | |
1194 | |
1103 | open my $fh2, "$mode&" . fileno $fh |
1195 | open my $fh2, "$mode&", $fh |
1104 | or die "cannot dup() filehandle: $!,"; |
1196 | or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,"; |
1105 | |
1197 | |
1106 | # we assume CLOEXEC is already set by perl in all important cases |
1198 | # we assume CLOEXEC is already set by perl in all important cases |
1107 | |
1199 | |
1108 | ($fh2, $rw) |
1200 | ($fh2, $rw) |
1109 | } |
1201 | } |
… | |
… | |
1441 | |
1533 | |
1442 | =item C<PERL_ANYEVENT_MAX_FORKS> |
1534 | =item C<PERL_ANYEVENT_MAX_FORKS> |
1443 | |
1535 | |
1444 | The maximum number of child processes that C<AnyEvent::Util::fork_call> |
1536 | The maximum number of child processes that C<AnyEvent::Util::fork_call> |
1445 | will create in parallel. |
1537 | will create in parallel. |
|
|
1538 | |
|
|
1539 | =item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS> |
|
|
1540 | |
|
|
1541 | The default value for the C<max_outstanding> parameter for the default DNS |
|
|
1542 | resolver - this is the maximum number of parallel DNS requests that are |
|
|
1543 | sent to the DNS server. |
|
|
1544 | |
|
|
1545 | =item C<PERL_ANYEVENT_RESOLV_CONF> |
|
|
1546 | |
|
|
1547 | The file to use instead of F</etc/resolv.conf> (or OS-specific |
|
|
1548 | configuration) in the default resolver. When set to the empty string, no |
|
|
1549 | default config will be used. |
|
|
1550 | |
|
|
1551 | =item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>. |
|
|
1552 | |
|
|
1553 | When neither C<ca_file> nor C<ca_path> was specified during |
|
|
1554 | L<AnyEvent::TLS> context creation, and either of these environment |
|
|
1555 | variables exist, they will be used to specify CA certificate locations |
|
|
1556 | instead of a system-dependent default. |
1446 | |
1557 | |
1447 | =back |
1558 | =back |
1448 | |
1559 | |
1449 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
1560 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
1450 | |
1561 | |
… | |
… | |
2073 | L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. |
2184 | L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. |
2074 | |
2185 | |
2075 | Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, |
2186 | Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, |
2076 | L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, |
2187 | L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, |
2077 | L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, |
2188 | L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, |
2078 | L<AnyEvent::Impl::POE>. |
2189 | L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>. |
2079 | |
2190 | |
2080 | Non-blocking file handles, sockets, TCP clients and |
2191 | Non-blocking file handles, sockets, TCP clients and |
2081 | servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>. |
2192 | servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>. |
2082 | |
2193 | |
2083 | Asynchronous DNS: L<AnyEvent::DNS>. |
2194 | Asynchronous DNS: L<AnyEvent::DNS>. |
2084 | |
2195 | |
2085 | Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>, |
2196 | Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, |
|
|
2197 | L<Coro::Event>, |
2086 | |
2198 | |
2087 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. |
2199 | Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>, |
|
|
2200 | L<AnyEvent::HTTP>. |
2088 | |
2201 | |
2089 | |
2202 | |
2090 | =head1 AUTHOR |
2203 | =head1 AUTHOR |
2091 | |
2204 | |
2092 | Marc Lehmann <schmorp@schmorp.de> |
2205 | Marc Lehmann <schmorp@schmorp.de> |