[ViewVC] Diff of: cvs/AnyEvent/README

Comparing AnyEvent/README (file contents):
Revision 1.64 by root, Fri Dec 31 04:50:44 2010 UTC vs.
Revision 1.75 by root, Thu Jul 16 12:48:38 2015 UTC

…		…
1	NAME	1	NAME
2	AnyEvent - the DBI of event loop programming	2	AnyEvent - the DBI of event loop programming
3		3
4	EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async,	4	EV, Event, Glib, Tk, UV, Perl, Event::Lib, Irssi, rxvt-unicode,
5	Qt and POE are various supported event loops/environments.	5	IO::Async, Qt, FLTK and POE are various supported event
		6	loops/environments.
6		7
7	SYNOPSIS	8	SYNOPSIS
8	use AnyEvent;	9	use AnyEvent;
9		10
10	# if you prefer function calls, look at the AE manpage for	11	# if you prefer function calls, look at the AE manpage for
115	The interface itself is vaguely similar, but not identical to the Event	116	The interface itself is vaguely similar, but not identical to the Event
116	module.	117	module.
117		118
118	During the first call of any watcher-creation method, the module tries	119	During the first call of any watcher-creation method, the module tries
119	to detect the currently loaded event loop by probing whether one of the	120	to detect the currently loaded event loop by probing whether one of the
120	following modules is already loaded: EV, AnyEvent::Impl::Perl, Event,	121	following modules is already loaded: EV, AnyEvent::Loop, Event, Glib,
121	Glib, Tk, Event::Lib, Qt, POE. The first one found is used. If none are	122	Tk, Event::Lib, Qt, POE. The first one found is used. If none are
122	detected, the module tries to load the first four modules in the order	123	detected, the module tries to load the first four modules in the order
123	given; but note that if EV is not available, the pure-perl	124	given; but note that if EV is not available, the pure-perl
124	AnyEvent::Impl::Perl should always work, so the other two are not	125	AnyEvent::Loop should always work, so the other two are not normally
125	normally tried.	126	tried.
126		127
127	Because AnyEvent first checks for modules that are already loaded,	128	Because AnyEvent first checks for modules that are already loaded,
128	loading an event model explicitly before first using AnyEvent will	129	loading an event model explicitly before first using AnyEvent will
129	likely make that model the default. For example:	130	likely make that model the default. For example:
130		131
…		…
136	The likely means that, if any module loads another event model and	137	The likely means that, if any module loads another event model and
137	starts using it, all bets are off - this case should be very rare	138	starts using it, all bets are off - this case should be very rare
138	though, as very few modules hardcode event loops without announcing this	139	though, as very few modules hardcode event loops without announcing this
139	very loudly.	140	very loudly.
140		141
141	The pure-perl implementation of AnyEvent is called	142	The pure-perl implementation of AnyEvent is called "AnyEvent::Loop".
142	"AnyEvent::Impl::Perl". Like other event modules you can load it	143	Like other event modules you can load it explicitly and enjoy the high
143	explicitly and enjoy the high availability of that event loop :)	144	availability of that event loop :)
144		145
145	WATCHERS	146	WATCHERS
146	AnyEvent has the central concept of a watcher, which is an object that	147	AnyEvent has the central concept of a watcher, which is an object that
147	stores relevant data for each kind of event you are waiting for, such as	148	stores relevant data for each kind of event you are waiting for, such as
148	the callback to call, the file handle to watch, etc.	149	the callback to call, the file handle to watch, etc.
…		…
262		263
263	Example 2: fire an event after 0.5 seconds, then roughly every second.	264	Example 2: fire an event after 0.5 seconds, then roughly every second.
264		265
265	my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {	266	my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
266	warn "timeout\n";	267	warn "timeout\n";
267	};	268	});
268		269
269	TIMING ISSUES	270	TIMING ISSUES
270	There are two ways to handle timers: based on real time (relative, "fire	271	There are two ways to handle timers: based on real time (relative, "fire
271	in 10 seconds") and based on wallclock time (absolute, "fire at 12	272	in 10 seconds") and based on wallclock time (absolute, "fire at 12
272	o'clock").	273	o'clock").
…		…
347	can get whatever behaviour you want with any event loop, by taking	348	can get whatever behaviour you want with any event loop, by taking
348	the difference between "AnyEvent->time" and "AnyEvent->now" into	349	the difference between "AnyEvent->time" and "AnyEvent->now" into
349	account.	350	account.
350		351
351	AnyEvent->now_update	352	AnyEvent->now_update
352	Some event loops (such as EV or AnyEvent::Impl::Perl) cache the	353	Some event loops (such as EV or AnyEvent::Loop) cache the current
353	current time for each loop iteration (see the discussion of	354	time for each loop iteration (see the discussion of AnyEvent->now,
354	AnyEvent->now, above).	355	above).
355		356
356	When a callback runs for a long time (or when the process sleeps),	357	When a callback runs for a long time (or when the process sleeps),
357	then this "current" time will differ substantially from the real	358	then this "current" time will differ substantially from the real
358	time, which might affect timers and time-outs.	359	time, which might affect timers and time-outs.
359		360
…		…
403	will not restart syscalls (that includes Async::Interrupt and AnyEvent's	404	will not restart syscalls (that includes Async::Interrupt and AnyEvent's
404	pure perl implementation).	405	pure perl implementation).
405		406
406	Safe/Unsafe Signals	407	Safe/Unsafe Signals
407	Perl signals can be either "safe" (synchronous to opcode handling) or	408	Perl signals can be either "safe" (synchronous to opcode handling) or
408	"unsafe" (asynchronous) - the former might get delayed indefinitely, the	409	"unsafe" (asynchronous) - the former might delay signal delivery
409	latter might corrupt your memory.	410	indefinitely, the latter might corrupt your memory.
410		411
411	AnyEvent signal handlers are, in addition, synchronous to the event	412	AnyEvent signal handlers are, in addition, synchronous to the event
412	loop, i.e. they will not interrupt your running perl program but will	413	loop, i.e. they will not interrupt your running perl program but will
413	only be called as part of the normal event handling (just like timer,	414	only be called as part of the normal event handling (just like timer,
414	I/O etc. callbacks, too).	415	I/O etc. callbacks, too).
…		…
416	Signal Races, Delays and Workarounds	417	Signal Races, Delays and Workarounds
417	Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching	418	Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
418	callbacks to signals in a generic way, which is a pity, as you cannot do	419	callbacks to signals in a generic way, which is a pity, as you cannot do
419	race-free signal handling in perl, requiring C libraries for this.	420	race-free signal handling in perl, requiring C libraries for this.
420	AnyEvent will try to do its best, which means in some cases, signals	421	AnyEvent will try to do its best, which means in some cases, signals
421	will be delayed. The maximum time a signal might be delayed is specified	422	will be delayed. The maximum time a signal might be delayed is 10
422	in $AnyEvent::MAX_SIGNAL_LATENCY (default: 10 seconds). This variable	423	seconds by default, but can be overriden via
423	can be changed only before the first signal watcher is created, and	424	$ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY} or $AnyEvent::MAX_SIGNAL_LATENCY
424	should be left alone otherwise. This variable determines how often	425	- see the "ENVIRONMENT VARIABLES" section for details.
425	AnyEvent polls for signals (in case a wake-up was missed). Higher values
426	will cause fewer spurious wake-ups, which is better for power and CPU
427	saving.
428		426
429	All these problems can be avoided by installing the optional	427	All these problems can be avoided by installing the optional
430	Async::Interrupt module, which works with most event loops. It will not	428	Async::Interrupt module, which works with most event loops. It will not
431	work with inherently broken event loops such as Event or Event::Lib (and	429	work with inherently broken event loops such as Event or Event::Lib (and
432	not with POE currently, as POE does its own workaround with one-second
433	latency). For those, you just have to suffer the delays.	430	not with POE currently). For those, you just have to suffer the delays.
434		431
435	CHILD PROCESS WATCHERS	432	CHILD PROCESS WATCHERS
436	$w = AnyEvent->child (pid => <process id>, cb => <callback>);	433	$w = AnyEvent->child (pid => <process id>, cb => <callback>);
437		434
438	You can also watch for a child process exit and catch its exit status.	435	You can also watch for a child process exit and catch its exit status.
…		…
466	This means you cannot create a child watcher as the very first thing in	463	This means you cannot create a child watcher as the very first thing in
467	an AnyEvent program, you have to create at least one watcher before	464	an AnyEvent program, you have to create at least one watcher before
468	you "fork" the child (alternatively, you can call "AnyEvent::detect").	465	you "fork" the child (alternatively, you can call "AnyEvent::detect").
469		466
470	As most event loops do not support waiting for child events, they will	467	As most event loops do not support waiting for child events, they will
471	be emulated by AnyEvent in most cases, in which the latency and race	468	be emulated by AnyEvent in most cases, in which case the latency and
472	problems mentioned in the description of signal watchers apply.	469	race problems mentioned in the description of signal watchers apply.
473		470
474	Example: fork a process and wait for it	471	Example: fork a process and wait for it
475		472
476	my $done = AnyEvent->condvar;	473	my $done = AnyEvent->condvar;
477		474
		475	# this forks and immediately calls exit in the child. this
		476	# normally has all sorts of bad consequences for your parent,
		477	# so take this as an example only. always fork and exec,
		478	# or call POSIX::_exit, in real code.
478	my $pid = fork or exit 5;	479	my $pid = fork or exit 5;
479		480
480	my $w = AnyEvent->child (	481	my $w = AnyEvent->child (
481	pid => $pid,	482	pid => $pid,
482	cb => sub {	483	cb => sub {
…		…
722	This works because for every event source (EOF on file handle),	723	This works because for every event source (EOF on file handle),
723	there is one call to "begin", so the condvar waits for all calls to	724	there is one call to "begin", so the condvar waits for all calls to
724	"end" before sending.	725	"end" before sending.
725		726
726	The ping example mentioned above is slightly more complicated, as	727	The ping example mentioned above is slightly more complicated, as
727	the there are results to be passwd back, and the number of tasks	728	the there are results to be passed back, and the number of tasks
728	that are begun can potentially be zero:	729	that are begun can potentially be zero:
729		730
730	my $cv = AnyEvent->condvar;	731	my $cv = AnyEvent->condvar;
731		732
732	my %result;	733	my %result;
…		…
740	};	741	};
741	}	742	}
742		743
743	$cv->end;	744	$cv->end;
744		745
		746	...
		747
		748	my $results = $cv->recv;
		749
745	This code fragment supposedly pings a number of hosts and calls	750	This code fragment supposedly pings a number of hosts and calls
746	"send" after results for all then have have been gathered - in any	751	"send" after results for all then have have been gathered - in any
747	order. To achieve this, the code issues a call to "begin" when it	752	order. To achieve this, the code issues a call to "begin" when it
748	starts each ping request and calls "end" when it has received some	753	starts each ping request and calls "end" when it has received some
749	result for it. Since "begin" and "end" only maintain a counter, the	754	result for it. Since "begin" and "end" only maintain a counter, the
…		…
778	In list context, all parameters passed to "send" will be returned,	783	In list context, all parameters passed to "send" will be returned,
779	in scalar context only the first one will be returned.	784	in scalar context only the first one will be returned.
780		785
781	Note that doing a blocking wait in a callback is not supported by	786	Note that doing a blocking wait in a callback is not supported by
782	any event loop, that is, recursive invocation of a blocking "->recv"	787	any event loop, that is, recursive invocation of a blocking "->recv"
783	is not allowed, and the "recv" call will "croak" if such a condition	788	is not allowed and the "recv" call will "croak" if such a condition
784	is detected. This condition can be slightly loosened by using	789	is detected. This requirement can be dropped by relying on
785	Coro::AnyEvent, which allows you to do a blocking "->recv" from any	790	Coro::AnyEvent , which allows you to do a blocking "->recv" from any
786	thread that doesn't run the event loop itself.	791	thread that doesn't run the event loop itself. Coro::AnyEvent is
		792	loaded automatically when Coro is used with AnyEvent, so code does
		793	not need to do anything special to take advantage of that: any code
		794	that would normally block your program because it calls "recv", be
		795	executed in an "async" thread instead without blocking other
		796	threads.
787		797
788	Not all event models support a blocking wait - some die in that case	798	Not all event models support a blocking wait - some die in that case
789	(programs might want to do that to stay interactive), so *if you are	799	(programs might want to do that to stay interactive), so *if you are
790	using this from a module, never require a blocking wait*. Instead,	800	using this from a module, never require a blocking wait*. Instead,
791	let the caller decide whether the call will block or not (for	801	let the caller decide whether the call will block or not (for
…		…
821	use. If EV is not installed, then AnyEvent will fall back to its own	831	use. If EV is not installed, then AnyEvent will fall back to its own
822	pure-perl implementation, which is available everywhere as it comes	832	pure-perl implementation, which is available everywhere as it comes
823	with AnyEvent itself.	833	with AnyEvent itself.
824		834
825	AnyEvent::Impl::EV based on EV (interface to libev, best choice).	835	AnyEvent::Impl::EV based on EV (interface to libev, best choice).
826	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.	836	AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
827		837
828	Backends that are transparently being picked up when they are used.	838	Backends that are transparently being picked up when they are used.
829	These will be used if they are already loaded when the first watcher	839	These will be used if they are already loaded when the first watcher
830	is created, in which case it is assumed that the application is	840	is created, in which case it is assumed that the application is
831	using them. This means that AnyEvent will automatically pick the	841	using them. This means that AnyEvent will automatically pick the
…		…
834	by the main program.	844	by the main program.
835		845
836	AnyEvent::Impl::Event based on Event, very stable, few glitches.	846	AnyEvent::Impl::Event based on Event, very stable, few glitches.
837	AnyEvent::Impl::Glib based on Glib, slow but very stable.	847	AnyEvent::Impl::Glib based on Glib, slow but very stable.
838	AnyEvent::Impl::Tk based on Tk, very broken.	848	AnyEvent::Impl::Tk based on Tk, very broken.
		849	AnyEvent::Impl::UV based on UV, innovated square wheels.
839	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.	850	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
840	AnyEvent::Impl::POE based on POE, very slow, some limitations.	851	AnyEvent::Impl::POE based on POE, very slow, some limitations.
841	AnyEvent::Impl::Irssi used when running within irssi.	852	AnyEvent::Impl::Irssi used when running within irssi.
842	AnyEvent::Impl::IOAsync based on IO::Async.	853	AnyEvent::Impl::IOAsync based on IO::Async.
843	AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.	854	AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
		855	AnyEvent::Impl::FLTK based on FLTK (fltk 2 binding).
844		856
845	Backends with special needs.	857	Backends with special needs.
846	Qt requires the Qt::Application to be instantiated first, but will	858	Qt requires the Qt::Application to be instantiated first, but will
847	otherwise be picked up automatically. As long as the main program	859	otherwise be picked up automatically. As long as the main program
848	instantiates the application before any AnyEvent watchers are	860	instantiates the application before any AnyEvent watchers are
…		…
885	Returns $AnyEvent::MODEL, forcing autodetection of the event model	897	Returns $AnyEvent::MODEL, forcing autodetection of the event model
886	if necessary. You should only call this function right before you	898	if necessary. You should only call this function right before you
887	would have created an AnyEvent watcher anyway, that is, as late as	899	would have created an AnyEvent watcher anyway, that is, as late as
888	possible at runtime, and not e.g. during initialisation of your	900	possible at runtime, and not e.g. during initialisation of your
889	module.	901	module.
		902
		903	The effect of calling this function is as if a watcher had been
		904	created (specifically, actions that happen "when the first watcher
		905	is created" happen when calling detetc as well).
890		906
891	If you need to do some initialisation before AnyEvent watchers are	907	If you need to do some initialisation before AnyEvent watchers are
892	created, use "post_detect".	908	created, use "post_detect".
893		909
894	$guard = AnyEvent::post_detect { BLOCK }	910	$guard = AnyEvent::post_detect { BLOCK }
…		…
956	# AnyEvent not yet initialised, so make sure to load Coro::AnyEvent	972	# AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
957	# as soon as it is	973	# as soon as it is
958	push @AnyEvent::post_detect, sub { require Coro::AnyEvent };	974	push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
959	}	975	}
960		976
		977	AnyEvent::postpone { BLOCK }
		978	Arranges for the block to be executed as soon as possible, but not
		979	before the call itself returns. In practise, the block will be
		980	executed just before the event loop polls for new events, or shortly
		981	afterwards.
		982
		983	This function never returns anything (to make the "return postpone {
		984	... }" idiom more useful.
		985
		986	To understand the usefulness of this function, consider a function
		987	that asynchronously does something for you and returns some
		988	transaction object or guard to let you cancel the operation. For
		989	example, "AnyEvent::Socket::tcp_connect":
		990
		991	# start a connection attempt unless one is active
		992	$self->{connect_guard} \|\|= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
		993	delete $self->{connect_guard};
		994	...
		995	};
		996
		997	Imagine that this function could instantly call the callback, for
		998	example, because it detects an obvious error such as a negative port
		999	number. Invoking the callback before the function returns causes
		1000	problems however: the callback will be called and will try to delete
		1001	the guard object. But since the function hasn't returned yet, there
		1002	is nothing to delete. When the function eventually returns it will
		1003	assign the guard object to "$self->{connect_guard}", where it will
		1004	likely never be deleted, so the program thinks it is still trying to
		1005	connect.
		1006
		1007	This is where "AnyEvent::postpone" should be used. Instead of
		1008	calling the callback directly on error:
		1009
		1010	$cb->(undef), return # signal error to callback, BAD!
		1011	if $some_error_condition;
		1012
		1013	It should use "postpone":
		1014
		1015	AnyEvent::postpone { $cb->(undef) }, return # signal error to callback, later
		1016	if $some_error_condition;
		1017
		1018	AnyEvent::log $level, $msg[, @args]
		1019	Log the given $msg at the given $level.
		1020
		1021	If AnyEvent::Log is not loaded then this function makes a simple
		1022	test to see whether the message will be logged. If the test succeeds
		1023	it will load AnyEvent::Log and call "AnyEvent::Log::log" -
		1024	consequently, look at the AnyEvent::Log documentation for details.
		1025
		1026	If the test fails it will simply return. Right now this happens when
		1027	a numerical loglevel is used and it is larger than the level
		1028	specified via $ENV{PERL_ANYEVENT_VERBOSE}.
		1029
		1030	If you want to sprinkle loads of logging calls around your code,
		1031	consider creating a logger callback with the "AnyEvent::Log::logger"
		1032	function, which can reduce typing, codesize and can reduce the
		1033	logging overhead enourmously.
		1034
		1035	AnyEvent::fh_block $filehandle
		1036	AnyEvent::fh_unblock $filehandle
		1037	Sets blocking or non-blocking behaviour for the given filehandle.
		1038
961	WHAT TO DO IN A MODULE	1039	WHAT TO DO IN A MODULE
962	As a module author, you should "use AnyEvent" and call AnyEvent methods	1040	As a module author, you should "use AnyEvent" and call AnyEvent methods
963	freely, but you should not load a specific event module or rely on it.	1041	freely, but you should not load a specific event module or rely on it.
964		1042
965	Be careful when you create watchers in the module body - AnyEvent will	1043	Be careful when you create watchers in the module body - AnyEvent will
…		…
995	will decide on the event model to use as soon as it creates watchers,	1073	will decide on the event model to use as soon as it creates watchers,
996	and it might choose the wrong one unless you load the correct one	1074	and it might choose the wrong one unless you load the correct one
997	yourself.	1075	yourself.
998		1076
999	You can chose to use a pure-perl implementation by loading the	1077	You can chose to use a pure-perl implementation by loading the
1000	"AnyEvent::Impl::Perl" module, which gives you similar behaviour	1078	"AnyEvent::Loop" module, which gives you similar behaviour everywhere,
1001	everywhere, but letting AnyEvent chose the model is generally better.	1079	but letting AnyEvent chose the model is generally better.
1002		1080
1003	MAINLOOP EMULATION	1081	MAINLOOP EMULATION
1004	Sometimes (often for short test scripts, or even standalone programs who	1082	Sometimes (often for short test scripts, or even standalone programs who
1005	only want to use AnyEvent), you do not want to run a specific event	1083	only want to use AnyEvent), you do not want to run a specific event
1006	loop.	1084	loop.
…		…
1018		1096
1019	OTHER MODULES	1097	OTHER MODULES
1020	The following is a non-exhaustive list of additional modules that use	1098	The following is a non-exhaustive list of additional modules that use
1021	AnyEvent as a client and can therefore be mixed easily with other	1099	AnyEvent as a client and can therefore be mixed easily with other
1022	AnyEvent modules and other event loops in the same program. Some of the	1100	AnyEvent modules and other event loops in the same program. Some of the
1023	modules come as part of AnyEvent, the others are available via CPAN.	1101	modules come as part of AnyEvent, the others are available via CPAN (see
		1102	<http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for a longer
		1103	non-exhaustive list), and the list is heavily biased towards modules of
		1104	the AnyEvent author himself :)
1024		1105
1025	AnyEvent::Util	1106	AnyEvent::Util (part of the AnyEvent distribution)
1026	Contains various utility functions that replace often-used blocking	1107	Contains various utility functions that replace often-used blocking
1027	functions such as "inet_aton" with event/callback-based versions.	1108	functions such as "inet_aton" with event/callback-based versions.
1028		1109
1029	AnyEvent::Socket	1110	AnyEvent::Socket (part of the AnyEvent distribution)
1030	Provides various utility functions for (internet protocol) sockets,	1111	Provides various utility functions for (internet protocol) sockets,
1031	addresses and name resolution. Also functions to create non-blocking	1112	addresses and name resolution. Also functions to create non-blocking
1032	tcp connections or tcp servers, with IPv6 and SRV record support and	1113	tcp connections or tcp servers, with IPv6 and SRV record support and
1033	more.	1114	more.
1034		1115
1035	AnyEvent::Handle	1116	AnyEvent::Handle (part of the AnyEvent distribution)
1036	Provide read and write buffers, manages watchers for reads and	1117	Provide read and write buffers, manages watchers for reads and
1037	writes, supports raw and formatted I/O, I/O queued and fully	1118	writes, supports raw and formatted I/O, I/O queued and fully
1038	transparent and non-blocking SSL/TLS (via AnyEvent::TLS).	1119	transparent and non-blocking SSL/TLS (via AnyEvent::TLS).
1039		1120
1040	AnyEvent::DNS	1121	AnyEvent::DNS (part of the AnyEvent distribution)
1041	Provides rich asynchronous DNS resolver capabilities.	1122	Provides rich asynchronous DNS resolver capabilities.
1042		1123
1043	AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD,	1124	AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD,
1044	AnyEvent::IGS, AnyEvent::FCP	1125	AnyEvent::IGS, AnyEvent::FCP
1045	Implement event-based interfaces to the protocols of the same name	1126	Implement event-based interfaces to the protocols of the same name
1046	(for the curious, IGS is the International Go Server and FCP is the	1127	(for the curious, IGS is the International Go Server and FCP is the
1047	Freenet Client Protocol).	1128	Freenet Client Protocol).
1048		1129
1049	AnyEvent::Handle::UDP	1130	AnyEvent::AIO (part of the AnyEvent distribution)
1050	Here be danger!
1051
1052	As Pauli would put it, "Not only is it not right, it's not even
1053	wrong!" - there are so many things wrong with AnyEvent::Handle::UDP,
1054	most notably its use of a stream-based API with a protocol that
1055	isn't streamable, that the only way to improve it is to delete it.
1056
1057	It features data corruption (but typically only under load) and
1058	general confusion. On top, the author is not only clueless about UDP
1059	but also fact-resistant - some gems of his understanding: "connect
1060	doesn't work with UDP", "UDP packets are not IP packets", "UDP only
1061	has datagrams, not packets", "I don't need to implement proper error
1062	checking as UDP doesn't support error checking" and so on - he
1063	doesn't even understand what's wrong with his module when it is
1064	explained to him.
1065
1066	AnyEvent::DBI
1067	Executes DBI requests asynchronously in a proxy process for you,
1068	notifying you in an event-based way when the operation is finished.
1069
1070	AnyEvent::AIO
1071	Truly asynchronous (as opposed to non-blocking) I/O, should be in	1131	Truly asynchronous (as opposed to non-blocking) I/O, should be in
1072	the toolbox of every event programmer. AnyEvent::AIO transparently	1132	the toolbox of every event programmer. AnyEvent::AIO transparently
1073	fuses IO::AIO and AnyEvent together, giving AnyEvent access to	1133	fuses IO::AIO and AnyEvent together, giving AnyEvent access to
1074	event-based file I/O, and much more.	1134	event-based file I/O, and much more.
1075		1135
		1136	AnyEvent::Fork, AnyEvent::Fork::RPC, AnyEvent::Fork::Pool,
		1137	AnyEvent::Fork::Remote
		1138	These let you safely fork new subprocesses, either locally or
		1139	remotely (e.g.v ia ssh), using some RPC protocol or not, without the
		1140	limitations normally imposed by fork (AnyEvent works fine for
		1141	example). Dynamically-resized worker pools are obviously included as
		1142	well.
		1143
		1144	And they are quite tiny and fast as well - "abusing" AnyEvent::Fork
		1145	just to exec external programs can easily beat using "fork" and
		1146	"exec" (or even "system") in most programs.
		1147
		1148	AnyEvent::Filesys::Notify
		1149	AnyEvent is good for non-blocking stuff, but it can't detect file or
		1150	path changes (e.g. "watch this directory for new files", "watch this
		1151	file for changes"). The AnyEvent::Filesys::Notify module promises to
		1152	do just that in a portbale fashion, supporting inotify on GNU/Linux
		1153	and some weird, without doubt broken, stuff on OS X to monitor
		1154	files. It can fall back to blocking scans at regular intervals
		1155	transparently on other platforms, so it's about as portable as it
		1156	gets.
		1157
		1158	(I haven't used it myself, but it seems the biggest problem with it
		1159	is it quite bad performance).
		1160
1076	AnyEvent::HTTPD	1161	AnyEvent::DBI
1077	A simple embedded webserver.	1162	Executes DBI requests asynchronously in a proxy process for you,
		1163	notifying you in an event-based way when the operation is finished.
1078		1164
1079	AnyEvent::FastPing	1165	AnyEvent::FastPing
1080	The fastest ping in the west.	1166	The fastest ping in the west.
1081		1167
1082	Coro	1168	Coro
1083	Has special support for AnyEvent via Coro::AnyEvent.	1169	Has special support for AnyEvent via Coro::AnyEvent, which allows
		1170	you to simply invert the flow control - don't call us, we will call
		1171	you:
		1172
		1173	async {
		1174	Coro::AnyEvent::sleep 5; # creates a 5s timer and waits for it
		1175	print "5 seconds later!\n";
		1176
		1177	Coro::AnyEvent::readable *STDIN; # uses an I/O watcher
		1178	my $line = <STDIN>; # works for ttys
		1179
		1180	AnyEvent::HTTP::http_get "url", Coro::rouse_cb;
		1181	my ($body, $hdr) = Coro::rouse_wait;
		1182	};
1084		1183
1085	SIMPLIFIED AE API	1184	SIMPLIFIED AE API
1086	Starting with version 5.0, AnyEvent officially supports a second, much	1185	Starting with version 5.0, AnyEvent officially supports a second, much
1087	simpler, API that is designed to reduce the calling, typing and memory	1186	simpler, API that is designed to reduce the calling, typing and memory
1088	overhead by using function call syntax and a fixed number of parameters.	1187	overhead by using function call syntax and a fixed number of parameters.
…		…
1104	The pure perl event loop simply re-throws the exception (usually within	1203	The pure perl event loop simply re-throws the exception (usually within
1105	"condvar->recv"), the Event and EV modules call "$Event/EV::DIED->()",	1204	"condvar->recv"), the Event and EV modules call "$Event/EV::DIED->()",
1106	Glib uses "install_exception_handler" and so on.	1205	Glib uses "install_exception_handler" and so on.
1107		1206
1108	ENVIRONMENT VARIABLES	1207	ENVIRONMENT VARIABLES
1109	The following environment variables are used by this module or its	1208	AnyEvent supports a number of environment variables that tune the
1110	submodules.	1209	runtime behaviour. They are usually evaluated when AnyEvent is loaded,
		1210	initialised, or a submodule that uses them is loaded. Many of them also
		1211	cause AnyEvent to load additional modules - for example,
		1212	"PERL_ANYEVENT_DEBUG_WRAP" causes the AnyEvent::Debug module to be
		1213	loaded.
1111		1214
1112	Note that AnyEvent will remove all environment variables starting with	1215	All the environment variables documented here start with
1113	"PERL_ANYEVENT_" from %ENV when it is loaded while taint mode is	1216	"PERL_ANYEVENT_", which is what AnyEvent considers its own namespace.
1114	enabled.	1217	Other modules are encouraged (but by no means required) to use
		1218	"PERL_ANYEVENT_SUBMODULE" if they have registered the
		1219	AnyEvent::Submodule namespace on CPAN, for any submodule. For example,
		1220	AnyEvent::HTTP could be expected to use "PERL_ANYEVENT_HTTP_PROXY" (it
		1221	should not access env variables starting with "AE_", see below).
		1222
		1223	All variables can also be set via the "AE_" prefix, that is, instead of
		1224	setting "PERL_ANYEVENT_VERBOSE" you can also set "AE_VERBOSE". In case
		1225	there is a clash btween anyevent and another program that uses
		1226	"AE_something" you can set the corresponding "PERL_ANYEVENT_something"
		1227	variable to the empty string, as those variables take precedence.
		1228
		1229	When AnyEvent is first loaded, it copies all "AE_xxx" env variables to
		1230	their "PERL_ANYEVENT_xxx" counterpart unless that variable already
		1231	exists. If taint mode is on, then AnyEvent will remove all environment
		1232	variables starting with "PERL_ANYEVENT_" from %ENV (or replace them with
		1233	"undef" or the empty string, if the corresaponding "AE_" variable is
		1234	set).
		1235
		1236	The exact algorithm is currently:
		1237
		1238	1. if taint mode enabled, delete all PERL_ANYEVENT_xyz variables from %ENV
		1239	2. copy over AE_xyz to PERL_ANYEVENT_xyz unless the latter alraedy exists
		1240	3. if taint mode enabled, set all PERL_ANYEVENT_xyz variables to undef.
		1241
		1242	This ensures that child processes will not see the "AE_" variables.
		1243
		1244	The following environment variables are currently known to AnyEvent:
1115		1245
1116	"PERL_ANYEVENT_VERBOSE"	1246	"PERL_ANYEVENT_VERBOSE"
1117	By default, AnyEvent will be completely silent except in fatal	1247	By default, AnyEvent will log messages with loglevel 4 ("error") or
1118	conditions. You can set this environment variable to make AnyEvent	1248	higher (see AnyEvent::Log). You can set this environment variable to
1119	more talkative.	1249	a numerical loglevel to make AnyEvent more (or less) talkative.
1120		1250
		1251	If you want to do more than just set the global logging level you
		1252	should have a look at "PERL_ANYEVENT_LOG", which allows much more
		1253	complex specifications.
		1254
		1255	When set to 0 ("off"), then no messages whatsoever will be logged
		1256	with everything else at defaults.
		1257
1121	When set to 1 or higher, causes AnyEvent to warn about unexpected	1258	When set to 5 or higher ("warn"), AnyEvent warns about unexpected
1122	conditions, such as not being able to load the event model specified	1259	conditions, such as not being able to load the event model specified
1123	by "PERL_ANYEVENT_MODEL".	1260	by "PERL_ANYEVENT_MODEL", or a guard callback throwing an exception
		1261	- this is the minimum recommended level for use during development.
1124		1262
1125	When set to 2 or higher, cause AnyEvent to report to STDERR which	1263	When set to 7 or higher (info), AnyEvent reports which event model
1126	event model it chooses.	1264	it chooses.
1127		1265
1128	When set to 8 or higher, then AnyEvent will report extra information	1266	When set to 8 or higher (debug), then AnyEvent will report extra
1129	on which optional modules it loads and how it implements certain	1267	information on which optional modules it loads and how it implements
1130	features.	1268	certain features.
		1269
		1270	"PERL_ANYEVENT_LOG"
		1271	Accepts rather complex logging specifications. For example, you
		1272	could log all "debug" messages of some module to stderr, warnings
		1273	and above to stderr, and errors and above to syslog, with:
		1274
		1275	PERL_ANYEVENT_LOG=Some::Module=debug,+log:filter=warn,+%syslog:%syslog=error,syslog
		1276
		1277	For the rather extensive details, see AnyEvent::Log.
		1278
		1279	This variable is evaluated when AnyEvent (or AnyEvent::Log) is
		1280	loaded, so will take effect even before AnyEvent has initialised
		1281	itself.
		1282
		1283	Note that specifying this environment variable causes the
		1284	AnyEvent::Log module to be loaded, while "PERL_ANYEVENT_VERBOSE"
		1285	does not, so only using the latter saves a few hundred kB of memory
		1286	unless a module explicitly needs the extra features of
		1287	AnyEvent::Log.
1131		1288
1132	"PERL_ANYEVENT_STRICT"	1289	"PERL_ANYEVENT_STRICT"
1133	AnyEvent does not do much argument checking by default, as thorough	1290	AnyEvent does not do much argument checking by default, as thorough
1134	argument checking is very costly. Setting this variable to a true	1291	argument checking is very costly. Setting this variable to a true
1135	value will cause AnyEvent to load "AnyEvent::Strict" and then to	1292	value will cause AnyEvent to load "AnyEvent::Strict" and then to
…		…
1141	Unlike "use strict" (or its modern cousin, "use common::sense", it	1298	Unlike "use strict" (or its modern cousin, "use common::sense", it
1142	is definitely recommended to keep it off in production. Keeping	1299	is definitely recommended to keep it off in production. Keeping
1143	"PERL_ANYEVENT_STRICT=1" in your environment while developing	1300	"PERL_ANYEVENT_STRICT=1" in your environment while developing
1144	programs can be very useful, however.	1301	programs can be very useful, however.
1145		1302
		1303	"PERL_ANYEVENT_DEBUG_SHELL"
		1304	If this env variable is nonempty, then its contents will be
		1305	interpreted by "AnyEvent::Socket::parse_hostport" and
		1306	"AnyEvent::Debug::shell" (after replacing every occurance of $$ by
		1307	the process pid). The shell object is saved in
		1308	$AnyEvent::Debug::SHELL.
		1309
		1310	This happens when the first watcher is created.
		1311
		1312	For example, to bind a debug shell on a unix domain socket in
		1313	/tmp/debug<pid>.sock, you could use this:
		1314
		1315	PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog
		1316	# connect with e.g.: socat readline /tmp/debug123.sock
		1317
		1318	Or to bind to tcp port 4545 on localhost:
		1319
		1320	PERL_ANYEVENT_DEBUG_SHELL=127.0.0.1:4545 perlprog
		1321	# connect with e.g.: telnet localhost 4545
		1322
		1323	Note that creating sockets in /tmp or on localhost is very unsafe on
		1324	multiuser systems.
		1325
		1326	"PERL_ANYEVENT_DEBUG_WRAP"
		1327	Can be set to 0, 1 or 2 and enables wrapping of all watchers for
		1328	debugging purposes. See "AnyEvent::Debug::wrap" for details.
		1329
1146	"PERL_ANYEVENT_MODEL"	1330	"PERL_ANYEVENT_MODEL"
1147	This can be used to specify the event model to be used by AnyEvent,	1331	This can be used to specify the event model to be used by AnyEvent,
1148	before auto detection and -probing kicks in. It must be a string	1332	before auto detection and -probing kicks in.
1149	consisting entirely of ASCII letters. The string "AnyEvent::Impl::"	1333
1150	gets prepended and the resulting module name is loaded and if the	1334	It normally is a string consisting entirely of ASCII letters (e.g.
1151	load was successful, used as event model. If it fails to load	1335	"EV" or "IOAsync"). The string "AnyEvent::Impl::" gets prepended and
		1336	the resulting module name is loaded and - if the load was successful
		1337	- used as event model backend. If it fails to load then AnyEvent
1152	AnyEvent will proceed with auto detection and -probing.	1338	will proceed with auto detection and -probing.
1153		1339
1154	This functionality might change in future versions.	1340	If the string ends with "::" instead (e.g. "AnyEvent::Impl::EV::")
		1341	then nothing gets prepended and the module name is used as-is (hint:
		1342	"::" at the end of a string designates a module name and quotes it
		1343	appropriately).
1155		1344
1156	For example, to force the pure perl model (AnyEvent::Impl::Perl) you	1345	For example, to force the pure perl model (AnyEvent::Loop::Perl) you
1157	could start your program like this:	1346	could start your program like this:
1158		1347
1159	PERL_ANYEVENT_MODEL=Perl perl ...	1348	PERL_ANYEVENT_MODEL=Perl perl ...
		1349
		1350	"PERL_ANYEVENT_IO_MODEL"
		1351	The current file I/O model - see AnyEvent::IO for more info.
		1352
		1353	At the moment, only "Perl" (small, pure-perl, synchronous) and
		1354	"IOAIO" (truly asynchronous) are supported. The default is "IOAIO"
		1355	if AnyEvent::AIO can be loaded, otherwise it is "Perl".
1160		1356
1161	"PERL_ANYEVENT_PROTOCOLS"	1357	"PERL_ANYEVENT_PROTOCOLS"
1162	Used by both AnyEvent::DNS and AnyEvent::Socket to determine	1358	Used by both AnyEvent::DNS and AnyEvent::Socket to determine
1163	preferences for IPv4 or IPv6. The default is unspecified (and might	1359	preferences for IPv4 or IPv6. The default is unspecified (and might
1164	change, or be the result of auto probing).	1360	change, or be the result of auto probing).
…		…
1168	mentioned will be used, and preference will be given to protocols	1364	mentioned will be used, and preference will be given to protocols
1169	mentioned earlier in the list.	1365	mentioned earlier in the list.
1170		1366
1171	This variable can effectively be used for denial-of-service attacks	1367	This variable can effectively be used for denial-of-service attacks
1172	against local programs (e.g. when setuid), although the impact is	1368	against local programs (e.g. when setuid), although the impact is
1173	likely small, as the program has to handle conenction and other	1369	likely small, as the program has to handle connection and other
1174	failures anyways.	1370	failures anyways.
1175		1371
1176	Examples: "PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6" - prefer IPv4 over	1372	Examples: "PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6" - prefer IPv4 over
1177	IPv6, but support both and try to use both.	1373	IPv6, but support both and try to use both.
1178	"PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to	1374	"PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to
1179	resolve or contact IPv6 addresses.	1375	resolve or contact IPv6 addresses.
1180	"PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4" support either IPv4 or IPv6, but	1376	"PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4" support either IPv4 or IPv6, but
1181	prefer IPv6 over IPv4.	1377	prefer IPv6 over IPv4.
1182		1378
		1379	"PERL_ANYEVENT_HOSTS"
		1380	This variable, if specified, overrides the /etc/hosts file used by
		1381	AnyEvent::Socket"::resolve_sockaddr", i.e. hosts aliases will be
		1382	read from that file instead.
		1383
1183	"PERL_ANYEVENT_EDNS0"	1384	"PERL_ANYEVENT_EDNS0"
1184	Used by AnyEvent::DNS to decide whether to use the EDNS0 extension	1385	Used by AnyEvent::DNS to decide whether to use the EDNS0 extension
1185	for DNS. This extension is generally useful to reduce DNS traffic,	1386	for DNS. This extension is generally useful to reduce DNS traffic,
1186	but some (broken) firewalls drop such DNS packets, which is why it	1387	especially when DNSSEC is involved, but some (broken) firewalls drop
1187	is off by default.	1388	such DNS packets, which is why it is off by default.
1188		1389
1189	Setting this variable to 1 will cause AnyEvent::DNS to announce	1390	Setting this variable to 1 will cause AnyEvent::DNS to announce
1190	EDNS0 in its DNS requests.	1391	EDNS0 in its DNS requests.
1191		1392
1192	"PERL_ANYEVENT_MAX_FORKS"	1393	"PERL_ANYEVENT_MAX_FORKS"
…		…
1196	"PERL_ANYEVENT_MAX_OUTSTANDING_DNS"	1397	"PERL_ANYEVENT_MAX_OUTSTANDING_DNS"
1197	The default value for the "max_outstanding" parameter for the	1398	The default value for the "max_outstanding" parameter for the
1198	default DNS resolver - this is the maximum number of parallel DNS	1399	default DNS resolver - this is the maximum number of parallel DNS
1199	requests that are sent to the DNS server.	1400	requests that are sent to the DNS server.
1200		1401
		1402	"PERL_ANYEVENT_MAX_SIGNAL_LATENCY"
		1403	Perl has inherently racy signal handling (you can basically choose
		1404	between losing signals and memory corruption) - pure perl event
		1405	loops (including "AnyEvent::Loop", when "Async::Interrupt" isn't
		1406	available) therefore have to poll regularly to avoid losing signals.
		1407
		1408	Some event loops are racy, but don't poll regularly, and some event
		1409	loops are written in C but are still racy. For those event loops,
		1410	AnyEvent installs a timer that regularly wakes up the event loop.
		1411
		1412	By default, the interval for this timer is 10 seconds, but you can
		1413	override this delay with this environment variable (or by setting
		1414	the $AnyEvent::MAX_SIGNAL_LATENCY variable before creating signal
		1415	watchers).
		1416
		1417	Lower values increase CPU (and energy) usage, higher values can
		1418	introduce long delays when reaping children or waiting for signals.
		1419
		1420	The AnyEvent::Async module, if available, will be used to avoid this
		1421	polling (with most event loops).
		1422
1201	"PERL_ANYEVENT_RESOLV_CONF"	1423	"PERL_ANYEVENT_RESOLV_CONF"
1202	The file to use instead of /etc/resolv.conf (or OS-specific	1424	The absolute path to a resolv.conf-style file to use instead of
1203	configuration) in the default resolver. When set to the empty	1425	/etc/resolv.conf (or the OS-specific configuration) in the default
1204	string, no default config will be used.	1426	resolver, or the empty string to select the default configuration.
1205		1427
1206	"PERL_ANYEVENT_CA_FILE", "PERL_ANYEVENT_CA_PATH".	1428	"PERL_ANYEVENT_CA_FILE", "PERL_ANYEVENT_CA_PATH".
1207	When neither "ca_file" nor "ca_path" was specified during	1429	When neither "ca_file" nor "ca_path" was specified during
1208	AnyEvent::TLS context creation, and either of these environment	1430	AnyEvent::TLS context creation, and either of these environment
1209	variables exist, they will be used to specify CA certificate	1431	variables are nonempty, they will be used to specify CA certificate
1210	locations instead of a system-dependent default.	1432	locations instead of a system-dependent default.
1211		1433
1212	"PERL_ANYEVENT_AVOID_GUARD" and "PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT"	1434	"PERL_ANYEVENT_AVOID_GUARD" and "PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT"
1213	When these are set to 1, then the respective modules are not loaded.	1435	When these are set to 1, then the respective modules are not loaded.
1214	Mostly good for testing AnyEvent itself.	1436	Mostly good for testing AnyEvent itself.
…		…
1534	when used without AnyEvent), but most event loops have acceptable	1756	when used without AnyEvent), but most event loops have acceptable
1535	performance with or without AnyEvent.	1757	performance with or without AnyEvent.
1536		1758
1537	* The overhead AnyEvent adds is usually much smaller than the overhead	1759	* The overhead AnyEvent adds is usually much smaller than the overhead
1538	of the actual event loop, only with extremely fast event loops such	1760	of the actual event loop, only with extremely fast event loops such
1539	as EV adds AnyEvent significant overhead.	1761	as EV does AnyEvent add significant overhead.
1540		1762
1541	* You should avoid POE like the plague if you want performance or	1763	* You should avoid POE like the plague if you want performance or
1542	reasonable memory usage.	1764	reasonable memory usage.
1543		1765
1544	BENCHMARKING THE LARGE SERVER CASE	1766	BENCHMARKING THE LARGE SERVER CASE
…		…
1804	the help of AnyEvent::TLS), gains the ability to do TLS/SSL.	2026	the help of AnyEvent::TLS), gains the ability to do TLS/SSL.
1805		2027
1806	Time::HiRes	2028	Time::HiRes
1807	This module is part of perl since release 5.008. It will be used	2029	This module is part of perl since release 5.008. It will be used
1808	when the chosen event library does not come with a timing source of	2030	when the chosen event library does not come with a timing source of
1809	its own. The pure-perl event loop (AnyEvent::Impl::Perl) will	2031	its own. The pure-perl event loop (AnyEvent::Loop) will additionally
1810	additionally use it to try to use a monotonic clock for timing	2032	load it to try to use a monotonic clock for timing stability.
1811	stability.	2033
		2034	AnyEvent::AIO (and IO::AIO)
		2035	The default implementation of AnyEvent::IO is to do I/O
		2036	synchronously, stopping programs while they access the disk, which
		2037	is fine for a lot of programs.
		2038
		2039	Installing AnyEvent::AIO (and its IO::AIO dependency) makes it
		2040	switch to a true asynchronous implementation, so event processing
		2041	can continue even while waiting for disk I/O.
1812		2042
1813	FORK	2043	FORK
1814	Most event libraries are not fork-safe. The ones who are usually are	2044	Most event libraries are not fork-safe. The ones who are usually are
1815	because they rely on inefficient but fork-safe "select" or "poll" calls	2045	because they rely on inefficient but fork-safe "select" or "poll" calls
1816	- higher performance APIs such as BSD's kqueue or the dreaded Linux	2046	- higher performance APIs such as BSD's kqueue or the dreaded Linux
…		…
1824	usually happens when the first AnyEvent watcher is created, or the	2054	usually happens when the first AnyEvent watcher is created, or the
1825	library is loaded).	2055	library is loaded).
1826		2056
1827	If you have to fork, you must either do so before creating your first	2057	If you have to fork, you must either do so before creating your first
1828	watcher OR you must not use AnyEvent at all in the child OR you must do	2058	watcher OR you must not use AnyEvent at all in the child OR you must do
1829	something completely out of the scope of AnyEvent.	2059	something completely out of the scope of AnyEvent (see below).
1830		2060
1831	The problem of doing event processing in the parent and the child is	2061	The problem of doing event processing in the parent and the child is
1832	much more complicated: even for backends that are fork-aware or	2062	much more complicated: even for backends that are fork-aware or
1833	fork-safe, their behaviour is not usually what you want: fork clones all	2063	fork-safe, their behaviour is not usually what you want: fork clones all
1834	watchers, that means all timers, I/O watchers etc. are active in both	2064	watchers, that means all timers, I/O watchers etc. are active in both
1835	parent and child, which is almost never what you want. USing "exec" to	2065	parent and child, which is almost never what you want. Using "exec" to
1836	start worker children from some kind of manage rprocess is usually	2066	start worker children from some kind of manage prrocess is usually
1837	preferred, because it is much easier and cleaner, at the expense of	2067	preferred, because it is much easier and cleaner, at the expense of
1838	having to have another binary.	2068	having to have another binary.
		2069
		2070	In addition to logical problems with fork, there are also implementation
		2071	problems. For example, on POSIX systems, you cannot fork at all in Perl
		2072	code if a thread (I am talking of pthreads here) was ever created in the
		2073	process, and this is just the tip of the iceberg. In general, using fork
		2074	from Perl is difficult, and attempting to use fork without an exec to
		2075	implement some kind of parallel processing is almost certainly doomed.
		2076
		2077	To safely fork and exec, you should use a module such as Proc::FastSpawn
		2078	that let's you safely fork and exec new processes.
		2079
		2080	If you want to do multiprocessing using processes, you can look at the
		2081	AnyEvent::Fork module (and some related modules such as
		2082	AnyEvent::Fork::RPC, AnyEvent::Fork::Pool and AnyEvent::Fork::Remote).
		2083	This module allows you to safely create subprocesses without any
		2084	limitations - you can use X11 toolkits or AnyEvent in the children
		2085	created by AnyEvent::Fork safely and without any special precautions.
1839		2086
1840	SECURITY CONSIDERATIONS	2087	SECURITY CONSIDERATIONS
1841	AnyEvent can be forced to load any event model via	2088	AnyEvent can be forced to load any event model via
1842	$ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used	2089	$ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used
1843	to execute arbitrary code or directly gain access, it can easily be used	2090	to execute arbitrary code or directly gain access, it can easily be used
…		…
1871	SEE ALSO	2118	SEE ALSO
1872	Tutorial/Introduction: AnyEvent::Intro.	2119	Tutorial/Introduction: AnyEvent::Intro.
1873		2120
1874	FAQ: AnyEvent::FAQ.	2121	FAQ: AnyEvent::FAQ.
1875		2122
1876	Utility functions: AnyEvent::Util.	2123	Utility functions: AnyEvent::Util (misc. grab-bag), AnyEvent::Log
		2124	(simply logging).
1877		2125
1878	Event modules: EV, EV::Glib, Glib::EV, Event, Glib::Event, Glib, Tk,	2126	Development/Debugging: AnyEvent::Strict (stricter checking),
1879	Event::Lib, Qt, POE.	2127	AnyEvent::Debug (interactive shell, watcher tracing).
		2128
		2129	Supported event modules: AnyEvent::Loop, EV, EV::Glib, Glib::EV, Event,
		2130	Glib::Event, Glib, Tk, Event::Lib, Qt, POE, FLTK, Cocoa::EventLoop, UV.
1880		2131
1881	Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event,	2132	Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event,
1882	AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl,	2133	AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl,
1883	AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE,	2134	AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE,
		2135	AnyEvent::Impl::IOAsync, AnyEvent::Impl::Irssi, AnyEvent::Impl::FLTK,
1884	AnyEvent::Impl::IOAsync, Anyevent::Impl::Irssi.	2136	AnyEvent::Impl::Cocoa, AnyEvent::Impl::UV.
1885		2137
1886	Non-blocking file handles, sockets, TCP clients and servers:	2138	Non-blocking handles, pipes, stream sockets, TCP clients and servers:
1887	AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS.	2139	AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS.
		2140
		2141	Asynchronous File I/O: AnyEvent::IO.
1888		2142
1889	Asynchronous DNS: AnyEvent::DNS.	2143	Asynchronous DNS: AnyEvent::DNS.
1890		2144
1891	Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event.	2145	Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event.
1892		2146
1893	Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::IRC,	2147	Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::IRC,
1894	AnyEvent::HTTP.	2148	AnyEvent::HTTP.
1895		2149
1896	AUTHOR	2150	AUTHOR
1897	Marc Lehmann <schmorp@schmorp.de>	2151	Marc Lehmann <schmorp@schmorp.de>
1898	http://home.schmorp.de/	2152	http://anyevent.schmorp.de
1899		2153

Diff Legend

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

Comparing AnyEvent/README (file contents): Revision 1.64 by root, Fri Dec 31 04:50:44 2010 UTC vs. Revision 1.75 by root, Thu Jul 16 12:48:38 2015 UTC

Diff Legend

Comparing AnyEvent/README (file contents):
Revision 1.64 by root, Fri Dec 31 04:50:44 2010 UTC vs.
Revision 1.75 by root, Thu Jul 16 12:48:38 2015 UTC