ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent/Handle.pm

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.95 by root, Thu Oct 2 06:42:39 2008 UTC vs.
Revision 1.237 by root, Tue Jul 30 23:14:32 2013 UTC

1	package AnyEvent::Handle;
2
3	no warnings;
4	use strict qw(subs vars);
5
6	use AnyEvent ();
7	use AnyEvent::Util qw(WSAEWOULDBLOCK);
8	use Scalar::Util ();
9	use Carp ();
10	use Fcntl ();
11	use Errno qw(EAGAIN EINTR);
12
13	=head1 NAME	1	=head1 NAME
14		2
15	AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent	3	AnyEvent::Handle - non-blocking I/O on streaming handles via AnyEvent
16
17	=cut
18
19	our $VERSION = 4.3;
20		4
21	=head1 SYNOPSIS	5	=head1 SYNOPSIS
22		6
23	use AnyEvent;	7	use AnyEvent;
24	use AnyEvent::Handle;	8	use AnyEvent::Handle;
25		9
26	my $cv = AnyEvent->condvar;	10	my $cv = AnyEvent->condvar;
27		11
28	my $handle =	12	my $hdl; $hdl = new AnyEvent::Handle
29	AnyEvent::Handle->new (
30	fh => \*STDIN,	13	fh => \*STDIN,
31	on_eof => sub {	14	on_error => sub {
32	$cv->broadcast;	15	my ($hdl, $fatal, $msg) = @_;
33	},	16	AE::log error => $msg;
		17	$hdl->destroy;
		18	$cv->send;
34	);	19	};
35		20
36	# send some request line	21	# send some request line
37	$handle->push_write ("getinfo\015\012");	22	$hdl->push_write ("getinfo\015\012");
38		23
39	# read the response line	24	# read the response line
40	$handle->push_read (line => sub {	25	$hdl->push_read (line => sub {
41	my ($handle, $line) = @_;	26	my ($hdl, $line) = @_;
42	warn "read line <$line>\n";	27	say "got line <$line>";
43	$cv->send;	28	$cv->send;
44	});	29	});
45		30
46	$cv->recv;	31	$cv->recv;
47		32
48	=head1 DESCRIPTION	33	=head1 DESCRIPTION
49		34
50	This module is a helper module to make it easier to do event-based I/O on	35	This is a helper module to make it easier to do event-based I/O on
51	filehandles. For utility functions for doing non-blocking connects and accepts	36	stream-based filehandles (sockets, pipes, and other stream things).
52	on sockets see L<AnyEvent::Util>.
53		37
54	The L<AnyEvent::Intro> tutorial contains some well-documented	38	The L<AnyEvent::Intro> tutorial contains some well-documented
55	AnyEvent::Handle examples.	39	AnyEvent::Handle examples.
56		40
57	In the following, when the documentation refers to of "bytes" then this	41	In the following, where the documentation refers to "bytes", it means
58	means characters. As sysread and syswrite are used for all I/O, their	42	characters. As sysread and syswrite are used for all I/O, their
59	treatment of characters applies to this module as well.	43	treatment of characters applies to this module as well.
		44
		45	At the very minimum, you should specify C<fh> or C<connect>, and the
		46	C<on_error> callback.
60		47
61	All callbacks will be invoked with the handle object as their first	48	All callbacks will be invoked with the handle object as their first
62	argument.	49	argument.
63		50
64	=head2 SIGPIPE is not handled by this module	51	=cut
65		52
66	SIGPIPE is not handled by this module, so one of the practical	53	package AnyEvent::Handle;
67	requirements of using it is to ignore SIGPIPE (C<$SIG{PIPE} =	54
68	'IGNORE'>). At least, this is highly recommend in a networked program: If	55	use Scalar::Util ();
69	you use AnyEvent::Handle in a filter program (like sort), exiting on	56	use List::Util ();
70	SIGPIPE is probably the right thing to do.	57	use Carp ();
		58	use Errno qw(EAGAIN EINTR);
		59
		60	use AnyEvent (); BEGIN { AnyEvent::common_sense }
		61	use AnyEvent::Util qw(WSAEWOULDBLOCK);
		62
		63	our $VERSION = $AnyEvent::VERSION;
		64
		65	sub _load_func($) {
		66	my $func = $_[0];
		67
		68	unless (defined &$func) {
		69	my $pkg = $func;
		70	do {
		71	$pkg =~ s/::[^:]+$//
		72	or return;
		73	eval "require $pkg";
		74	} until defined &$func;
		75	}
		76
		77	\&$func
		78	}
		79
		80	sub MAX_READ_SIZE() { 131072 }
71		81
72	=head1 METHODS	82	=head1 METHODS
73		83
74	=over 4	84	=over 4
75		85
76	=item B<new (%args)>	86	=item $handle = B<new> AnyEvent::Handle fh => $filehandle, key => value...
77		87
78	The constructor supports these arguments (all as key => value pairs).	88	The constructor supports these arguments (all as C<< key => value >> pairs).
79		89
80	=over 4	90	=over 4
81		91
82	=item fh => $filehandle [MANDATORY]	92	=item fh => $filehandle [C<fh> or C<connect> MANDATORY]
83		93
84	The filehandle this L<AnyEvent::Handle> object will operate on.	94	The filehandle this L<AnyEvent::Handle> object will operate on.
85
86	NOTE: The filehandle will be set to non-blocking mode (using	95	NOTE: The filehandle will be set to non-blocking mode (using
87	C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in	96	C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in
88	that mode.	97	that mode.
89		98
		99	=item connect => [$host, $service] [C<fh> or C<connect> MANDATORY]
		100
		101	Try to connect to the specified host and service (port), using
		102	C<AnyEvent::Socket::tcp_connect>. The C<$host> additionally becomes the
		103	default C<peername>.
		104
		105	You have to specify either this parameter, or C<fh>, above.
		106
		107	It is possible to push requests on the read and write queues, and modify
		108	properties of the stream, even while AnyEvent::Handle is connecting.
		109
		110	When this parameter is specified, then the C<on_prepare>,
		111	C<on_connect_error> and C<on_connect> callbacks will be called under the
		112	appropriate circumstances:
		113
		114	=over 4
		115
90	=item on_eof => $cb->($handle)	116	=item on_prepare => $cb->($handle)
91		117
92	Set the callback to be called when an end-of-file condition is detected,	118	This (rarely used) callback is called before a new connection is
93	i.e. in the case of a socket, when the other side has closed the	119	attempted, but after the file handle has been created (you can access that
94	connection cleanly.	120	file handle via C<< $handle->{fh} >>). It could be used to prepare the
		121	file handle with parameters required for the actual connect (as opposed to
		122	settings that can be changed when the connection is already established).
95		123
96	For sockets, this just means that the other side has stopped sending data,	124	The return value of this callback should be the connect timeout value in
97	you can still try to write data, and, in fact, one can return from the eof	125	seconds (or C<0>, or C<undef>, or the empty list, to indicate that the
98	callback and continue writing data, as only the read part has been shut	126	default timeout is to be used).
99	down.
100		127
101	While not mandatory, it is I<highly> recommended to set an eof callback,	128	=item on_connect => $cb->($handle, $host, $port, $retry->())
102	otherwise you might end up with a closed socket while you are still
103	waiting for data.
104		129
105	If an EOF condition has been detected but no C<on_eof> callback has been	130	This callback is called when a connection has been successfully established.
106	set, then a fatal error will be raised with C<$!> set to <0>.
107		131
		132	The peer's numeric host and port (the socket peername) are passed as
		133	parameters, together with a retry callback. At the time it is called the
		134	read and write queues, EOF status, TLS status and similar properties of
		135	the handle will have been reset.
		136
		137	It is not allowed to use the read or write queues while the handle object
		138	is connecting.
		139
		140	If, for some reason, the handle is not acceptable, calling C<$retry> will
		141	continue with the next connection target (in case of multi-homed hosts or
		142	SRV records there can be multiple connection endpoints). The C<$retry>
		143	callback can be invoked after the connect callback returns, i.e. one can
		144	start a handshake and then decide to retry with the next host if the
		145	handshake fails.
		146
		147	In most cases, you should ignore the C<$retry> parameter.
		148
		149	=item on_connect_error => $cb->($handle, $message)
		150
		151	This callback is called when the connection could not be
		152	established. C<$!> will contain the relevant error code, and C<$message> a
		153	message describing it (usually the same as C<"$!">).
		154
		155	If this callback isn't specified, then C<on_error> will be called with a
		156	fatal error instead.
		157
		158	=back
		159
108	=item on_error => $cb->($handle, $fatal)	160	=item on_error => $cb->($handle, $fatal, $message)
109		161
110	This is the error callback, which is called when, well, some error	162	This is the error callback, which is called when, well, some error
111	occured, such as not being able to resolve the hostname, failure to	163	occured, such as not being able to resolve the hostname, failure to
112	connect or a read error.	164	connect, or a read error.
113		165
114	Some errors are fatal (which is indicated by C<$fatal> being true). On	166	Some errors are fatal (which is indicated by C<$fatal> being true). On
115	fatal errors the handle object will be shut down and will not be usable	167	fatal errors the handle object will be destroyed (by a call to C<< ->
116	(but you are free to look at the current C<< ->rbuf >>). Examples of fatal	168	destroy >>) after invoking the error callback (which means you are free to
117	errors are an EOF condition with active (but unsatisifable) read watchers	169	examine the handle object). Examples of fatal errors are an EOF condition
118	(C<EPIPE>) or I/O errors.	170	with active (but unsatisfiable) read watchers (C<EPIPE>) or I/O errors. In
		171	cases where the other side can close the connection at will, it is
		172	often easiest to not report C<EPIPE> errors in this callback.
119		173
		174	AnyEvent::Handle tries to find an appropriate error code for you to check
		175	against, but in some cases (TLS errors), this does not work well.
		176
		177	If you report the error to the user, it is recommended to always output
		178	the C<$message> argument in human-readable error messages (you don't need
		179	to report C<"$!"> if you report C<$message>).
		180
		181	If you want to react programmatically to the error, then looking at C<$!>
		182	and comparing it against some of the documented C<Errno> values is usually
		183	better than looking at the C<$message>.
		184
120	Non-fatal errors can be retried by simply returning, but it is recommended	185	Non-fatal errors can be retried by returning, but it is recommended
121	to simply ignore this parameter and instead abondon the handle object	186	to simply ignore this parameter and instead abondon the handle object
122	when this callback is invoked. Examples of non-fatal errors are timeouts	187	when this callback is invoked. Examples of non-fatal errors are timeouts
123	C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).	188	C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
124		189
125	On callback entrance, the value of C<$!> contains the operating system	190	On entry to the callback, the value of C<$!> contains the operating
126	error (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT> or C<EBADMSG>).	191	system error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
		192	C<EPROTO>).
127		193
128	While not mandatory, it is I<highly> recommended to set this callback, as	194	While not mandatory, it is I<highly> recommended to set this callback, as
129	you will not be notified of errors otherwise. The default simply calls	195	you will not be notified of errors otherwise. The default just calls
130	C<croak>.	196	C<croak>.
131		197
132	=item on_read => $cb->($handle)	198	=item on_read => $cb->($handle)
133		199
134	This sets the default read callback, which is called when data arrives	200	This sets the default read callback, which is called when data arrives
135	and no read request is in the queue (unlike read queue callbacks, this	201	and no read request is in the queue (unlike read queue callbacks, this
136	callback will only be called when at least one octet of data is in the	202	callback will only be called when at least one octet of data is in the
137	read buffer).	203	read buffer).
138		204
139	To access (and remove data from) the read buffer, use the C<< ->rbuf >>	205	To access (and remove data from) the read buffer, use the C<< ->rbuf >>
140	method or access the C<$handle->{rbuf}> member directly.	206	method or access the C<< $handle->{rbuf} >> member directly. Note that you
		207	must not enlarge or modify the read buffer, you can only remove data at
		208	the beginning from it.
141		209
		210	You can also call C<< ->push_read (...) >> or any other function that
		211	modifies the read queue. Or do both. Or ...
		212
142	When an EOF condition is detected then AnyEvent::Handle will first try to	213	When an EOF condition is detected, AnyEvent::Handle will first try to
143	feed all the remaining data to the queued callbacks and C<on_read> before	214	feed all the remaining data to the queued callbacks and C<on_read> before
144	calling the C<on_eof> callback. If no progress can be made, then a fatal	215	calling the C<on_eof> callback. If no progress can be made, then a fatal
145	error will be raised (with C<$!> set to C<EPIPE>).	216	error will be raised (with C<$!> set to C<EPIPE>).
146		217
		218	Note that, unlike requests in the read queue, an C<on_read> callback
		219	doesn't mean you I<require> some data: if there is an EOF and there
		220	are outstanding read requests then an error will be flagged. With an
		221	C<on_read> callback, the C<on_eof> callback will be invoked.
		222
		223	=item on_eof => $cb->($handle)
		224
		225	Set the callback to be called when an end-of-file condition is detected,
		226	i.e. in the case of a socket, when the other side has closed the
		227	connection cleanly, and there are no outstanding read requests in the
		228	queue (if there are read requests, then an EOF counts as an unexpected
		229	connection close and will be flagged as an error).
		230
		231	For sockets, this just means that the other side has stopped sending data,
		232	you can still try to write data, and, in fact, one can return from the EOF
		233	callback and continue writing data, as only the read part has been shut
		234	down.
		235
		236	If an EOF condition has been detected but no C<on_eof> callback has been
		237	set, then a fatal error will be raised with C<$!> set to <0>.
		238
147	=item on_drain => $cb->($handle)	239	=item on_drain => $cb->($handle)
148		240
149	This sets the callback that is called when the write buffer becomes empty	241	This sets the callback that is called once when the write buffer becomes
150	(or when the callback is set and the buffer is empty already).	242	empty (and immediately when the handle object is created).
151		243
152	To append to the write buffer, use the C<< ->push_write >> method.	244	To append to the write buffer, use the C<< ->push_write >> method.
153		245
154	This callback is useful when you don't want to put all of your write data	246	This callback is useful when you don't want to put all of your write data
155	into the queue at once, for example, when you want to write the contents	247	into the queue at once, for example, when you want to write the contents
…		…
157	memory and push it into the queue, but instead only read more data from	249	memory and push it into the queue, but instead only read more data from
158	the file when the write queue becomes empty.	250	the file when the write queue becomes empty.
159		251
160	=item timeout => $fractional_seconds	252	=item timeout => $fractional_seconds
161		253
		254	=item rtimeout => $fractional_seconds
		255
		256	=item wtimeout => $fractional_seconds
		257
162	If non-zero, then this enables an "inactivity" timeout: whenever this many	258	If non-zero, then these enables an "inactivity" timeout: whenever this
163	seconds pass without a successful read or write on the underlying file	259	many seconds pass without a successful read or write on the underlying
164	handle, the C<on_timeout> callback will be invoked (and if that one is	260	file handle (or a call to C<timeout_reset>), the C<on_timeout> callback
165	missing, a non-fatal C<ETIMEDOUT> error will be raised).	261	will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>
		262	error will be raised).
166		263
		264	There are three variants of the timeouts that work independently of each
		265	other, for both read and write (triggered when nothing was read I<OR>
		266	written), just read (triggered when nothing was read), and just write:
		267	C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks
		268	C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions
		269	C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>.
		270
167	Note that timeout processing is also active when you currently do not have	271	Note that timeout processing is active even when you do not have any
168	any outstanding read or write requests: If you plan to keep the connection	272	outstanding read or write requests: If you plan to keep the connection
169	idle then you should disable the timout temporarily or ignore the timeout	273	idle then you should disable the timeout temporarily or ignore the
170	in the C<on_timeout> callback, in which case AnyEvent::Handle will simply	274	timeout in the corresponding C<on_timeout> callback, in which case
171	restart the timeout.	275	AnyEvent::Handle will simply restart the timeout.
172		276
173	Zero (the default) disables this timeout.	277	Zero (the default) disables the corresponding timeout.
174		278
175	=item on_timeout => $cb->($handle)	279	=item on_timeout => $cb->($handle)
		280
		281	=item on_rtimeout => $cb->($handle)
		282
		283	=item on_wtimeout => $cb->($handle)
176		284
177	Called whenever the inactivity timeout passes. If you return from this	285	Called whenever the inactivity timeout passes. If you return from this
178	callback, then the timeout will be reset as if some activity had happened,	286	callback, then the timeout will be reset as if some activity had happened,
179	so this condition is not fatal in any way.	287	so this condition is not fatal in any way.
180		288
…		…
188	be configured to accept only so-and-so much data that it cannot act on	296	be configured to accept only so-and-so much data that it cannot act on
189	(for example, when expecting a line, an attacker could send an unlimited	297	(for example, when expecting a line, an attacker could send an unlimited
190	amount of data without a callback ever being called as long as the line	298	amount of data without a callback ever being called as long as the line
191	isn't finished).	299	isn't finished).
192		300
		301	=item wbuf_max => <bytes>
		302
		303	If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
		304	when the write buffer ever (strictly) exceeds this size. This is useful to
		305	avoid some forms of denial-of-service attacks.
		306
		307	Although the units of this parameter is bytes, this is the I<raw> number
		308	of bytes not yet accepted by the kernel. This can make a difference when
		309	you e.g. use TLS, as TLS typically makes your write data larger (but it
		310	can also make it smaller due to compression).
		311
		312	As an example of when this limit is useful, take a chat server that sends
		313	chat messages to a client. If the client does not read those in a timely
		314	manner then the send buffer in the server would grow unbounded.
		315
193	=item autocork => <boolean>	316	=item autocork => <boolean>
194		317
195	When disabled (the default), then C<push_write> will try to immediately	318	When disabled (the default), C<push_write> will try to immediately
196	write the data to the handle, if possible. This avoids having to register	319	write the data to the handle if possible. This avoids having to register
197	a write watcher and wait for the next event loop iteration, but can	320	a write watcher and wait for the next event loop iteration, but can
198	be inefficient if you write multiple small chunks (on the wire, this	321	be inefficient if you write multiple small chunks (on the wire, this
199	disadvantage is usually avoided by your kernel's nagle algorithm, see	322	disadvantage is usually avoided by your kernel's nagle algorithm, see
200	C<no_delay>, but this option can save costly syscalls).	323	C<no_delay>, but this option can save costly syscalls).
201		324
202	When enabled, then writes will always be queued till the next event loop	325	When enabled, writes will always be queued till the next event loop
203	iteration. This is efficient when you do many small writes per iteration,	326	iteration. This is efficient when you do many small writes per iteration,
204	but less efficient when you do a single write only per iteration (or when	327	but less efficient when you do a single write only per iteration (or when
205	the write buffer often is full). It also increases write latency.	328	the write buffer often is full). It also increases write latency.
206		329
207	=item no_delay => <boolean>	330	=item no_delay => <boolean>
…		…
211	the Nagle algorithm, and usually it is beneficial.	334	the Nagle algorithm, and usually it is beneficial.
212		335
213	In some situations you want as low a delay as possible, which can be	336	In some situations you want as low a delay as possible, which can be
214	accomplishd by setting this option to a true value.	337	accomplishd by setting this option to a true value.
215		338
216	The default is your opertaing system's default behaviour (most likely	339	The default is your operating system's default behaviour (most likely
217	enabled), this option explicitly enables or disables it, if possible.	340	enabled). This option explicitly enables or disables it, if possible.
		341
		342	=item keepalive => <boolean>
		343
		344	Enables (default disable) the SO_KEEPALIVE option on the stream socket:
		345	normally, TCP connections have no time-out once established, so TCP
		346	connections, once established, can stay alive forever even when the other
		347	side has long gone. TCP keepalives are a cheap way to take down long-lived
		348	TCP connections when the other side becomes unreachable. While the default
		349	is OS-dependent, TCP keepalives usually kick in after around two hours,
		350	and, if the other side doesn't reply, take down the TCP connection some 10
		351	to 15 minutes later.
		352
		353	It is harmless to specify this option for file handles that do not support
		354	keepalives, and enabling it on connections that are potentially long-lived
		355	is usually a good idea.
		356
		357	=item oobinline => <boolean>
		358
		359	BSD majorly fucked up the implementation of TCP urgent data. The result
		360	is that almost no OS implements TCP according to the specs, and every OS
		361	implements it slightly differently.
		362
		363	If you want to handle TCP urgent data, then setting this flag (the default
		364	is enabled) gives you the most portable way of getting urgent data, by
		365	putting it into the stream.
		366
		367	Since BSD emulation of OOB data on top of TCP's urgent data can have
		368	security implications, AnyEvent::Handle sets this flag automatically
		369	unless explicitly specified. Note that setting this flag after
		370	establishing a connection I<may> be a bit too late (data loss could
		371	already have occured on BSD systems), but at least it will protect you
		372	from most attacks.
218		373
219	=item read_size => <bytes>	374	=item read_size => <bytes>
220		375
221	The default read block size (the amount of bytes this module will	376	The initial read block size, the number of bytes this module will try
222	try to read during each loop iteration, which affects memory	377	to read during each loop iteration. Each handle object will consume
223	requirements). Default: C<8192>.	378	at least this amount of memory for the read buffer as well, so when
		379	handling many connections watch out for memory requirements). See also
		380	C<max_read_size>. Default: C<2048>.
		381
		382	=item max_read_size => <bytes>
		383
		384	The maximum read buffer size used by the dynamic adjustment
		385	algorithm: Each time AnyEvent::Handle can read C<read_size> bytes in
		386	one go it will double C<read_size> up to the maximum given by this
		387	option. Default: C<131072> or C<read_size>, whichever is higher.
224		388
225	=item low_water_mark => <bytes>	389	=item low_water_mark => <bytes>
226		390
227	Sets the amount of bytes (default: C<0>) that make up an "empty" write	391	Sets the number of bytes (default: C<0>) that make up an "empty" write
228	buffer: If the write reaches this size or gets even samller it is	392	buffer: If the buffer reaches this size or gets even samller it is
229	considered empty.	393	considered empty.
230		394
231	Sometimes it can be beneficial (for performance reasons) to add data to	395	Sometimes it can be beneficial (for performance reasons) to add data to
232	the write buffer before it is fully drained, but this is a rare case, as	396	the write buffer before it is fully drained, but this is a rare case, as
233	the operating system kernel usually buffers data as well, so the default	397	the operating system kernel usually buffers data as well, so the default
234	is good in almost all cases.	398	is good in almost all cases.
235		399
236	=item linger => <seconds>	400	=item linger => <seconds>
237		401
238	If non-zero (default: C<3600>), then the destructor of the	402	If this is non-zero (default: C<3600>), the destructor of the
239	AnyEvent::Handle object will check whether there is still outstanding	403	AnyEvent::Handle object will check whether there is still outstanding
240	write data and will install a watcher that will write this data to the	404	write data and will install a watcher that will write this data to the
241	socket. No errors will be reported (this mostly matches how the operating	405	socket. No errors will be reported (this mostly matches how the operating
242	system treats outstanding data at socket close time).	406	system treats outstanding data at socket close time).
243		407
244	This will not work for partial TLS data that could not be encoded	408	This will not work for partial TLS data that could not be encoded
245	yet. This data will be lost. Calling the C<stoptls> method in time might	409	yet. This data will be lost. Calling the C<stoptls> method in time might
246	help.	410	help.
247		411
		412	=item peername => $string
		413
		414	A string used to identify the remote site - usually the DNS hostname
		415	(I<not> IDN!) used to create the connection, rarely the IP address.
		416
		417	Apart from being useful in error messages, this string is also used in TLS
		418	peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
		419	verification will be skipped when C<peername> is not specified or is
		420	C<undef>.
		421
248	=item tls => "accept" | "connect" | Net::SSLeay::SSL object	422	=item tls => "accept" | "connect" | Net::SSLeay::SSL object
249		423
250	When this parameter is given, it enables TLS (SSL) mode, that means	424	When this parameter is given, it enables TLS (SSL) mode, that means
251	AnyEvent will start a TLS handshake as soon as the conenction has been	425	AnyEvent will start a TLS handshake as soon as the connection has been
252	established and will transparently encrypt/decrypt data afterwards.	426	established and will transparently encrypt/decrypt data afterwards.
		427
		428	All TLS protocol errors will be signalled as C<EPROTO>, with an
		429	appropriate error message.
253		430
254	TLS mode requires Net::SSLeay to be installed (it will be loaded	431	TLS mode requires Net::SSLeay to be installed (it will be loaded
255	automatically when you try to create a TLS handle): this module doesn't	432	automatically when you try to create a TLS handle): this module doesn't
256	have a dependency on that module, so if your module requires it, you have	433	have a dependency on that module, so if your module requires it, you have
257	to add the dependency yourself.	434	to add the dependency yourself. If Net::SSLeay cannot be loaded or is too
		435	old, you get an C<EPROTO> error.
258		436
259	Unlike TCP, TLS has a server and client side: for the TLS server side, use	437	Unlike TCP, TLS has a server and client side: for the TLS server side, use
260	C<accept>, and for the TLS client side of a connection, use C<connect>	438	C<accept>, and for the TLS client side of a connection, use C<connect>
261	mode.	439	mode.
262		440
263	You can also provide your own TLS connection object, but you have	441	You can also provide your own TLS connection object, but you have
264	to make sure that you call either C<Net::SSLeay::set_connect_state>	442	to make sure that you call either C<Net::SSLeay::set_connect_state>
265	or C<Net::SSLeay::set_accept_state> on it before you pass it to	443	or C<Net::SSLeay::set_accept_state> on it before you pass it to
266	AnyEvent::Handle.	444	AnyEvent::Handle. Also, this module will take ownership of this connection
		445	object.
267		446
		447	At some future point, AnyEvent::Handle might switch to another TLS
		448	implementation, then the option to use your own session object will go
		449	away.
		450
		451	B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
		452	passing in the wrong integer will lead to certain crash. This most often
		453	happens when one uses a stylish C<< tls => 1 >> and is surprised about the
		454	segmentation fault.
		455
268	See the C<< ->starttls >> method for when need to start TLS negotiation later.	456	Use the C<< ->starttls >> method if you need to start TLS negotiation later.
269		457
270	=item tls_ctx => $ssl_ctx	458	=item tls_ctx => $anyevent_tls
271		459
272	Use the given C<Net::SSLeay::CTX> object to create the new TLS connection	460	Use the given C<AnyEvent::TLS> object to create the new TLS connection
273	(unless a connection object was specified directly). If this parameter is	461	(unless a connection object was specified directly). If this
274	missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.	462	parameter is missing (or C<undef>), then AnyEvent::Handle will use
		463	C<AnyEvent::Handle::TLS_CTX>.
		464
		465	Instead of an object, you can also specify a hash reference with C<< key
		466	=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
		467	new TLS context object.
		468
		469	=item on_starttls => $cb->($handle, $success[, $error_message])
		470
		471	This callback will be invoked when the TLS/SSL handshake has finished. If
		472	C<$success> is true, then the TLS handshake succeeded, otherwise it failed
		473	(C<on_stoptls> will not be called in this case).
		474
		475	The session in C<< $handle->{tls} >> can still be examined in this
		476	callback, even when the handshake was not successful.
		477
		478	TLS handshake failures will not cause C<on_error> to be invoked when this
		479	callback is in effect, instead, the error message will be passed to C<on_starttls>.
		480
		481	Without this callback, handshake failures lead to C<on_error> being
		482	called as usual.
		483
		484	Note that you cannot just call C<starttls> again in this callback. If you
		485	need to do that, start an zero-second timer instead whose callback can
		486	then call C<< ->starttls >> again.
		487
		488	=item on_stoptls => $cb->($handle)
		489
		490	When a SSLv3/TLS shutdown/close notify/EOF is detected and this callback is
		491	set, then it will be invoked after freeing the TLS session. If it is not,
		492	then a TLS shutdown condition will be treated like a normal EOF condition
		493	on the handle.
		494
		495	The session in C<< $handle->{tls} >> can still be examined in this
		496	callback.
		497
		498	This callback will only be called on TLS shutdowns, not when the
		499	underlying handle signals EOF.
275		500
276	=item json => JSON or JSON::XS object	501	=item json => JSON or JSON::XS object
277		502
278	This is the json coder object used by the C<json> read and write types.	503	This is the json coder object used by the C<json> read and write types.
279		504
…		…
288		513
289	=cut	514	=cut
290		515
291	sub new {	516	sub new {
292	my $class = shift;	517	my $class = shift;
293
294	my $self = bless { @_ }, $class;	518	my $self = bless { @_ }, $class;
295		519
296	$self->{fh} or Carp::croak "mandatory argument fh is missing";	520	if ($self->{fh}) {
		521	$self->_start;
		522	return unless $self->{fh}; # could be gone by now
		523
		524	} elsif ($self->{connect}) {
		525	require AnyEvent::Socket;
		526
		527	$self->{peername} = $self->{connect}[0]
		528	unless exists $self->{peername};
		529
		530	$self->{_skip_drain_rbuf} = 1;
		531
		532	{
		533	Scalar::Util::weaken (my $self = $self);
		534
		535	$self->{_connect} =
		536	AnyEvent::Socket::tcp_connect (
		537	$self->{connect}[0],
		538	$self->{connect}[1],
		539	sub {
		540	my ($fh, $host, $port, $retry) = @_;
		541
		542	delete $self->{_connect}; # no longer needed
		543
		544	if ($fh) {
		545	$self->{fh} = $fh;
		546
		547	delete $self->{_skip_drain_rbuf};
		548	$self->_start;
		549
		550	$self->{on_connect}
		551	and $self->{on_connect}($self, $host, $port, sub {
		552	delete @$self{qw(fh _tw _rtw _wtw _ww _rw _eof _queue rbuf _wbuf tls _tls_rbuf _tls_wbuf)};
		553	$self->{_skip_drain_rbuf} = 1;
		554	&$retry;
		555	});
		556
		557	} else {
		558	if ($self->{on_connect_error}) {
		559	$self->{on_connect_error}($self, "$!");
		560	$self->destroy if $self;
		561	} else {
		562	$self->_error ($!, 1);
		563	}
		564	}
		565	},
		566	sub {
		567	local $self->{fh} = $_[0];
		568
		569	$self->{on_prepare}
		570	? $self->{on_prepare}->($self)
		571	: ()
		572	}
		573	);
		574	}
		575
		576	} else {
		577	Carp::croak "AnyEvent::Handle: either an existing fh or the connect parameter must be specified";
		578	}
		579
		580	$self
		581	}
		582
		583	sub _start {
		584	my ($self) = @_;
		585
		586	# too many clueless people try to use udp and similar sockets
		587	# with AnyEvent::Handle, do them a favour.
		588	my $type = getsockopt $self->{fh}, Socket::SOL_SOCKET (), Socket::SO_TYPE ();
		589	Carp::croak "AnyEvent::Handle: only stream sockets supported, anything else will NOT work!"
		590	if Socket::SOCK_STREAM () != (unpack "I", $type) && defined $type;
297		591
298	AnyEvent::Util::fh_nonblocking $self->{fh}, 1;	592	AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
299		593
		594	$self->{_activity} =
		595	$self->{_ractivity} =
		596	$self->{_wactivity} = AE::now;
		597
		598	$self->{read_size} ||= 2048;
		599	$self->{max_read_size} = $self->{read_size}
		600	if $self->{read_size} > ($self->{max_read_size} || MAX_READ_SIZE);
		601
		602	$self->timeout (delete $self->{timeout} ) if $self->{timeout};
		603	$self->rtimeout (delete $self->{rtimeout} ) if $self->{rtimeout};
		604	$self->wtimeout (delete $self->{wtimeout} ) if $self->{wtimeout};
		605
		606	$self->no_delay (delete $self->{no_delay} ) if exists $self->{no_delay} && $self->{no_delay};
		607	$self->keepalive (delete $self->{keepalive}) if exists $self->{keepalive} && $self->{keepalive};
		608
		609	$self->oobinline (exists $self->{oobinline} ? delete $self->{oobinline} : 1);
		610
300	$self->starttls (delete $self->{tls}, delete $self->{tls_ctx})	611	$self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
301	if $self->{tls};	612	if $self->{tls};
302		613
303	$self->{_activity} = AnyEvent->now;
304	$self->_timeout;
305
306	$self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain};	614	$self->on_drain (delete $self->{on_drain} ) if $self->{on_drain};
307	$self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
308		615
309	$self->start_read	616	$self->start_read
310	if $self->{on_read};	617	if $self->{on_read} || @{ $self->{_queue} };
311		618
312	$self	619	$self->_drain_wbuf;
313	}
314
315	sub _shutdown {
316	my ($self) = @_;
317
318	delete $self->{_tw};
319	delete $self->{_rw};
320	delete $self->{_ww};
321	delete $self->{fh};
322
323	&_freetls;
324
325	delete $self->{on_read};
326	delete $self->{_queue};
327	}	620	}
328		621
329	sub _error {	622	sub _error {
330	my ($self, $errno, $fatal) = @_;	623	my ($self, $errno, $fatal, $message) = @_;
331
332	$self->_shutdown
333	if $fatal;
334		624
335	$! = $errno;	625	$! = $errno;
		626	$message ||= "$!";
336		627
337	if ($self->{on_error}) {	628	if ($self->{on_error}) {
338	$self->{on_error}($self, $fatal);	629	$self->{on_error}($self, $fatal, $message);
339	} else {	630	$self->destroy if $fatal;
		631	} elsif ($self->{fh} || $self->{connect}) {
		632	$self->destroy;
340	Carp::croak "AnyEvent::Handle uncaught error: $!";	633	Carp::croak "AnyEvent::Handle uncaught error: $message";
341	}	634	}
342	}	635	}
343		636
344	=item $fh = $handle->fh	637	=item $fh = $handle->fh
345		638
…		…
369	$_[0]{on_eof} = $_[1];	662	$_[0]{on_eof} = $_[1];
370	}	663	}
371		664
372	=item $handle->on_timeout ($cb)	665	=item $handle->on_timeout ($cb)
373		666
374	Replace the current C<on_timeout> callback, or disables the callback (but	667	=item $handle->on_rtimeout ($cb)
375	not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor
376	argument and method.
377		668
378	=cut	669	=item $handle->on_wtimeout ($cb)
379		670
380	sub on_timeout {	671	Replace the current C<on_timeout>, C<on_rtimeout> or C<on_wtimeout>
381	$_[0]{on_timeout} = $_[1];	672	callback, or disables the callback (but not the timeout) if C<$cb> =
382	}	673	C<undef>. See the C<timeout> constructor argument and method.
		674
		675	=cut
		676
		677	# see below
383		678
384	=item $handle->autocork ($boolean)	679	=item $handle->autocork ($boolean)
385		680
386	Enables or disables the current autocork behaviour (see C<autocork>	681	Enables or disables the current autocork behaviour (see C<autocork>
387	constructor argument).	682	constructor argument). Changes will only take effect on the next write.
388		683
389	=cut	684	=cut
		685
		686	sub autocork {
		687	$_[0]{autocork} = $_[1];
		688	}
390		689
391	=item $handle->no_delay ($boolean)	690	=item $handle->no_delay ($boolean)
392		691
393	Enables or disables the C<no_delay> setting (see constructor argument of	692	Enables or disables the C<no_delay> setting (see constructor argument of
394	the same name for details).	693	the same name for details).
…		…
396	=cut	695	=cut
397		696
398	sub no_delay {	697	sub no_delay {
399	$_[0]{no_delay} = $_[1];	698	$_[0]{no_delay} = $_[1];
400		699
		700	setsockopt $_[0]{fh}, Socket::IPPROTO_TCP (), Socket::TCP_NODELAY (), int $_[1]
		701	if $_[0]{fh};
		702	}
		703
		704	=item $handle->keepalive ($boolean)
		705
		706	Enables or disables the C<keepalive> setting (see constructor argument of
		707	the same name for details).
		708
		709	=cut
		710
		711	sub keepalive {
		712	$_[0]{keepalive} = $_[1];
		713
401	eval {	714	eval {
402	local $SIG{__DIE__};	715	local $SIG{__DIE__};
403	setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1];	716	setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
		717	if $_[0]{fh};
404	};	718	};
405	}	719	}
406		720
		721	=item $handle->oobinline ($boolean)
		722
		723	Enables or disables the C<oobinline> setting (see constructor argument of
		724	the same name for details).
		725
		726	=cut
		727
		728	sub oobinline {
		729	$_[0]{oobinline} = $_[1];
		730
		731	eval {
		732	local $SIG{__DIE__};
		733	setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_OOBINLINE (), int $_[1]
		734	if $_[0]{fh};
		735	};
		736	}
		737
		738	=item $handle->keepalive ($boolean)
		739
		740	Enables or disables the C<keepalive> setting (see constructor argument of
		741	the same name for details).
		742
		743	=cut
		744
		745	sub keepalive {
		746	$_[0]{keepalive} = $_[1];
		747
		748	eval {
		749	local $SIG{__DIE__};
		750	setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
		751	if $_[0]{fh};
		752	};
		753	}
		754
		755	=item $handle->on_starttls ($cb)
		756
		757	Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument).
		758
		759	=cut
		760
		761	sub on_starttls {
		762	$_[0]{on_starttls} = $_[1];
		763	}
		764
		765	=item $handle->on_stoptls ($cb)
		766
		767	Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
		768
		769	=cut
		770
		771	sub on_stoptls {
		772	$_[0]{on_stoptls} = $_[1];
		773	}
		774
		775	=item $handle->rbuf_max ($max_octets)
		776
		777	Configures the C<rbuf_max> setting (C<undef> disables it).
		778
		779	=item $handle->wbuf_max ($max_octets)
		780
		781	Configures the C<wbuf_max> setting (C<undef> disables it).
		782
		783	=cut
		784
		785	sub rbuf_max {
		786	$_[0]{rbuf_max} = $_[1];
		787	}
		788
		789	sub wbuf_max {
		790	$_[0]{wbuf_max} = $_[1];
		791	}
		792
407	#############################################################################	793	#############################################################################
408		794
409	=item $handle->timeout ($seconds)	795	=item $handle->timeout ($seconds)
410		796
		797	=item $handle->rtimeout ($seconds)
		798
		799	=item $handle->wtimeout ($seconds)
		800
411	Configures (or disables) the inactivity timeout.	801	Configures (or disables) the inactivity timeout.
412		802
413	=cut	803	The timeout will be checked instantly, so this method might destroy the
		804	handle before it returns.
414		805
415	sub timeout {	806	=item $handle->timeout_reset
		807
		808	=item $handle->rtimeout_reset
		809
		810	=item $handle->wtimeout_reset
		811
		812	Reset the activity timeout, as if data was received or sent.
		813
		814	These methods are cheap to call.
		815
		816	=cut
		817
		818	for my $dir ("", "r", "w") {
		819	my $timeout = "${dir}timeout";
		820	my $tw = "_${dir}tw";
		821	my $on_timeout = "on_${dir}timeout";
		822	my $activity = "_${dir}activity";
		823	my $cb;
		824
		825	*$on_timeout = sub {
		826	$_[0]{$on_timeout} = $_[1];
		827	};
		828
		829	*$timeout = sub {
416	my ($self, $timeout) = @_;	830	my ($self, $new_value) = @_;
417		831
		832	$new_value >= 0
		833	or Carp::croak "AnyEvent::Handle->$timeout called with negative timeout ($new_value), caught";
		834
418	$self->{timeout} = $timeout;	835	$self->{$timeout} = $new_value;
419	$self->_timeout;	836	delete $self->{$tw}; &$cb;
420	}	837	};
421		838
		839	*{"${dir}timeout_reset"} = sub {
		840	$_[0]{$activity} = AE::now;
		841	};
		842
		843	# main workhorse:
422	# reset the timeout watcher, as neccessary	844	# reset the timeout watcher, as neccessary
423	# also check for time-outs	845	# also check for time-outs
424	sub _timeout {	846	$cb = sub {
425	my ($self) = @_;	847	my ($self) = @_;
426		848
427	if ($self->{timeout}) {	849	if ($self->{$timeout} && $self->{fh}) {
428	my $NOW = AnyEvent->now;	850	my $NOW = AE::now;
429		851
430	# when would the timeout trigger?	852	# when would the timeout trigger?
431	my $after = $self->{_activity} + $self->{timeout} - $NOW;	853	my $after = $self->{$activity} + $self->{$timeout} - $NOW;
432		854
433	# now or in the past already?	855	# now or in the past already?
434	if ($after <= 0) {	856	if ($after <= 0) {
435	$self->{_activity} = $NOW;	857	$self->{$activity} = $NOW;
436		858
437	if ($self->{on_timeout}) {	859	if ($self->{$on_timeout}) {
438	$self->{on_timeout}($self);	860	$self->{$on_timeout}($self);
439	} else {	861	} else {
440	$self->_error (&Errno::ETIMEDOUT);	862	$self->_error (Errno::ETIMEDOUT);
		863	}
		864
		865	# callback could have changed timeout value, optimise
		866	return unless $self->{$timeout};
		867
		868	# calculate new after
		869	$after = $self->{$timeout};
441	}	870	}
442		871
443	# callback could have changed timeout value, optimise	872	Scalar::Util::weaken $self;
444	return unless $self->{timeout};	873	return unless $self; # ->error could have destroyed $self
445		874
446	# calculate new after	875	$self->{$tw} ||= AE::timer $after, 0, sub {
447	$after = $self->{timeout};	876	delete $self->{$tw};
		877	$cb->($self);
		878	};
		879	} else {
		880	delete $self->{$tw};
448	}	881	}
449
450	Scalar::Util::weaken $self;
451	return unless $self; # ->error could have destroyed $self
452
453	$self->{_tw} ||= AnyEvent->timer (after => $after, cb => sub {
454	delete $self->{_tw};
455	$self->_timeout;
456	});
457	} else {
458	delete $self->{_tw};
459	}	882	}
460	}	883	}
461		884
462	#############################################################################	885	#############################################################################
463		886
…		…
470		893
471	The write queue is very simple: you can add data to its end, and	894	The write queue is very simple: you can add data to its end, and
472	AnyEvent::Handle will automatically try to get rid of it for you.	895	AnyEvent::Handle will automatically try to get rid of it for you.
473		896
474	When data could be written and the write buffer is shorter then the low	897	When data could be written and the write buffer is shorter then the low
475	water mark, the C<on_drain> callback will be invoked.	898	water mark, the C<on_drain> callback will be invoked once.
476		899
477	=over 4	900	=over 4
478		901
479	=item $handle->on_drain ($cb)	902	=item $handle->on_drain ($cb)
480		903
481	Sets the C<on_drain> callback or clears it (see the description of	904	Sets the C<on_drain> callback or clears it (see the description of
482	C<on_drain> in the constructor).	905	C<on_drain> in the constructor).
483		906
		907	This method may invoke callbacks (and therefore the handle might be
		908	destroyed after it returns).
		909
484	=cut	910	=cut
485		911
486	sub on_drain {	912	sub on_drain {
487	my ($self, $cb) = @_;	913	my ($self, $cb) = @_;
488		914
…		…
492	if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});	918	if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
493	}	919	}
494		920
495	=item $handle->push_write ($data)	921	=item $handle->push_write ($data)
496		922
497	Queues the given scalar to be written. You can push as much data as you	923	Queues the given scalar to be written. You can push as much data as
498	want (only limited by the available memory), as C<AnyEvent::Handle>	924	you want (only limited by the available memory and C<wbuf_max>), as
499	buffers it independently of the kernel.	925	C<AnyEvent::Handle> buffers it independently of the kernel.
		926
		927	This method may invoke callbacks (and therefore the handle might be
		928	destroyed after it returns).
500		929
501	=cut	930	=cut
502		931
503	sub _drain_wbuf {	932	sub _drain_wbuf {
504	my ($self) = @_;	933	my ($self) = @_;
…		…
508	Scalar::Util::weaken $self;	937	Scalar::Util::weaken $self;
509		938
510	my $cb = sub {	939	my $cb = sub {
511	my $len = syswrite $self->{fh}, $self->{wbuf};	940	my $len = syswrite $self->{fh}, $self->{wbuf};
512		941
513	if ($len >= 0) {	942	if (defined $len) {
514	substr $self->{wbuf}, 0, $len, "";	943	substr $self->{wbuf}, 0, $len, "";
515		944
516	$self->{_activity} = AnyEvent->now;	945	$self->{_activity} = $self->{_wactivity} = AE::now;
517		946
518	$self->{on_drain}($self)	947	$self->{on_drain}($self)
519	if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})	948	if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
520	&& $self->{on_drain};	949	&& $self->{on_drain};
521		950
…		…
527		956
528	# try to write data immediately	957	# try to write data immediately
529	$cb->() unless $self->{autocork};	958	$cb->() unless $self->{autocork};
530		959
531	# if still data left in wbuf, we need to poll	960	# if still data left in wbuf, we need to poll
532	$self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb)	961	$self->{_ww} = AE::io $self->{fh}, 1, $cb
533	if length $self->{wbuf};	962	if length $self->{wbuf};
		963
		964	if (
		965	defined $self->{wbuf_max}
		966	&& $self->{wbuf_max} < length $self->{wbuf}
		967	) {
		968	$self->_error (Errno::ENOSPC, 1), return;
		969	}
534	};	970	};
535	}	971	}
536		972
537	our %WH;	973	our %WH;
538		974
		975	# deprecated
539	sub register_write_type($$) {	976	sub register_write_type($$) {
540	$WH{$_[0]} = $_[1];	977	$WH{$_[0]} = $_[1];
541	}	978	}
542		979
543	sub push_write {	980	sub push_write {
544	my $self = shift;	981	my $self = shift;
545		982
546	if (@_ > 1) {	983	if (@_ > 1) {
547	my $type = shift;	984	my $type = shift;
548		985
		986	@_ = ($WH{$type} ||= _load_func "$type\::anyevent_write_type"
549	@_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write")	987	or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_write")
550	->($self, @_);	988	->($self, @_);
551	}	989	}
552		990
		991	# we downgrade here to avoid hard-to-track-down bugs,
		992	# and diagnose the problem earlier and better.
		993
553	if ($self->{tls}) {	994	if ($self->{tls}) {
554	$self->{_tls_wbuf} .= $_[0];	995	utf8::downgrade $self->{_tls_wbuf} .= $_[0];
555	&_dotls ($self);	996	&_dotls ($self) if $self->{fh};
556	} else {	997	} else {
557	$self->{wbuf} .= $_[0];	998	utf8::downgrade $self->{wbuf} .= $_[0];
558	$self->_drain_wbuf;	999	$self->_drain_wbuf if $self->{fh};
559	}	1000	}
560	}	1001	}
561		1002
562	=item $handle->push_write (type => @args)	1003	=item $handle->push_write (type => @args)
563		1004
564	Instead of formatting your data yourself, you can also let this module do	1005	Instead of formatting your data yourself, you can also let this module
565	the job by specifying a type and type-specific arguments.	1006	do the job by specifying a type and type-specific arguments. You
		1007	can also specify the (fully qualified) name of a package, in which
		1008	case AnyEvent tries to load the package and then expects to find the
		1009	C<anyevent_write_type> function inside (see "custom write types", below).
566		1010
567	Predefined types are (if you have ideas for additional types, feel free to	1011	Predefined types are (if you have ideas for additional types, feel free to
568	drop by and tell us):	1012	drop by and tell us):
569		1013
570	=over 4	1014	=over 4
…		…
577	=cut	1021	=cut
578		1022
579	register_write_type netstring => sub {	1023	register_write_type netstring => sub {
580	my ($self, $string) = @_;	1024	my ($self, $string) = @_;
581		1025
582	sprintf "%d:%s,", (length $string), $string	1026	(length $string) . ":$string,"
583	};	1027	};
584		1028
585	=item packstring => $format, $data	1029	=item packstring => $format, $data
586		1030
587	An octet string prefixed with an encoded length. The encoding C<$format>	1031	An octet string prefixed with an encoded length. The encoding C<$format>
…		…
627	Other languages could read single lines terminated by a newline and pass	1071	Other languages could read single lines terminated by a newline and pass
628	this line into their JSON decoder of choice.	1072	this line into their JSON decoder of choice.
629		1073
630	=cut	1074	=cut
631		1075
		1076	sub json_coder() {
		1077	eval { require JSON::XS; JSON::XS->new->utf8 }
		1078	|| do { require JSON; JSON->new->utf8 }
		1079	}
		1080
632	register_write_type json => sub {	1081	register_write_type json => sub {
633	my ($self, $ref) = @_;	1082	my ($self, $ref) = @_;
634		1083
635	require JSON;	1084	my $json = $self->{json} ||= json_coder;
636		1085
637	$self->{json} ? $self->{json}->encode ($ref)	1086	$json->encode ($ref)
638	: JSON::encode_json ($ref)
639	};	1087	};
640		1088
641	=item storable => $reference	1089	=item storable => $reference
642		1090
643	Freezes the given reference using L<Storable> and writes it to the	1091	Freezes the given reference using L<Storable> and writes it to the
…		…
646	=cut	1094	=cut
647		1095
648	register_write_type storable => sub {	1096	register_write_type storable => sub {
649	my ($self, $ref) = @_;	1097	my ($self, $ref) = @_;
650		1098
651	require Storable;	1099	require Storable unless $Storable::VERSION;
652		1100
653	pack "w/a*", Storable::nfreeze ($ref)	1101	pack "w/a*", Storable::nfreeze ($ref)
654	};	1102	};
655		1103
656	=back	1104	=back
657		1105
658	=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args)	1106	=item $handle->push_shutdown
659		1107
660	This function (not method) lets you add your own types to C<push_write>.	1108	Sometimes you know you want to close the socket after writing your data
		1109	before it was actually written. One way to do that is to replace your
		1110	C<on_drain> handler by a callback that shuts down the socket (and set
		1111	C<low_water_mark> to C<0>). This method is a shorthand for just that, and
		1112	replaces the C<on_drain> callback with:
		1113
		1114	sub { shutdown $_[0]{fh}, 1 }
		1115
		1116	This simply shuts down the write side and signals an EOF condition to the
		1117	the peer.
		1118
		1119	You can rely on the normal read queue and C<on_eof> handling
		1120	afterwards. This is the cleanest way to close a connection.
		1121
		1122	This method may invoke callbacks (and therefore the handle might be
		1123	destroyed after it returns).
		1124
		1125	=cut
		1126
		1127	sub push_shutdown {
		1128	my ($self) = @_;
		1129
		1130	delete $self->{low_water_mark};
		1131	$self->on_drain (sub { shutdown $_[0]{fh}, 1 });
		1132	}
		1133
		1134	=item custom write types - Package::anyevent_write_type $handle, @args
		1135
		1136	Instead of one of the predefined types, you can also specify the name of
		1137	a package. AnyEvent will try to load the package and then expects to find
		1138	a function named C<anyevent_write_type> inside. If it isn't found, it
		1139	progressively tries to load the parent package until it either finds the
		1140	function (good) or runs out of packages (bad).
		1141
661	Whenever the given C<type> is used, C<push_write> will invoke the code	1142	Whenever the given C<type> is used, C<push_write> will the function with
662	reference with the handle object and the remaining arguments.	1143	the handle object and the remaining arguments.
663		1144
664	The code reference is supposed to return a single octet string that will	1145	The function is supposed to return a single octet string that will be
665	be appended to the write buffer.	1146	appended to the write buffer, so you can mentally treat this function as a
		1147	"arguments to on-the-wire-format" converter.
666		1148
667	Note that this is a function, and all types registered this way will be	1149	Example: implement a custom write type C<join> that joins the remaining
668	global, so try to use unique names.	1150	arguments using the first one.
		1151
		1152	$handle->push_write (My::Type => " ", 1,2,3);
		1153
		1154	# uses the following package, which can be defined in the "My::Type" or in
		1155	# the "My" modules to be auto-loaded, or just about anywhere when the
		1156	# My::Type::anyevent_write_type is defined before invoking it.
		1157
		1158	package My::Type;
		1159
		1160	sub anyevent_write_type {
		1161	my ($handle, $delim, @args) = @_;
		1162
		1163	join $delim, @args
		1164	}
669		1165
670	=cut	1166	=cut
671		1167
672	#############################################################################	1168	#############################################################################
673		1169
…		…
682	ways, the "simple" way, using only C<on_read> and the "complex" way, using	1178	ways, the "simple" way, using only C<on_read> and the "complex" way, using
683	a queue.	1179	a queue.
684		1180
685	In the simple case, you just install an C<on_read> callback and whenever	1181	In the simple case, you just install an C<on_read> callback and whenever
686	new data arrives, it will be called. You can then remove some data (if	1182	new data arrives, it will be called. You can then remove some data (if
687	enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna	1183	enough is there) from the read buffer (C<< $handle->rbuf >>). Or you can
688	leave the data there if you want to accumulate more (e.g. when only a	1184	leave the data there if you want to accumulate more (e.g. when only a
689	partial message has been received so far).	1185	partial message has been received so far), or change the read queue with
		1186	e.g. C<push_read>.
690		1187
691	In the more complex case, you want to queue multiple callbacks. In this	1188	In the more complex case, you want to queue multiple callbacks. In this
692	case, AnyEvent::Handle will call the first queued callback each time new	1189	case, AnyEvent::Handle will call the first queued callback each time new
693	data arrives (also the first time it is queued) and removes it when it has	1190	data arrives (also the first time it is queued) and remove it when it has
694	done its job (see C<push_read>, below).	1191	done its job (see C<push_read>, below).
695		1192
696	This way you can, for example, push three line-reads, followed by reading	1193	This way you can, for example, push three line-reads, followed by reading
697	a chunk of data, and AnyEvent::Handle will execute them in order.	1194	a chunk of data, and AnyEvent::Handle will execute them in order.
698		1195
…		…
755	=cut	1252	=cut
756		1253
757	sub _drain_rbuf {	1254	sub _drain_rbuf {
758	my ($self) = @_;	1255	my ($self) = @_;
759		1256
		1257	# avoid recursion
		1258	return if $self->{_skip_drain_rbuf};
760	local $self->{_in_drain} = 1;	1259	local $self->{_skip_drain_rbuf} = 1;
761
762	if (
763	defined $self->{rbuf_max}
764	&& $self->{rbuf_max} < length $self->{rbuf}
765	) {
766	$self->_error (&Errno::ENOSPC, 1), return;
767	}
768		1260
769	while () {	1261	while () {
		1262	# we need to use a separate tls read buffer, as we must not receive data while
		1263	# we are draining the buffer, and this can only happen with TLS.
		1264	$self->{rbuf} .= delete $self->{_tls_rbuf}
		1265	if exists $self->{_tls_rbuf};
		1266
770	my $len = length $self->{rbuf};	1267	my $len = length $self->{rbuf};
771		1268
772	if (my $cb = shift @{ $self->{_queue} }) {	1269	if (my $cb = shift @{ $self->{_queue} }) {
773	unless ($cb->($self)) {	1270	unless ($cb->($self)) {
774	if ($self->{_eof}) {	1271	# no progress can be made
775	# no progress can be made (not enough data and no data forthcoming)	1272	# (not enough data and no data forthcoming)
776	$self->_error (&Errno::EPIPE, 1), return;	1273	$self->_error (Errno::EPIPE, 1), return
777	}	1274	if $self->{_eof};
778		1275
779	unshift @{ $self->{_queue} }, $cb;	1276	unshift @{ $self->{_queue} }, $cb;
780	last;	1277	last;
781	}	1278	}
782	} elsif ($self->{on_read}) {	1279	} elsif ($self->{on_read}) {
…		…
789	&& !@{ $self->{_queue} } # and the queue is still empty	1286	&& !@{ $self->{_queue} } # and the queue is still empty
790	&& $self->{on_read} # but we still have on_read	1287	&& $self->{on_read} # but we still have on_read
791	) {	1288	) {
792	# no further data will arrive	1289	# no further data will arrive
793	# so no progress can be made	1290	# so no progress can be made
794	$self->_error (&Errno::EPIPE, 1), return	1291	$self->_error (Errno::EPIPE, 1), return
795	if $self->{_eof};	1292	if $self->{_eof};
796		1293
797	last; # more data might arrive	1294	last; # more data might arrive
798	}	1295	}
799	} else {	1296	} else {
…		…
802	last;	1299	last;
803	}	1300	}
804	}	1301	}
805		1302
806	if ($self->{_eof}) {	1303	if ($self->{_eof}) {
807	if ($self->{on_eof}) {	1304	$self->{on_eof}
808	$self->{on_eof}($self)	1305	? $self->{on_eof}($self)
809	} else {	1306	: $self->_error (0, 1, "Unexpected end-of-file");
810	$self->_error (0, 1);	1307
811	}	1308	return;
		1309	}
		1310
		1311	if (
		1312	defined $self->{rbuf_max}
		1313	&& $self->{rbuf_max} < length $self->{rbuf}
		1314	) {
		1315	$self->_error (Errno::ENOSPC, 1), return;
812	}	1316	}
813		1317
814	# may need to restart read watcher	1318	# may need to restart read watcher
815	unless ($self->{_rw}) {	1319	unless ($self->{_rw}) {
816	$self->start_read	1320	$self->start_read
…		…
822		1326
823	This replaces the currently set C<on_read> callback, or clears it (when	1327	This replaces the currently set C<on_read> callback, or clears it (when
824	the new callback is C<undef>). See the description of C<on_read> in the	1328	the new callback is C<undef>). See the description of C<on_read> in the
825	constructor.	1329	constructor.
826		1330
		1331	This method may invoke callbacks (and therefore the handle might be
		1332	destroyed after it returns).
		1333
827	=cut	1334	=cut
828		1335
829	sub on_read {	1336	sub on_read {
830	my ($self, $cb) = @_;	1337	my ($self, $cb) = @_;
831		1338
832	$self->{on_read} = $cb;	1339	$self->{on_read} = $cb;
833	$self->_drain_rbuf if $cb && !$self->{_in_drain};	1340	$self->_drain_rbuf if $cb;
834	}	1341	}
835		1342
836	=item $handle->rbuf	1343	=item $handle->rbuf
837		1344
838	Returns the read buffer (as a modifiable lvalue).	1345	Returns the read buffer (as a modifiable lvalue). You can also access the
		1346	read buffer directly as the C<< ->{rbuf} >> member, if you want (this is
		1347	much faster, and no less clean).
839		1348
840	You can access the read buffer directly as the C<< ->{rbuf} >> member, if	1349	The only operation allowed on the read buffer (apart from looking at it)
841	you want.	1350	is removing data from its beginning. Otherwise modifying or appending to
		1351	it is not allowed and will lead to hard-to-track-down bugs.
842		1352
843	NOTE: The read buffer should only be used or modified if the C<on_read>,	1353	NOTE: The read buffer should only be used or modified in the C<on_read>
844	C<push_read> or C<unshift_read> methods are used. The other read methods	1354	callback or when C<push_read> or C<unshift_read> are used with a single
845	automatically manage the read buffer.	1355	callback (i.e. untyped). Typed C<push_read> and C<unshift_read> methods
		1356	will manage the read buffer on their own.
846		1357
847	=cut	1358	=cut
848		1359
849	sub rbuf : lvalue {	1360	sub rbuf : lvalue {
850	$_[0]{rbuf}	1361	$_[0]{rbuf}
…		…
867		1378
868	If enough data was available, then the callback must remove all data it is	1379	If enough data was available, then the callback must remove all data it is
869	interested in (which can be none at all) and return a true value. After returning	1380	interested in (which can be none at all) and return a true value. After returning
870	true, it will be removed from the queue.	1381	true, it will be removed from the queue.
871		1382
		1383	These methods may invoke callbacks (and therefore the handle might be
		1384	destroyed after it returns).
		1385
872	=cut	1386	=cut
873		1387
874	our %RH;	1388	our %RH;
875		1389
876	sub register_read_type($$) {	1390	sub register_read_type($$) {
…		…
882	my $cb = pop;	1396	my $cb = pop;
883		1397
884	if (@_) {	1398	if (@_) {
885	my $type = shift;	1399	my $type = shift;
886		1400
		1401	$cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
887	$cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_read")	1402	or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_read")
888	->($self, $cb, @_);	1403	->($self, $cb, @_);
889	}	1404	}
890		1405
891	push @{ $self->{_queue} }, $cb;	1406	push @{ $self->{_queue} }, $cb;
892	$self->_drain_rbuf unless $self->{_in_drain};	1407	$self->_drain_rbuf;
893	}	1408	}
894		1409
895	sub unshift_read {	1410	sub unshift_read {
896	my $self = shift;	1411	my $self = shift;
897	my $cb = pop;	1412	my $cb = pop;
898		1413
899	if (@_) {	1414	if (@_) {
900	my $type = shift;	1415	my $type = shift;
901		1416
		1417	$cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
902	$cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::unshift_read")	1418	or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::unshift_read")
903	->($self, $cb, @_);	1419	->($self, $cb, @_);
904	}	1420	}
905		1421
906
907	unshift @{ $self->{_queue} }, $cb;	1422	unshift @{ $self->{_queue} }, $cb;
908	$self->_drain_rbuf unless $self->{_in_drain};	1423	$self->_drain_rbuf;
909	}	1424	}
910		1425
911	=item $handle->push_read (type => @args, $cb)	1426	=item $handle->push_read (type => @args, $cb)
912		1427
913	=item $handle->unshift_read (type => @args, $cb)	1428	=item $handle->unshift_read (type => @args, $cb)
914		1429
915	Instead of providing a callback that parses the data itself you can chose	1430	Instead of providing a callback that parses the data itself you can chose
916	between a number of predefined parsing formats, for chunks of data, lines	1431	between a number of predefined parsing formats, for chunks of data, lines
917	etc.	1432	etc. You can also specify the (fully qualified) name of a package, in
		1433	which case AnyEvent tries to load the package and then expects to find the
		1434	C<anyevent_read_type> function inside (see "custom read types", below).
918		1435
919	Predefined types are (if you have ideas for additional types, feel free to	1436	Predefined types are (if you have ideas for additional types, feel free to
920	drop by and tell us):	1437	drop by and tell us):
921		1438
922	=over 4	1439	=over 4
…		…
928	data.	1445	data.
929		1446
930	Example: read 2 bytes.	1447	Example: read 2 bytes.
931		1448
932	$handle->push_read (chunk => 2, sub {	1449	$handle->push_read (chunk => 2, sub {
933	warn "yay ", unpack "H*", $_[1];	1450	say "yay " . unpack "H*", $_[1];
934	});	1451	});
935		1452
936	=cut	1453	=cut
937		1454
938	register_read_type chunk => sub {	1455	register_read_type chunk => sub {
…		…
968		1485
969	register_read_type line => sub {	1486	register_read_type line => sub {
970	my ($self, $cb, $eol) = @_;	1487	my ($self, $cb, $eol) = @_;
971		1488
972	if (@_ < 3) {	1489	if (@_ < 3) {
973	# this is more than twice as fast as the generic code below	1490	# this is faster then the generic code below
974	sub {	1491	sub {
975	$_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return;	1492	(my $pos = index $_[0]{rbuf}, "\012") >= 0
		1493	or return;
976		1494
		1495	(my $str = substr $_[0]{rbuf}, 0, $pos + 1, "") =~ s/(\015?\012)\Z// or die;
977	$cb->($_[0], $1, $2);	1496	$cb->($_[0], $str, "$1");
978	1	1497	1
979	}	1498	}
980	} else {	1499	} else {
981	$eol = quotemeta $eol unless ref $eol;	1500	$eol = quotemeta $eol unless ref $eol;
982	$eol = qr|^(.*?)($eol)|s;	1501	$eol = qr|^(.*?)($eol)|s;
983		1502
984	sub {	1503	sub {
985	$_[0]{rbuf} =~ s/$eol// or return;	1504	$_[0]{rbuf} =~ s/$eol// or return;
986		1505
987	$cb->($_[0], $1, $2);	1506	$cb->($_[0], "$1", "$2");
988	1	1507	1
989	}	1508	}
990	}	1509	}
991	};	1510	};
992		1511
…		…
1014	the receive buffer when neither C<$accept> nor C<$reject> match,	1533	the receive buffer when neither C<$accept> nor C<$reject> match,
1015	and everything preceding and including the match will be accepted	1534	and everything preceding and including the match will be accepted
1016	unconditionally. This is useful to skip large amounts of data that you	1535	unconditionally. This is useful to skip large amounts of data that you
1017	know cannot be matched, so that the C<$accept> or C<$reject> regex do not	1536	know cannot be matched, so that the C<$accept> or C<$reject> regex do not
1018	have to start matching from the beginning. This is purely an optimisation	1537	have to start matching from the beginning. This is purely an optimisation
1019	and is usually worth only when you expect more than a few kilobytes.	1538	and is usually worth it only when you expect more than a few kilobytes.
1020		1539
1021	Example: expect a http header, which ends at C<\015\012\015\012>. Since we	1540	Example: expect a http header, which ends at C<\015\012\015\012>. Since we
1022	expect the header to be very large (it isn't in practise, but...), we use	1541	expect the header to be very large (it isn't in practice, but...), we use
1023	a skip regex to skip initial portions. The skip regex is tricky in that	1542	a skip regex to skip initial portions. The skip regex is tricky in that
1024	it only accepts something not ending in either \015 or \012, as these are	1543	it only accepts something not ending in either \015 or \012, as these are
1025	required for the accept regex.	1544	required for the accept regex.
1026		1545
1027	$handle->push_read (regex =>	1546	$handle->push_read (regex =>
…		…
1040		1559
1041	sub {	1560	sub {
1042	# accept	1561	# accept
1043	if ($$rbuf =~ $accept) {	1562	if ($$rbuf =~ $accept) {
1044	$data .= substr $$rbuf, 0, $+[0], "";	1563	$data .= substr $$rbuf, 0, $+[0], "";
1045	$cb->($self, $data);	1564	$cb->($_[0], $data);
1046	return 1;	1565	return 1;
1047	}	1566	}
1048		1567
1049	# reject	1568	# reject
1050	if ($reject && $$rbuf =~ $reject) {	1569	if ($reject && $$rbuf =~ $reject) {
1051	$self->_error (&Errno::EBADMSG);	1570	$_[0]->_error (Errno::EBADMSG);
1052	}	1571	}
1053		1572
1054	# skip	1573	# skip
1055	if ($skip && $$rbuf =~ $skip) {	1574	if ($skip && $$rbuf =~ $skip) {
1056	$data .= substr $$rbuf, 0, $+[0], "";	1575	$data .= substr $$rbuf, 0, $+[0], "";
…		…
1072	my ($self, $cb) = @_;	1591	my ($self, $cb) = @_;
1073		1592
1074	sub {	1593	sub {
1075	unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) {	1594	unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) {
1076	if ($_[0]{rbuf} =~ /[^0-9]/) {	1595	if ($_[0]{rbuf} =~ /[^0-9]/) {
1077	$self->_error (&Errno::EBADMSG);	1596	$_[0]->_error (Errno::EBADMSG);
1078	}	1597	}
1079	return;	1598	return;
1080	}	1599	}
1081		1600
1082	my $len = $1;	1601	my $len = $1;
1083		1602
1084	$self->unshift_read (chunk => $len, sub {	1603	$_[0]->unshift_read (chunk => $len, sub {
1085	my $string = $_[1];	1604	my $string = $_[1];
1086	$_[0]->unshift_read (chunk => 1, sub {	1605	$_[0]->unshift_read (chunk => 1, sub {
1087	if ($_[1] eq ",") {	1606	if ($_[1] eq ",") {
1088	$cb->($_[0], $string);	1607	$cb->($_[0], $string);
1089	} else {	1608	} else {
1090	$self->_error (&Errno::EBADMSG);	1609	$_[0]->_error (Errno::EBADMSG);
1091	}	1610	}
1092	});	1611	});
1093	});	1612	});
1094		1613
1095	1	1614	1
…		…
1101	An octet string prefixed with an encoded length. The encoding C<$format>	1620	An octet string prefixed with an encoded length. The encoding C<$format>
1102	uses the same format as a Perl C<pack> format, but must specify a single	1621	uses the same format as a Perl C<pack> format, but must specify a single
1103	integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an	1622	integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
1104	optional C<!>, C<< < >> or C<< > >> modifier).	1623	optional C<!>, C<< < >> or C<< > >> modifier).
1105		1624
1106	DNS over TCP uses a prefix of C<n>, EPP uses a prefix of C<N>.	1625	For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
		1626	EPP uses a prefix of C<N> (4 octtes).
1107		1627
1108	Example: read a block of data prefixed by its length in BER-encoded	1628	Example: read a block of data prefixed by its length in BER-encoded
1109	format (very efficient).	1629	format (very efficient).
1110		1630
1111	$handle->push_read (packstring => "w", sub {	1631	$handle->push_read (packstring => "w", sub {
…		…
1141	}	1661	}
1142	};	1662	};
1143		1663
1144	=item json => $cb->($handle, $hash_or_arrayref)	1664	=item json => $cb->($handle, $hash_or_arrayref)
1145		1665
1146	Reads a JSON object or array, decodes it and passes it to the callback.	1666	Reads a JSON object or array, decodes it and passes it to the
		1667	callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1147		1668
1148	If a C<json> object was passed to the constructor, then that will be used	1669	If a C<json> object was passed to the constructor, then that will be used
1149	for the final decode, otherwise it will create a JSON coder expecting UTF-8.	1670	for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1150		1671
1151	This read type uses the incremental parser available with JSON version	1672	This read type uses the incremental parser available with JSON version
…		…
1160	=cut	1681	=cut
1161		1682
1162	register_read_type json => sub {	1683	register_read_type json => sub {
1163	my ($self, $cb) = @_;	1684	my ($self, $cb) = @_;
1164		1685
1165	require JSON;	1686	my $json = $self->{json} ||= json_coder;
1166		1687
1167	my $data;	1688	my $data;
1168	my $rbuf = \$self->{rbuf};	1689	my $rbuf = \$self->{rbuf};
1169		1690
1170	my $json = $self->{json} ||= JSON->new->utf8;
1171
1172	sub {	1691	sub {
1173	my $ref = $json->incr_parse ($self->{rbuf});	1692	my $ref = eval { $json->incr_parse ($_[0]{rbuf}) };
1174		1693
1175	if ($ref) {	1694	if ($ref) {
1176	$self->{rbuf} = $json->incr_text;	1695	$_[0]{rbuf} = $json->incr_text;
1177	$json->incr_text = "";	1696	$json->incr_text = "";
1178	$cb->($self, $ref);	1697	$cb->($_[0], $ref);
1179		1698
1180	1	1699	1
		1700	} elsif ($@) {
		1701	# error case
		1702	$json->incr_skip;
		1703
		1704	$_[0]{rbuf} = $json->incr_text;
		1705	$json->incr_text = "";
		1706
		1707	$_[0]->_error (Errno::EBADMSG);
		1708
		1709	()
1181	} else {	1710	} else {
1182	$self->{rbuf} = "";	1711	$_[0]{rbuf} = "";
		1712
1183	()	1713	()
1184	}	1714	}
1185	}	1715	}
1186	};	1716	};
1187		1717
…		…
1196	=cut	1726	=cut
1197		1727
1198	register_read_type storable => sub {	1728	register_read_type storable => sub {
1199	my ($self, $cb) = @_;	1729	my ($self, $cb) = @_;
1200		1730
1201	require Storable;	1731	require Storable unless $Storable::VERSION;
1202		1732
1203	sub {	1733	sub {
1204	# when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method	1734	# when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1205	defined (my $len = eval { unpack "w", $_[0]{rbuf} })	1735	defined (my $len = eval { unpack "w", $_[0]{rbuf} })
1206	or return;	1736	or return;
…		…
1209		1739
1210	# bypass unshift if we already have the remaining chunk	1740	# bypass unshift if we already have the remaining chunk
1211	if ($format + $len <= length $_[0]{rbuf}) {	1741	if ($format + $len <= length $_[0]{rbuf}) {
1212	my $data = substr $_[0]{rbuf}, $format, $len;	1742	my $data = substr $_[0]{rbuf}, $format, $len;
1213	substr $_[0]{rbuf}, 0, $format + $len, "";	1743	substr $_[0]{rbuf}, 0, $format + $len, "";
		1744
1214	$cb->($_[0], Storable::thaw ($data));	1745	eval { $cb->($_[0], Storable::thaw ($data)); 1 }
		1746	or return $_[0]->_error (Errno::EBADMSG);
1215	} else {	1747	} else {
1216	# remove prefix	1748	# remove prefix
1217	substr $_[0]{rbuf}, 0, $format, "";	1749	substr $_[0]{rbuf}, 0, $format, "";
1218		1750
1219	# read remaining chunk	1751	# read remaining chunk
1220	$_[0]->unshift_read (chunk => $len, sub {	1752	$_[0]->unshift_read (chunk => $len, sub {
1221	if (my $ref = eval { Storable::thaw ($_[1]) }) {	1753	eval { $cb->($_[0], Storable::thaw ($_[1])); 1 }
1222	$cb->($_[0], $ref);
1223	} else {
1224	$self->_error (&Errno::EBADMSG);	1754	or $_[0]->_error (Errno::EBADMSG);
1225	}
1226	});	1755	});
1227	}	1756	}
1228		1757
1229	1	1758	1
1230	}	1759	}
1231	};	1760	};
1232		1761
		1762	=item tls_detect => $cb->($handle, $detect, $major, $minor)
		1763
		1764	Checks the input stream for a valid SSL or TLS handshake TLSPaintext
		1765	record without consuming anything. Only SSL version 3 or higher
		1766	is handled, up to the fictituous protocol 4.x (but both SSL3+ and
		1767	SSL2-compatible framing is supported).
		1768
		1769	If it detects that the input data is likely TLS, it calls the callback
		1770	with a true value for C<$detect> and the (on-wire) TLS version as second
		1771	and third argument (C<$major> is C<3>, and C<$minor> is 0..3 for SSL
		1772	3.0, TLS 1.0, 1.1 and 1.2, respectively). If it detects the input to
		1773	be definitely not TLS, it calls the callback with a false value for
		1774	C<$detect>.
		1775
		1776	The callback could use this information to decide whether or not to start
		1777	TLS negotiation.
		1778
		1779	In all cases the data read so far is passed to the following read
		1780	handlers.
		1781
		1782	Usually you want to use the C<tls_autostart> read type instead.
		1783
		1784	If you want to design a protocol that works in the presence of TLS
		1785	dtection, make sure that any non-TLS data doesn't start with the octet 22
		1786	(ASCII SYN, 16 hex) or 128-255 (i.e. highest bit set). The checks this
		1787	read type does are a bit more strict, but might losen in the future to
		1788	accomodate protocol changes.
		1789
		1790	This read type does not rely on L<AnyEvent::TLS> (and thus, not on
		1791	L<Net::SSLeay>).
		1792
		1793	=item tls_autostart => $tls[, $tls_ctx]
		1794
		1795	Tries to detect a valid SSL or TLS handshake. If one is detected, it tries
		1796	to start tls by calling C<starttls> with the given arguments.
		1797
		1798	In practise, C<$tls> must be C<accept>, or a Net::SSLeay context that has
		1799	been configured to accept, as servers do not normally send a handshake on
		1800	their own and ths cannot be detected in this way.
		1801
		1802	See C<tls_detect> above for more details.
		1803
		1804	Example: give the client a chance to start TLS before accepting a text
		1805	line.
		1806
		1807	$hdl->push_read (tls_detect => "accept");
		1808	$hdl->push_read (line => sub {
		1809	print "received ", ($_[0]{tls} ? "encrypted" : "cleartext"), " <$_[1]>\n";
		1810	});
		1811
		1812	=cut
		1813
		1814	register_read_type tls_detect => sub {
		1815	my ($self, $cb) = @_;
		1816
		1817	sub {
		1818	# this regex matches a full or partial tls record
		1819	if (
		1820	# ssl3+: type(22=handshake) major(=3) minor(any) length_hi
		1821	$self->{rbuf} =~ /^(?:\z| \x16 (\z| [\x03\x04] (?:\z| . (?:\z| [\x00-\x40] ))))/xs
		1822	# ssl2 comapatible: len_hi len_lo type(1) major minor dummy(forlength)
		1823	or $self->{rbuf} =~ /^(?:\z| [\x80-\xff] (?:\z| . (?:\z| \x01 (\z| [\x03\x04] (?:\z| . (?:\z| . ))))))/xs
		1824	) {
		1825	return if 3 != length $1; # partial match, can't decide yet
		1826
		1827	# full match, valid TLS record
		1828	my ($major, $minor) = unpack "CC", $1;
		1829	$cb->($self, "accept", $major + $minor * 0.1);
		1830	} else {
		1831	# mismatch == guaranteed not TLS
		1832	$cb->($self, undef);
		1833	}
		1834
		1835	1
		1836	}
		1837	};
		1838
		1839	register_read_type tls_autostart => sub {
		1840	my ($self, @tls) = @_;
		1841
		1842	$RH{tls_detect}($self, sub {
		1843	return unless $_[1];
		1844	$_[0]->starttls (@tls);
		1845	})
		1846	};
		1847
1233	=back	1848	=back
1234		1849
1235	=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args)	1850	=item custom read types - Package::anyevent_read_type $handle, $cb, @args
1236		1851
1237	This function (not method) lets you add your own types to C<push_read>.	1852	Instead of one of the predefined types, you can also specify the name
		1853	of a package. AnyEvent will try to load the package and then expects to
		1854	find a function named C<anyevent_read_type> inside. If it isn't found, it
		1855	progressively tries to load the parent package until it either finds the
		1856	function (good) or runs out of packages (bad).
1238		1857
1239	Whenever the given C<type> is used, C<push_read> will invoke the code	1858	Whenever this type is used, C<push_read> will invoke the function with the
1240	reference with the handle object, the callback and the remaining	1859	handle object, the original callback and the remaining arguments.
1241	arguments.
1242		1860
1243	The code reference is supposed to return a callback (usually a closure)	1861	The function is supposed to return a callback (usually a closure) that
1244	that works as a plain read callback (see C<< ->push_read ($cb) >>).	1862	works as a plain read callback (see C<< ->push_read ($cb) >>), so you can
		1863	mentally treat the function as a "configurable read type to read callback"
		1864	converter.
1245		1865
1246	It should invoke the passed callback when it is done reading (remember to	1866	It should invoke the original callback when it is done reading (remember
1247	pass C<$handle> as first argument as all other callbacks do that).	1867	to pass C<$handle> as first argument as all other callbacks do that,
		1868	although there is no strict requirement on this).
1248		1869
1249	Note that this is a function, and all types registered this way will be
1250	global, so try to use unique names.
1251
1252	For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>,	1870	For examples, see the source of this module (F<perldoc -m
1253	search for C<register_read_type>)).	1871	AnyEvent::Handle>, search for C<register_read_type>)).
1254		1872
1255	=item $handle->stop_read	1873	=item $handle->stop_read
1256		1874
1257	=item $handle->start_read	1875	=item $handle->start_read
1258		1876
…		…
1264	Note that AnyEvent::Handle will automatically C<start_read> for you when	1882	Note that AnyEvent::Handle will automatically C<start_read> for you when
1265	you change the C<on_read> callback or push/unshift a read callback, and it	1883	you change the C<on_read> callback or push/unshift a read callback, and it
1266	will automatically C<stop_read> for you when neither C<on_read> is set nor	1884	will automatically C<stop_read> for you when neither C<on_read> is set nor
1267	there are any read requests in the queue.	1885	there are any read requests in the queue.
1268		1886
1269	These methods will have no effect when in TLS mode (as TLS doesn't support	1887	In older versions of this module (<= 5.3), these methods had no effect,
1270	half-duplex connections).	1888	as TLS does not support half-duplex connections. In current versions they
		1889	work as expected, as this behaviour is required to avoid certain resource
		1890	attacks, where the program would be forced to read (and buffer) arbitrary
		1891	amounts of data before being able to send some data. The drawback is that
		1892	some readings of the the SSL/TLS specifications basically require this
		1893	attack to be working, as SSL/TLS implementations might stall sending data
		1894	during a rehandshake.
		1895
		1896	As a guideline, during the initial handshake, you should not stop reading,
		1897	and as a client, it might cause problems, depending on your application.
1271		1898
1272	=cut	1899	=cut
1273		1900
1274	sub stop_read {	1901	sub stop_read {
1275	my ($self) = @_;	1902	my ($self) = @_;
1276		1903
1277	delete $self->{_rw} unless $self->{tls};	1904	delete $self->{_rw};
1278	}	1905	}
1279		1906
1280	sub start_read {	1907	sub start_read {
1281	my ($self) = @_;	1908	my ($self) = @_;
1282		1909
1283	unless ($self->{_rw} || $self->{_eof}) {	1910	unless ($self->{_rw} || $self->{_eof} || !$self->{fh}) {
1284	Scalar::Util::weaken $self;	1911	Scalar::Util::weaken $self;
1285		1912
1286	$self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub {	1913	$self->{_rw} = AE::io $self->{fh}, 0, sub {
1287	my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});	1914	my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1288	my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;	1915	my $len = sysread $self->{fh}, $$rbuf, $self->{read_size}, length $$rbuf;
1289		1916
1290	if ($len > 0) {	1917	if ($len > 0) {
1291	$self->{_activity} = AnyEvent->now;	1918	$self->{_activity} = $self->{_ractivity} = AE::now;
1292		1919
1293	if ($self->{tls}) {	1920	if ($self->{tls}) {
1294	Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);	1921	Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
		1922
1295	&_dotls ($self);	1923	&_dotls ($self);
1296	} else {	1924	} else {
1297	$self->_drain_rbuf unless $self->{_in_drain};	1925	$self->_drain_rbuf;
		1926	}
		1927
		1928	if ($len == $self->{read_size}) {
		1929	$self->{read_size} *= 2;
		1930	$self->{read_size} = $self->{max_read_size} || MAX_READ_SIZE
		1931	if $self->{read_size} > ($self->{max_read_size} || MAX_READ_SIZE);
1298	}	1932	}
1299		1933
1300	} elsif (defined $len) {	1934	} elsif (defined $len) {
1301	delete $self->{_rw};	1935	delete $self->{_rw};
1302	$self->{_eof} = 1;	1936	$self->{_eof} = 1;
1303	$self->_drain_rbuf unless $self->{_in_drain};	1937	$self->_drain_rbuf;
1304		1938
1305	} elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {	1939	} elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
1306	return $self->_error ($!, 1);	1940	return $self->_error ($!, 1);
1307	}	1941	}
1308	});	1942	};
1309	}	1943	}
1310	}	1944	}
1311		1945
		1946	our $ERROR_SYSCALL;
		1947	our $ERROR_WANT_READ;
		1948
		1949	sub _tls_error {
		1950	my ($self, $err) = @_;
		1951
		1952	return $self->_error ($!, 1)
		1953	if $err == Net::SSLeay::ERROR_SYSCALL ();
		1954
		1955	my $err = Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
		1956
		1957	# reduce error string to look less scary
		1958	$err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
		1959
		1960	if ($self->{_on_starttls}) {
		1961	(delete $self->{_on_starttls})->($self, undef, $err);
		1962	&_freetls;
		1963	} else {
		1964	&_freetls;
		1965	$self->_error (Errno::EPROTO, 1, $err);
		1966	}
		1967	}
		1968
		1969	# poll the write BIO and send the data if applicable
		1970	# also decode read data if possible
		1971	# this is basiclaly our TLS state machine
		1972	# more efficient implementations are possible with openssl,
		1973	# but not with the buggy and incomplete Net::SSLeay.
1312	sub _dotls {	1974	sub _dotls {
1313	my ($self) = @_;	1975	my ($self) = @_;
1314		1976
1315	my $buf;	1977	my $tmp;
1316		1978
1317	if (length $self->{_tls_wbuf}) {	1979	if (length $self->{_tls_wbuf}) {
1318	while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {	1980	while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
1319	substr $self->{_tls_wbuf}, 0, $len, "";	1981	substr $self->{_tls_wbuf}, 0, $tmp, "";
1320	}	1982	}
1321	}
1322		1983
		1984	$tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
		1985	return $self->_tls_error ($tmp)
		1986	if $tmp != $ERROR_WANT_READ
		1987	&& ($tmp != $ERROR_SYSCALL || $!);
		1988	}
		1989
1323	while (defined ($buf = Net::SSLeay::read ($self->{tls}))) {	1990	while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1324	unless (length $buf) {	1991	unless (length $tmp) {
1325	# let's treat SSL-eof as we treat normal EOF	1992	$self->{_on_starttls}
1326	delete $self->{_rw};	1993	and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
1327	$self->{_eof} = 1;
1328	&_freetls;	1994	&_freetls;
		1995
		1996	if ($self->{on_stoptls}) {
		1997	$self->{on_stoptls}($self);
		1998	return;
		1999	} else {
		2000	# let's treat SSL-eof as we treat normal EOF
		2001	delete $self->{_rw};
		2002	$self->{_eof} = 1;
		2003	}
1329	}	2004	}
1330		2005
1331	$self->{rbuf} .= $buf;	2006	$self->{_tls_rbuf} .= $tmp;
1332	$self->_drain_rbuf unless $self->{_in_drain};	2007	$self->_drain_rbuf;
1333	$self->{tls} or return; # tls session might have gone away in callback	2008	$self->{tls} or return; # tls session might have gone away in callback
1334	}	2009	}
1335		2010
1336	my $err = Net::SSLeay::get_error ($self->{tls}, -1);	2011	$tmp = Net::SSLeay::get_error ($self->{tls}, -1);
1337
1338	if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
1339	if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
1340	return $self->_error ($!, 1);	2012	return $self->_tls_error ($tmp)
1341	} elsif ($err == Net::SSLeay::ERROR_SSL ()) {	2013	if $tmp != $ERROR_WANT_READ
1342	return $self->_error (&Errno::EIO, 1);	2014	&& ($tmp != $ERROR_SYSCALL || $!);
1343	}
1344		2015
1345	# all others are fine for our purposes
1346	}
1347
1348	if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) {	2016	while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1349	$self->{wbuf} .= $buf;	2017	$self->{wbuf} .= $tmp;
1350	$self->_drain_wbuf;	2018	$self->_drain_wbuf;
		2019	$self->{tls} or return; # tls session might have gone away in callback
1351	}	2020	}
		2021
		2022	$self->{_on_starttls}
		2023	and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
		2024	and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
1352	}	2025	}
1353		2026
1354	=item $handle->starttls ($tls[, $tls_ctx])	2027	=item $handle->starttls ($tls[, $tls_ctx])
1355		2028
1356	Instead of starting TLS negotiation immediately when the AnyEvent::Handle	2029	Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1357	object is created, you can also do that at a later time by calling	2030	object is created, you can also do that at a later time by calling
1358	C<starttls>.	2031	C<starttls>. See the C<tls> constructor argument for general info.
		2032
		2033	Starting TLS is currently an asynchronous operation - when you push some
		2034	write data and then call C<< ->starttls >> then TLS negotiation will start
		2035	immediately, after which the queued write data is then sent. This might
		2036	change in future versions, so best make sure you have no outstanding write
		2037	data when calling this method.
1359		2038
1360	The first argument is the same as the C<tls> constructor argument (either	2039	The first argument is the same as the C<tls> constructor argument (either
1361	C<"connect">, C<"accept"> or an existing Net::SSLeay object).	2040	C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1362		2041
1363	The second argument is the optional C<Net::SSLeay::CTX> object that is	2042	The second argument is the optional C<AnyEvent::TLS> object that is used
1364	used when AnyEvent::Handle has to create its own TLS connection object.	2043	when AnyEvent::Handle has to create its own TLS connection object, or
		2044	a hash reference with C<< key => value >> pairs that will be used to
		2045	construct a new context.
1365		2046
1366	The TLS connection object will end up in C<< $handle->{tls} >> after this	2047	The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1367	call and can be used or changed to your liking. Note that the handshake	2048	context in C<< $handle->{tls_ctx} >> after this call and can be used or
1368	might have already started when this function returns.	2049	changed to your liking. Note that the handshake might have already started
		2050	when this function returns.
1369		2051
1370	If it an error to start a TLS handshake more than once per	2052	Due to bugs in OpenSSL, it might or might not be possible to do multiple
1371	AnyEvent::Handle object (this is due to bugs in OpenSSL).	2053	handshakes on the same stream. It is best to not attempt to use the
		2054	stream after stopping TLS.
1372		2055
		2056	This method may invoke callbacks (and therefore the handle might be
		2057	destroyed after it returns).
		2058
1373	=cut	2059	=cut
		2060
		2061	our %TLS_CACHE; #TODO not yet documented, should we?
1374		2062
1375	sub starttls {	2063	sub starttls {
1376	my ($self, $ssl, $ctx) = @_;	2064	my ($self, $tls, $ctx) = @_;
1377		2065
1378	require Net::SSLeay;	2066	Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught"
1379
1380	Carp::croak "it is an error to call starttls more than once on an Anyevent::Handle object"
1381	if $self->{tls};	2067	if $self->{tls};
		2068
		2069	unless (defined $AnyEvent::TLS::VERSION) {
		2070	eval {
		2071	require Net::SSLeay;
		2072	require AnyEvent::TLS;
		2073	1
		2074	} or return $self->_error (Errno::EPROTO, 1, "TLS support not available on this system");
		2075	}
		2076
		2077	$self->{tls} = $tls;
		2078	$self->{tls_ctx} = $ctx if @_ > 2;
		2079
		2080	return unless $self->{fh};
		2081
		2082	$ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
		2083	$ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
		2084
		2085	$tls = delete $self->{tls};
		2086	$ctx = $self->{tls_ctx};
		2087
		2088	local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
		2089
		2090	if ("HASH" eq ref $ctx) {
		2091	if ($ctx->{cache}) {
		2092	my $key = $ctx+0;
		2093	$ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
		2094	} else {
		2095	$ctx = new AnyEvent::TLS %$ctx;
		2096	}
		2097	}
1382		2098
1383	if ($ssl eq "accept") {	2099	$self->{tls_ctx} = $ctx || TLS_CTX ();
1384	$ssl = Net::SSLeay::new ($ctx || TLS_CTX ());	2100	$self->{tls} = $tls = $self->{tls_ctx}->_get_session ($tls, $self, $self->{peername});
1385	Net::SSLeay::set_accept_state ($ssl);
1386	} elsif ($ssl eq "connect") {
1387	$ssl = Net::SSLeay::new ($ctx || TLS_CTX ());
1388	Net::SSLeay::set_connect_state ($ssl);
1389	}
1390
1391	$self->{tls} = $ssl;
1392		2101
1393	# basically, this is deep magic (because SSL_read should have the same issues)	2102	# basically, this is deep magic (because SSL_read should have the same issues)
1394	# but the openssl maintainers basically said: "trust us, it just works".	2103	# but the openssl maintainers basically said: "trust us, it just works".
1395	# (unfortunately, we have to hardcode constants because the abysmally misdesigned	2104	# (unfortunately, we have to hardcode constants because the abysmally misdesigned
1396	# and mismaintained ssleay-module doesn't even offer them).	2105	# and mismaintained ssleay-module doesn't even offer them).
…		…
1400	#	2109	#
1401	# note that we do not try to keep the length constant between writes as we are required to do.	2110	# note that we do not try to keep the length constant between writes as we are required to do.
1402	# we assume that most (but not all) of this insanity only applies to non-blocking cases,	2111	# we assume that most (but not all) of this insanity only applies to non-blocking cases,
1403	# and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to	2112	# and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
1404	# have identity issues in that area.	2113	# have identity issues in that area.
1405	Net::SSLeay::CTX_set_mode ($self->{tls},	2114	# Net::SSLeay::CTX_set_mode ($ssl,
1406	(eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)	2115	# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1407	| (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));	2116	# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
		2117	Net::SSLeay::CTX_set_mode ($tls, 1|2);
1408		2118
1409	$self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());	2119	$self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1410	$self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());	2120	$self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1411		2121
		2122	Net::SSLeay::BIO_write ($self->{_rbio}, $self->{rbuf});
		2123	$self->{rbuf} = "";
		2124
1412	Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio});	2125	Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});
		2126
		2127	$self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
		2128	if $self->{on_starttls};
1413		2129
1414	&_dotls; # need to trigger the initial handshake	2130	&_dotls; # need to trigger the initial handshake
1415	$self->start_read; # make sure we actually do read	2131	$self->start_read; # make sure we actually do read
1416	}	2132	}
1417		2133
1418	=item $handle->stoptls	2134	=item $handle->stoptls
1419		2135
1420	Shuts down the SSL connection - this makes a proper EOF handshake by	2136	Shuts down the SSL connection - this makes a proper EOF handshake by
1421	sending a close notify to the other side, but since OpenSSL doesn't	2137	sending a close notify to the other side, but since OpenSSL doesn't
1422	support non-blocking shut downs, it is not possible to re-use the stream	2138	support non-blocking shut downs, it is not guaranteed that you can re-use
1423	afterwards.	2139	the stream afterwards.
		2140
		2141	This method may invoke callbacks (and therefore the handle might be
		2142	destroyed after it returns).
1424		2143
1425	=cut	2144	=cut
1426		2145
1427	sub stoptls {	2146	sub stoptls {
1428	my ($self) = @_;	2147	my ($self) = @_;
1429		2148
1430	if ($self->{tls}) {	2149	if ($self->{tls} && $self->{fh}) {
1431	Net::SSLeay::shutdown ($self->{tls});	2150	Net::SSLeay::shutdown ($self->{tls});
1432		2151
1433	&_dotls;	2152	&_dotls;
1434		2153
1435	# we don't give a shit. no, we do, but we can't. no...	2154	# # we don't give a shit. no, we do, but we can't. no...#d#
1436	# we, we... have to use openssl :/	2155	# # we, we... have to use openssl :/#d#
1437	&_freetls;	2156	# &_freetls;#d#
1438	}	2157	}
1439	}	2158	}
1440		2159
1441	sub _freetls {	2160	sub _freetls {
1442	my ($self) = @_;	2161	my ($self) = @_;
1443		2162
1444	return unless $self->{tls};	2163	return unless $self->{tls};
1445		2164
1446	Net::SSLeay::free (delete $self->{tls});	2165	$self->{tls_ctx}->_put_session (delete $self->{tls})
		2166	if $self->{tls} > 0;
1447		2167
1448	delete @$self{qw(_rbio _wbio _tls_wbuf)};	2168	delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
1449	}	2169	}
		2170
		2171	=item $handle->resettls
		2172
		2173	This rarely-used method simply resets and TLS state on the handle, usually
		2174	causing data loss.
		2175
		2176	One case where it may be useful is when you want to skip over the data in
		2177	the stream but you are not interested in interpreting it, so data loss is
		2178	no concern.
		2179
		2180	=cut
		2181
		2182	*resettls = \&_freetls;
1450		2183
1451	sub DESTROY {	2184	sub DESTROY {
1452	my $self = shift;	2185	my ($self) = @_;
1453		2186
1454	&_freetls;	2187	&_freetls;
1455		2188
1456	my $linger = exists $self->{linger} ? $self->{linger} : 3600;	2189	my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1457		2190
1458	if ($linger && length $self->{wbuf}) {	2191	if ($linger && length $self->{wbuf} && $self->{fh}) {
1459	my $fh = delete $self->{fh};	2192	my $fh = delete $self->{fh};
1460	my $wbuf = delete $self->{wbuf};	2193	my $wbuf = delete $self->{wbuf};
1461		2194
1462	my @linger;	2195	my @linger;
1463		2196
1464	push @linger, AnyEvent->io (fh => $fh, poll => "w", cb => sub {	2197	push @linger, AE::io $fh, 1, sub {
1465	my $len = syswrite $fh, $wbuf, length $wbuf;	2198	my $len = syswrite $fh, $wbuf, length $wbuf;
1466		2199
1467	if ($len > 0) {	2200	if ($len > 0) {
1468	substr $wbuf, 0, $len, "";	2201	substr $wbuf, 0, $len, "";
1469	} else {	2202	} elsif (defined $len || ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK)) {
1470	@linger = (); # end	2203	@linger = (); # end
1471	}	2204	}
		2205	};
		2206	push @linger, AE::timer $linger, 0, sub {
		2207	@linger = ();
		2208	};
		2209	}
		2210	}
		2211
		2212	=item $handle->destroy
		2213
		2214	Shuts down the handle object as much as possible - this call ensures that
		2215	no further callbacks will be invoked and as many resources as possible
		2216	will be freed. Any method you will call on the handle object after
		2217	destroying it in this way will be silently ignored (and it will return the
		2218	empty list).
		2219
		2220	Normally, you can just "forget" any references to an AnyEvent::Handle
		2221	object and it will simply shut down. This works in fatal error and EOF
		2222	callbacks, as well as code outside. It does I<NOT> work in a read or write
		2223	callback, so when you want to destroy the AnyEvent::Handle object from
		2224	within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
		2225	that case.
		2226
		2227	Destroying the handle object in this way has the advantage that callbacks
		2228	will be removed as well, so if those are the only reference holders (as
		2229	is common), then one doesn't need to do anything special to break any
		2230	reference cycles.
		2231
		2232	The handle might still linger in the background and write out remaining
		2233	data, as specified by the C<linger> option, however.
		2234
		2235	=cut
		2236
		2237	sub destroy {
		2238	my ($self) = @_;
		2239
		2240	$self->DESTROY;
		2241	%$self = ();
		2242	bless $self, "AnyEvent::Handle::destroyed";
		2243	}
		2244
		2245	sub AnyEvent::Handle::destroyed::AUTOLOAD {
		2246	#nop
		2247	}
		2248
		2249	=item $handle->destroyed
		2250
		2251	Returns false as long as the handle hasn't been destroyed by a call to C<<
		2252	->destroy >>, true otherwise.
		2253
		2254	Can be useful to decide whether the handle is still valid after some
		2255	callback possibly destroyed the handle. For example, C<< ->push_write >>,
		2256	C<< ->starttls >> and other methods can call user callbacks, which in turn
		2257	can destroy the handle, so work can be avoided by checking sometimes:
		2258
		2259	$hdl->starttls ("accept");
		2260	return if $hdl->destroyed;
		2261	$hdl->push_write (...
		2262
		2263	Note that the call to C<push_write> will silently be ignored if the handle
		2264	has been destroyed, so often you can just ignore the possibility of the
		2265	handle being destroyed.
		2266
		2267	=cut
		2268
		2269	sub destroyed { 0 }
		2270	sub AnyEvent::Handle::destroyed::destroyed { 1 }
		2271
		2272	=item AnyEvent::Handle::TLS_CTX
		2273
		2274	This function creates and returns the AnyEvent::TLS object used by default
		2275	for TLS mode.
		2276
		2277	The context is created by calling L<AnyEvent::TLS> without any arguments.
		2278
		2279	=cut
		2280
		2281	our $TLS_CTX;
		2282
		2283	sub TLS_CTX() {
		2284	$TLS_CTX ||= do {
		2285	require AnyEvent::TLS;
		2286
		2287	new AnyEvent::TLS
		2288	}
		2289	}
		2290
		2291	=back
		2292
		2293
		2294	=head1 NONFREQUENTLY ASKED QUESTIONS
		2295
		2296	=over 4
		2297
		2298	=item I C<undef> the AnyEvent::Handle reference inside my callback and
		2299	still get further invocations!
		2300
		2301	That's because AnyEvent::Handle keeps a reference to itself when handling
		2302	read or write callbacks.
		2303
		2304	It is only safe to "forget" the reference inside EOF or error callbacks,
		2305	from within all other callbacks, you need to explicitly call the C<<
		2306	->destroy >> method.
		2307
		2308	=item Why is my C<on_eof> callback never called?
		2309
		2310	Probably because your C<on_error> callback is being called instead: When
		2311	you have outstanding requests in your read queue, then an EOF is
		2312	considered an error as you clearly expected some data.
		2313
		2314	To avoid this, make sure you have an empty read queue whenever your handle
		2315	is supposed to be "idle" (i.e. connection closes are O.K.). You can set
		2316	an C<on_read> handler that simply pushes the first read requests in the
		2317	queue.
		2318
		2319	See also the next question, which explains this in a bit more detail.
		2320
		2321	=item How can I serve requests in a loop?
		2322
		2323	Most protocols consist of some setup phase (authentication for example)
		2324	followed by a request handling phase, where the server waits for requests
		2325	and handles them, in a loop.
		2326
		2327	There are two important variants: The first (traditional, better) variant
		2328	handles requests until the server gets some QUIT command, causing it to
		2329	close the connection first (highly desirable for a busy TCP server). A
		2330	client dropping the connection is an error, which means this variant can
		2331	detect an unexpected detection close.
		2332
		2333	To handle this case, always make sure you have a non-empty read queue, by
		2334	pushing the "read request start" handler on it:
		2335
		2336	# we assume a request starts with a single line
		2337	my @start_request; @start_request = (line => sub {
		2338	my ($hdl, $line) = @_;
		2339
		2340	... handle request
		2341
		2342	# push next request read, possibly from a nested callback
		2343	$hdl->push_read (@start_request);
		2344	});
		2345
		2346	# auth done, now go into request handling loop
		2347	# now push the first @start_request
		2348	$hdl->push_read (@start_request);
		2349
		2350	By always having an outstanding C<push_read>, the handle always expects
		2351	some data and raises the C<EPIPE> error when the connction is dropped
		2352	unexpectedly.
		2353
		2354	The second variant is a protocol where the client can drop the connection
		2355	at any time. For TCP, this means that the server machine may run out of
		2356	sockets easier, and in general, it means you cannot distinguish a protocl
		2357	failure/client crash from a normal connection close. Nevertheless, these
		2358	kinds of protocols are common (and sometimes even the best solution to the
		2359	problem).
		2360
		2361	Having an outstanding read request at all times is possible if you ignore
		2362	C<EPIPE> errors, but this doesn't help with when the client drops the
		2363	connection during a request, which would still be an error.
		2364
		2365	A better solution is to push the initial request read in an C<on_read>
		2366	callback. This avoids an error, as when the server doesn't expect data
		2367	(i.e. is idly waiting for the next request, an EOF will not raise an
		2368	error, but simply result in an C<on_eof> callback. It is also a bit slower
		2369	and simpler:
		2370
		2371	# auth done, now go into request handling loop
		2372	$hdl->on_read (sub {
		2373	my ($hdl) = @_;
		2374
		2375	# called each time we receive data but the read queue is empty
		2376	# simply start read the request
		2377
		2378	$hdl->push_read (line => sub {
		2379	my ($hdl, $line) = @_;
		2380
		2381	... handle request
		2382
		2383	# do nothing special when the request has been handled, just
		2384	# let the request queue go empty.
1472	});	2385	});
1473	push @linger, AnyEvent->timer (after => $linger, cb => sub {
1474	@linger = ();
1475	});	2386	});
1476	}
1477	}
1478		2387
1479	=item AnyEvent::Handle::TLS_CTX	2388	=item I get different callback invocations in TLS mode/Why can't I pause
		2389	reading?
1480		2390
1481	This function creates and returns the Net::SSLeay::CTX object used by	2391	Unlike, say, TCP, TLS connections do not consist of two independent
1482	default for TLS mode.	2392	communication channels, one for each direction. Or put differently, the
		2393	read and write directions are not independent of each other: you cannot
		2394	write data unless you are also prepared to read, and vice versa.
1483		2395
1484	The context is created like this:	2396	This means that, in TLS mode, you might get C<on_error> or C<on_eof>
		2397	callback invocations when you are not expecting any read data - the reason
		2398	is that AnyEvent::Handle always reads in TLS mode.
1485		2399
1486	Net::SSLeay::load_error_strings;	2400	During the connection, you have to make sure that you always have a
1487	Net::SSLeay::SSLeay_add_ssl_algorithms;	2401	non-empty read-queue, or an C<on_read> watcher. At the end of the
1488	Net::SSLeay::randomize;	2402	connection (or when you no longer want to use it) you can call the
1489		2403	C<destroy> method.
1490	my $CTX = Net::SSLeay::CTX_new;
1491
1492	Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL
1493
1494	=cut
1495
1496	our $TLS_CTX;
1497
1498	sub TLS_CTX() {
1499	$TLS_CTX || do {
1500	require Net::SSLeay;
1501
1502	Net::SSLeay::load_error_strings ();
1503	Net::SSLeay::SSLeay_add_ssl_algorithms ();
1504	Net::SSLeay::randomize ();
1505
1506	$TLS_CTX = Net::SSLeay::CTX_new ();
1507
1508	Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ());
1509
1510	$TLS_CTX
1511	}
1512	}
1513
1514	=back
1515
1516
1517	=head1 NONFREQUENTLY ASKED QUESTIONS
1518
1519	=over 4
1520		2404
1521	=item How do I read data until the other side closes the connection?	2405	=item How do I read data until the other side closes the connection?
1522		2406
1523	If you just want to read your data into a perl scalar, the easiest way to achieve this is	2407	If you just want to read your data into a perl scalar, the easiest way
1524	by setting an C<on_read> callback that does nothing, clearing the C<on_eof> callback	2408	to achieve this is by setting an C<on_read> callback that does nothing,
1525	and in the C<on_error> callback, the data will be in C<$_[0]{rbuf}>:	2409	clearing the C<on_eof> callback and in the C<on_error> callback, the data
		2410	will be in C<$_[0]{rbuf}>:
1526		2411
1527	$handle->on_read (sub { });	2412	$handle->on_read (sub { });
1528	$handle->on_eof (undef);	2413	$handle->on_eof (undef);
1529	$handle->on_error (sub {	2414	$handle->on_error (sub {
1530	my $data = delete $_[0]{rbuf};	2415	my $data = delete $_[0]{rbuf};
1531	undef $handle;
1532	});	2416	});
		2417
		2418	Note that this example removes the C<rbuf> member from the handle object,
		2419	which is not normally allowed by the API. It is expressly permitted in
		2420	this case only, as the handle object needs to be destroyed afterwards.
1533		2421
1534	The reason to use C<on_error> is that TCP connections, due to latencies	2422	The reason to use C<on_error> is that TCP connections, due to latencies
1535	and packets loss, might get closed quite violently with an error, when in	2423	and packets loss, might get closed quite violently with an error, when in
1536	fact, all data has been received.	2424	fact all data has been received.
1537		2425
1538	It is usually better to use acknowledgements when transfering data,	2426	It is usually better to use acknowledgements when transferring data,
1539	to make sure the other side hasn't just died and you got the data	2427	to make sure the other side hasn't just died and you got the data
1540	intact. This is also one reason why so many internet protocols have an	2428	intact. This is also one reason why so many internet protocols have an
1541	explicit QUIT command.	2429	explicit QUIT command.
1542		2430
1543
1544	=item I don't want to destroy the handle too early - how do I wait until all data has been sent?	2431	=item I don't want to destroy the handle too early - how do I wait until
		2432	all data has been written?
1545		2433
1546	After writing your last bits of data, set the C<on_drain> callback	2434	After writing your last bits of data, set the C<on_drain> callback
1547	and destroy the handle in there - with the default setting of	2435	and destroy the handle in there - with the default setting of
1548	C<low_water_mark> this will be called precisely when all data has been	2436	C<low_water_mark> this will be called precisely when all data has been
1549	written to the socket:	2437	written to the socket:
1550		2438
1551	$handle->push_write (...);	2439	$handle->push_write (...);
1552	$handle->on_drain (sub {	2440	$handle->on_drain (sub {
1553	warn "all data submitted to the kernel\n";	2441	AE::log debug => "All data submitted to the kernel.";
1554	undef $handle;	2442	undef $handle;
1555	});	2443	});
1556		2444
		2445	If you just want to queue some data and then signal EOF to the other side,
		2446	consider using C<< ->push_shutdown >> instead.
		2447
		2448	=item I want to contact a TLS/SSL server, I don't care about security.
		2449
		2450	If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
		2451	connect to it and then create the AnyEvent::Handle with the C<tls>
		2452	parameter:
		2453
		2454	tcp_connect $host, $port, sub {
		2455	my ($fh) = @_;
		2456
		2457	my $handle = new AnyEvent::Handle
		2458	fh => $fh,
		2459	tls => "connect",
		2460	on_error => sub { ... };
		2461
		2462	$handle->push_write (...);
		2463	};
		2464
		2465	=item I want to contact a TLS/SSL server, I do care about security.
		2466
		2467	Then you should additionally enable certificate verification, including
		2468	peername verification, if the protocol you use supports it (see
		2469	L<AnyEvent::TLS>, C<verify_peername>).
		2470
		2471	E.g. for HTTPS:
		2472
		2473	tcp_connect $host, $port, sub {
		2474	my ($fh) = @_;
		2475
		2476	my $handle = new AnyEvent::Handle
		2477	fh => $fh,
		2478	peername => $host,
		2479	tls => "connect",
		2480	tls_ctx => { verify => 1, verify_peername => "https" },
		2481	...
		2482
		2483	Note that you must specify the hostname you connected to (or whatever
		2484	"peername" the protocol needs) as the C<peername> argument, otherwise no
		2485	peername verification will be done.
		2486
		2487	The above will use the system-dependent default set of trusted CA
		2488	certificates. If you want to check against a specific CA, add the
		2489	C<ca_file> (or C<ca_cert>) arguments to C<tls_ctx>:
		2490
		2491	tls_ctx => {
		2492	verify => 1,
		2493	verify_peername => "https",
		2494	ca_file => "my-ca-cert.pem",
		2495	},
		2496
		2497	=item I want to create a TLS/SSL server, how do I do that?
		2498
		2499	Well, you first need to get a server certificate and key. You have
		2500	three options: a) ask a CA (buy one, use cacert.org etc.) b) create a
		2501	self-signed certificate (cheap. check the search engine of your choice,
		2502	there are many tutorials on the net) or c) make your own CA (tinyca2 is a
		2503	nice program for that purpose).
		2504
		2505	Then create a file with your private key (in PEM format, see
		2506	L<AnyEvent::TLS>), followed by the certificate (also in PEM format). The
		2507	file should then look like this:
		2508
		2509	-----BEGIN RSA PRIVATE KEY-----
		2510	...header data
		2511	... lots of base64'y-stuff
		2512	-----END RSA PRIVATE KEY-----
		2513
		2514	-----BEGIN CERTIFICATE-----
		2515	... lots of base64'y-stuff
		2516	-----END CERTIFICATE-----
		2517
		2518	The important bits are the "PRIVATE KEY" and "CERTIFICATE" parts. Then
		2519	specify this file as C<cert_file>:
		2520
		2521	tcp_server undef, $port, sub {
		2522	my ($fh) = @_;
		2523
		2524	my $handle = new AnyEvent::Handle
		2525	fh => $fh,
		2526	tls => "accept",
		2527	tls_ctx => { cert_file => "my-server-keycert.pem" },
		2528	...
		2529
		2530	When you have intermediate CA certificates that your clients might not
		2531	know about, just append them to the C<cert_file>.
		2532
1557	=back	2533	=back
1558
1559		2534
1560	=head1 SUBCLASSING AnyEvent::Handle	2535	=head1 SUBCLASSING AnyEvent::Handle
1561		2536
1562	In many cases, you might want to subclass AnyEvent::Handle.	2537	In many cases, you might want to subclass AnyEvent::Handle.
1563		2538
…		…
1580		2555
1581	=item * all members not documented here and not prefixed with an underscore	2556	=item * all members not documented here and not prefixed with an underscore
1582	are free to use in subclasses.	2557	are free to use in subclasses.
1583		2558
1584	Of course, new versions of AnyEvent::Handle may introduce more "public"	2559	Of course, new versions of AnyEvent::Handle may introduce more "public"
1585	member variables, but thats just life, at least it is documented.	2560	member variables, but that's just life. At least it is documented.
1586		2561
1587	=back	2562	=back
1588		2563
1589	=head1 AUTHOR	2564	=head1 AUTHOR
1590		2565
1591	Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>.	2566	Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>.
1592		2567
1593	=cut	2568	=cut
1594		2569
1595	1; # End of AnyEvent::Handle	2570	1
		2571

Diff Legend

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