[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent/Handle.pm

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.202 by root, Sat Oct 16 02:01:54 2010 UTC vs.
Revision 1.243 by root, Mon Mar 16 08:15:46 2015 UTC

…		…
11		11
12	my $hdl; $hdl = new AnyEvent::Handle	12	my $hdl; $hdl = new AnyEvent::Handle
13	fh => \*STDIN,	13	fh => \*STDIN,
14	on_error => sub {	14	on_error => sub {
15	my ($hdl, $fatal, $msg) = @_;	15	my ($hdl, $fatal, $msg) = @_;
16	warn "got error $msg\n";	16	AE::log error => $msg;
17	$hdl->destroy;	17	$hdl->destroy;
18	$cv->send;	18	$cv->send;
19	};	19	};
20		20
21	# send some request line	21	# send some request line
22	$hdl->push_write ("getinfo\015\012");	22	$hdl->push_write ("getinfo\015\012");
23		23
24	# read the response line	24	# read the response line
25	$hdl->push_read (line => sub {	25	$hdl->push_read (line => sub {
26	my ($hdl, $line) = @_;	26	my ($hdl, $line) = @_;
27	warn "got line <$line>\n";	27	say "got line <$line>";
28	$cv->send;	28	$cv->send;
29	});	29	});
30		30
31	$cv->recv;	31	$cv->recv;
32		32
…		…
53	package AnyEvent::Handle;	53	package AnyEvent::Handle;
54		54
55	use Scalar::Util ();	55	use Scalar::Util ();
56	use List::Util ();	56	use List::Util ();
57	use Carp ();	57	use Carp ();
58	use Errno qw(EAGAIN EINTR);	58	use Errno qw(EAGAIN EWOULDBLOCK EINTR);
59		59
60	use AnyEvent (); BEGIN { AnyEvent::common_sense }	60	use AnyEvent (); BEGIN { AnyEvent::common_sense }
61	use AnyEvent::Util qw(WSAEWOULDBLOCK);	61	use AnyEvent::Util qw(WSAEWOULDBLOCK);
62		62
63	our $VERSION = $AnyEvent::VERSION;	63	our $VERSION = $AnyEvent::VERSION;
…		…
75	}	75	}
76		76
77	\&$func	77	\&$func
78	}	78	}
79		79
		80	sub MAX_READ_SIZE() { 131072 }
		81
80	=head1 METHODS	82	=head1 METHODS
81		83
82	=over 4	84	=over 4
83		85
84	=item $handle = B<new> AnyEvent::Handle fh => $filehandle, key => value...	86	=item $handle = B<new> AnyEvent::Handle fh => $filehandle, key => value...
…		…
112	=over 4	114	=over 4
113		115
114	=item on_prepare => $cb->($handle)	116	=item on_prepare => $cb->($handle)
115		117
116	This (rarely used) callback is called before a new connection is	118	This (rarely used) callback is called before a new connection is
117	attempted, but after the file handle has been created. It could be used to	119	attempted, but after the file handle has been created (you can access that
		120	file handle via C<< $handle->{fh} >>). It could be used to prepare the
118	prepare the file handle with parameters required for the actual connect	121	file handle with parameters required for the actual connect (as opposed to
119	(as opposed to settings that can be changed when the connection is already	122	settings that can be changed when the connection is already established).
120	established).
121		123
122	The return value of this callback should be the connect timeout value in	124	The return value of this callback should be the connect timeout value in
123	seconds (or C<0>, or C<undef>, or the empty list, to indicate that the	125	seconds (or C<0>, or C<undef>, or the empty list, to indicate that the
124	default timeout is to be used).	126	default timeout is to be used).
125		127
126	=item on_connect => $cb->($handle, $host, $port, $retry->())	128	=item on_connect => $cb->($handle, $host, $port, $retry->())
127		129
128	This callback is called when a connection has been successfully established.	130	This callback is called when a connection has been successfully established.
129		131
130	The peer's numeric host and port (the socket peername) are passed as	132	The peer's numeric host and port (the socket peername) are passed as
131	parameters, together with a retry callback.	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.
132		136
133	If, for some reason, the handle is not acceptable, calling C<$retry>	137	If, for some reason, the handle is not acceptable, calling C<$retry> will
134	will continue with the next connection target (in case of multi-homed	138	continue with the next connection target (in case of multi-homed hosts or
135	hosts or SRV records there can be multiple connection endpoints). At the	139	SRV records there can be multiple connection endpoints). The C<$retry>
136	time it is called the read and write queues, eof status, tls status and	140	callback can be invoked after the connect callback returns, i.e. one can
137	similar properties of the handle will have been reset.	141	start a handshake and then decide to retry with the next host if the
		142	handshake fails.
138		143
139	In most cases, you should ignore the C<$retry> parameter.	144	In most cases, you should ignore the C<$retry> parameter.
140		145
141	=item on_connect_error => $cb->($handle, $message)	146	=item on_connect_error => $cb->($handle, $message)
142		147
…		…
157		162
158	Some errors are fatal (which is indicated by C<$fatal> being true). On	163	Some errors are fatal (which is indicated by C<$fatal> being true). On
159	fatal errors the handle object will be destroyed (by a call to C<< ->	164	fatal errors the handle object will be destroyed (by a call to C<< ->
160	destroy >>) after invoking the error callback (which means you are free to	165	destroy >>) after invoking the error callback (which means you are free to
161	examine the handle object). Examples of fatal errors are an EOF condition	166	examine the handle object). Examples of fatal errors are an EOF condition
162	with active (but unsatisifable) read watchers (C<EPIPE>) or I/O errors. In	167	with active (but unsatisfiable) read watchers (C<EPIPE>) or I/O errors. In
163	cases where the other side can close the connection at will, it is	168	cases where the other side can close the connection at will, it is
164	often easiest to not report C<EPIPE> errors in this callback.	169	often easiest to not report C<EPIPE> errors in this callback.
165		170
166	AnyEvent::Handle tries to find an appropriate error code for you to check	171	AnyEvent::Handle tries to find an appropriate error code for you to check
167	against, but in some cases (TLS errors), this does not work well. It is	172	against, but in some cases (TLS errors), this does not work well.
168	recommended to always output the C<$message> argument in human-readable	173
169	error messages (it's usually the same as C<"$!">).	174	If you report the error to the user, it is recommended to always output
		175	the C<$message> argument in human-readable error messages (you don't need
		176	to report C<"$!"> if you report C<$message>).
		177
		178	If you want to react programmatically to the error, then looking at C<$!>
		179	and comparing it against some of the documented C<Errno> values is usually
		180	better than looking at the C<$message>.
170		181
171	Non-fatal errors can be retried by returning, but it is recommended	182	Non-fatal errors can be retried by returning, but it is recommended
172	to simply ignore this parameter and instead abondon the handle object	183	to simply ignore this parameter and instead abondon the handle object
173	when this callback is invoked. Examples of non-fatal errors are timeouts	184	when this callback is invoked. Examples of non-fatal errors are timeouts
174	C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).	185	C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
…		…
222	If an EOF condition has been detected but no C<on_eof> callback has been	233	If an EOF condition has been detected but no C<on_eof> callback has been
223	set, then a fatal error will be raised with C<$!> set to <0>.	234	set, then a fatal error will be raised with C<$!> set to <0>.
224		235
225	=item on_drain => $cb->($handle)	236	=item on_drain => $cb->($handle)
226		237
227	This sets the callback that is called when the write buffer becomes empty	238	This sets the callback that is called once when the write buffer becomes
228	(or immediately if the buffer is empty already).	239	empty (and immediately when the handle object is created).
229		240
230	To append to the write buffer, use the C<< ->push_write >> method.	241	To append to the write buffer, use the C<< ->push_write >> method.
231		242
232	This callback is useful when you don't want to put all of your write data	243	This callback is useful when you don't want to put all of your write data
233	into the queue at once, for example, when you want to write the contents	244	into the queue at once, for example, when you want to write the contents
…		…
245	many seconds pass without a successful read or write on the underlying	256	many seconds pass without a successful read or write on the underlying
246	file handle (or a call to C<timeout_reset>), the C<on_timeout> callback	257	file handle (or a call to C<timeout_reset>), the C<on_timeout> callback
247	will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>	258	will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>
248	error will be raised).	259	error will be raised).
249		260
250	There are three variants of the timeouts that work independently	261	There are three variants of the timeouts that work independently of each
251	of each other, for both read and write, just read, and just write:	262	other, for both read and write (triggered when nothing was read I<OR>
		263	written), just read (triggered when nothing was read), and just write:
252	C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks	264	C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks
253	C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions	265	C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions
254	C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>.	266	C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>.
255		267
256	Note that timeout processing is active even when you do not have	268	Note that timeout processing is active even when you do not have any
257	any outstanding read or write requests: If you plan to keep the connection	269	outstanding read or write requests: If you plan to keep the connection
258	idle then you should disable the timeout temporarily or ignore the timeout	270	idle then you should disable the timeout temporarily or ignore the
259	in the C<on_timeout> callback, in which case AnyEvent::Handle will simply	271	timeout in the corresponding C<on_timeout> callback, in which case
260	restart the timeout.	272	AnyEvent::Handle will simply restart the timeout.
261		273
262	Zero (the default) disables this timeout.	274	Zero (the default) disables the corresponding timeout.
263		275
264	=item on_timeout => $cb->($handle)	276	=item on_timeout => $cb->($handle)
		277
		278	=item on_rtimeout => $cb->($handle)
		279
		280	=item on_wtimeout => $cb->($handle)
265		281
266	Called whenever the inactivity timeout passes. If you return from this	282	Called whenever the inactivity timeout passes. If you return from this
267	callback, then the timeout will be reset as if some activity had happened,	283	callback, then the timeout will be reset as if some activity had happened,
268	so this condition is not fatal in any way.	284	so this condition is not fatal in any way.
269		285
…		…
276	For example, a server accepting connections from untrusted sources should	292	For example, a server accepting connections from untrusted sources should
277	be configured to accept only so-and-so much data that it cannot act on	293	be configured to accept only so-and-so much data that it cannot act on
278	(for example, when expecting a line, an attacker could send an unlimited	294	(for example, when expecting a line, an attacker could send an unlimited
279	amount of data without a callback ever being called as long as the line	295	amount of data without a callback ever being called as long as the line
280	isn't finished).	296	isn't finished).
		297
		298	=item wbuf_max => <bytes>
		299
		300	If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
		301	when the write buffer ever (strictly) exceeds this size. This is useful to
		302	avoid some forms of denial-of-service attacks.
		303
		304	Although the units of this parameter is bytes, this is the I<raw> number
		305	of bytes not yet accepted by the kernel. This can make a difference when
		306	you e.g. use TLS, as TLS typically makes your write data larger (but it
		307	can also make it smaller due to compression).
		308
		309	As an example of when this limit is useful, take a chat server that sends
		310	chat messages to a client. If the client does not read those in a timely
		311	manner then the send buffer in the server would grow unbounded.
281		312
282	=item autocork => <boolean>	313	=item autocork => <boolean>
283		314
284	When disabled (the default), C<push_write> will try to immediately	315	When disabled (the default), C<push_write> will try to immediately
285	write the data to the handle if possible. This avoids having to register	316	write the data to the handle if possible. This avoids having to register
…		…
337	already have occured on BSD systems), but at least it will protect you	368	already have occured on BSD systems), but at least it will protect you
338	from most attacks.	369	from most attacks.
339		370
340	=item read_size => <bytes>	371	=item read_size => <bytes>
341		372
342	The default read block size (the number of bytes this module will	373	The initial read block size, the number of bytes this module will try
343	try to read during each loop iteration, which affects memory	374	to read during each loop iteration. Each handle object will consume
344	requirements). Default: C<8192>.	375	at least this amount of memory for the read buffer as well, so when
		376	handling many connections watch out for memory requirements). See also
		377	C<max_read_size>. Default: C<2048>.
		378
		379	=item max_read_size => <bytes>
		380
		381	The maximum read buffer size used by the dynamic adjustment
		382	algorithm: Each time AnyEvent::Handle can read C<read_size> bytes in
		383	one go it will double C<read_size> up to the maximum given by this
		384	option. Default: C<131072> or C<read_size>, whichever is higher.
345		385
346	=item low_water_mark => <bytes>	386	=item low_water_mark => <bytes>
347		387
348	Sets the number of bytes (default: C<0>) that make up an "empty" write	388	Sets the number of bytes (default: C<0>) that make up an "empty" write
349	buffer: If the buffer reaches this size or gets even samller it is	389	buffer: If the buffer reaches this size or gets even samller it is
…		…
386	appropriate error message.	426	appropriate error message.
387		427
388	TLS mode requires Net::SSLeay to be installed (it will be loaded	428	TLS mode requires Net::SSLeay to be installed (it will be loaded
389	automatically when you try to create a TLS handle): this module doesn't	429	automatically when you try to create a TLS handle): this module doesn't
390	have a dependency on that module, so if your module requires it, you have	430	have a dependency on that module, so if your module requires it, you have
391	to add the dependency yourself.	431	to add the dependency yourself. If Net::SSLeay cannot be loaded or is too
		432	old, you get an C<EPROTO> error.
392		433
393	Unlike TCP, TLS has a server and client side: for the TLS server side, use	434	Unlike TCP, TLS has a server and client side: for the TLS server side, use
394	C<accept>, and for the TLS client side of a connection, use C<connect>	435	C<accept>, and for the TLS client side of a connection, use C<connect>
395	mode.	436	mode.
396		437
…		…
412	Use the C<< ->starttls >> method if you need to start TLS negotiation later.	453	Use the C<< ->starttls >> method if you need to start TLS negotiation later.
413		454
414	=item tls_ctx => $anyevent_tls	455	=item tls_ctx => $anyevent_tls
415		456
416	Use the given C<AnyEvent::TLS> object to create the new TLS connection	457	Use the given C<AnyEvent::TLS> object to create the new TLS connection
417	(unless a connection object was specified directly). If this parameter is	458	(unless a connection object was specified directly). If this
418	missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.	459	parameter is missing (or C<undef>), then AnyEvent::Handle will use
		460	C<AnyEvent::Handle::TLS_CTX>.
419		461
420	Instead of an object, you can also specify a hash reference with C<< key	462	Instead of an object, you can also specify a hash reference with C<< key
421	=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a	463	=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
422	new TLS context object.	464	new TLS context object.
423		465
…		…
451	callback.	493	callback.
452		494
453	This callback will only be called on TLS shutdowns, not when the	495	This callback will only be called on TLS shutdowns, not when the
454	underlying handle signals EOF.	496	underlying handle signals EOF.
455		497
456	=item json => JSON or JSON::XS object	498	=item json => L<JSON>, L<JSON::PP> or L<JSON::XS> object
457		499
458	This is the json coder object used by the C<json> read and write types.	500	This is the json coder object used by the C<json> read and write types.
459		501
460	If you don't supply it, then AnyEvent::Handle will create and use a	502	If you don't supply it, then AnyEvent::Handle will create and use a
461	suitable one (on demand), which will write and expect UTF-8 encoded JSON	503	suitable one (on demand), which will write and expect UTF-8 encoded
		504	JSON texts (either using L<JSON::XS> or L<JSON>). The written texts are
		505	guaranteed not to contain any newline character.
		506
		507	For security reasons, this encoder will likely I<not> handle numbers and
		508	strings, only arrays and objects/hashes. The reason is that originally
		509	JSON was self-delimited, but Dougles Crockford thought it was a splendid
		510	idea to redefine JSON incompatibly, so this is no longer true.
		511
		512	For protocols that used back-to-back JSON texts, this might lead to
		513	run-ins, where two or more JSON texts will be interpreted as one JSON
462	texts.	514	text.
463		515
		516	For this reason, if the default encoder uses L<JSON::XS>, it will default
		517	to not allowing anything but arrays and objects/hashes, at least for the
		518	forseeable future (it will change at some point). This might or might not
		519	be true for the L<JSON> module, so this might cause a security issue.
		520
		521	If you depend on either behaviour, you should create your own json object
		522	and pass it in explicitly.
		523
		524	=item cbor => L<CBOR::XS> object
		525
		526	This is the cbor coder object used by the C<cbor> read and write types.
		527
		528	If you don't supply it, then AnyEvent::Handle will create and use a
		529	suitable one (on demand), which will write CBOR without using extensions,
		530	if possible.
		531
464	Note that you are responsible to depend on the JSON module if you want to	532	Note that you are responsible to depend on the L<CBOR::XS> module if you
465	use this functionality, as AnyEvent does not have a dependency itself.	533	want to use this functionality, as AnyEvent does not have a dependency on
		534	it itself.
466		535
467	=back	536	=back
468		537
469	=cut	538	=cut
470		539
…		…
492	$self->{connect}[0],	561	$self->{connect}[0],
493	$self->{connect}[1],	562	$self->{connect}[1],
494	sub {	563	sub {
495	my ($fh, $host, $port, $retry) = @_;	564	my ($fh, $host, $port, $retry) = @_;
496		565
		566	delete $self->{_connect}; # no longer needed
		567
497	if ($fh) {	568	if ($fh) {
498	$self->{fh} = $fh;	569	$self->{fh} = $fh;
499		570
500	delete $self->{_skip_drain_rbuf};	571	delete $self->{_skip_drain_rbuf};
501	$self->_start;	572	$self->_start;
…		…
508	});	579	});
509		580
510	} else {	581	} else {
511	if ($self->{on_connect_error}) {	582	if ($self->{on_connect_error}) {
512	$self->{on_connect_error}($self, "$!");	583	$self->{on_connect_error}($self, "$!");
513	$self->destroy;	584	$self->destroy if $self;
514	} else {	585	} else {
515	$self->_error ($!, 1);	586	$self->_error ($!, 1);
516	}	587	}
517	}	588	}
518	},	589	},
519	sub {	590	sub {
520	local $self->{fh} = $_[0];	591	local $self->{fh} = $_[0];
521		592
522	$self->{on_prepare}	593	$self->{on_prepare}
523	? $self->{on_prepare}->($self)	594	? $self->{on_prepare}->($self)
524	: ()	595	: ()
525	}	596	}
526	);	597	);
527	}	598	}
528		599
…		…
545	AnyEvent::Util::fh_nonblocking $self->{fh}, 1;	616	AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
546		617
547	$self->{_activity} =	618	$self->{_activity} =
548	$self->{_ractivity} =	619	$self->{_ractivity} =
549	$self->{_wactivity} = AE::now;	620	$self->{_wactivity} = AE::now;
		621
		622	$self->{read_size} \|\|= 2048;
		623	$self->{max_read_size} = $self->{read_size}
		624	if $self->{read_size} > ($self->{max_read_size} \|\| MAX_READ_SIZE);
550		625
551	$self->timeout (delete $self->{timeout} ) if $self->{timeout};	626	$self->timeout (delete $self->{timeout} ) if $self->{timeout};
552	$self->rtimeout (delete $self->{rtimeout} ) if $self->{rtimeout};	627	$self->rtimeout (delete $self->{rtimeout} ) if $self->{rtimeout};
553	$self->wtimeout (delete $self->{wtimeout} ) if $self->{wtimeout};	628	$self->wtimeout (delete $self->{wtimeout} ) if $self->{wtimeout};
554		629
…		…
723		798
724	=item $handle->rbuf_max ($max_octets)	799	=item $handle->rbuf_max ($max_octets)
725		800
726	Configures the C<rbuf_max> setting (C<undef> disables it).	801	Configures the C<rbuf_max> setting (C<undef> disables it).
727		802
		803	=item $handle->wbuf_max ($max_octets)
		804
		805	Configures the C<wbuf_max> setting (C<undef> disables it).
		806
728	=cut	807	=cut
729		808
730	sub rbuf_max {	809	sub rbuf_max {
731	$_[0]{rbuf_max} = $_[1];	810	$_[0]{rbuf_max} = $_[1];
732	}	811	}
733		812
		813	sub wbuf_max {
		814	$_[0]{wbuf_max} = $_[1];
		815	}
		816
734	#############################################################################	817	#############################################################################
735		818
736	=item $handle->timeout ($seconds)	819	=item $handle->timeout ($seconds)
737		820
738	=item $handle->rtimeout ($seconds)	821	=item $handle->rtimeout ($seconds)
739		822
740	=item $handle->wtimeout ($seconds)	823	=item $handle->wtimeout ($seconds)
741		824
742	Configures (or disables) the inactivity timeout.	825	Configures (or disables) the inactivity timeout.
		826
		827	The timeout will be checked instantly, so this method might destroy the
		828	handle before it returns.
743		829
744	=item $handle->timeout_reset	830	=item $handle->timeout_reset
745		831
746	=item $handle->rtimeout_reset	832	=item $handle->rtimeout_reset
747		833
…		…
831		917
832	The write queue is very simple: you can add data to its end, and	918	The write queue is very simple: you can add data to its end, and
833	AnyEvent::Handle will automatically try to get rid of it for you.	919	AnyEvent::Handle will automatically try to get rid of it for you.
834		920
835	When data could be written and the write buffer is shorter then the low	921	When data could be written and the write buffer is shorter then the low
836	water mark, the C<on_drain> callback will be invoked.	922	water mark, the C<on_drain> callback will be invoked once.
837		923
838	=over 4	924	=over 4
839		925
840	=item $handle->on_drain ($cb)	926	=item $handle->on_drain ($cb)
841		927
…		…
856	if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});	942	if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
857	}	943	}
858		944
859	=item $handle->push_write ($data)	945	=item $handle->push_write ($data)
860		946
861	Queues the given scalar to be written. You can push as much data as you	947	Queues the given scalar to be written. You can push as much data as
862	want (only limited by the available memory), as C<AnyEvent::Handle>	948	you want (only limited by the available memory and C<wbuf_max>), as
863	buffers it independently of the kernel.	949	C<AnyEvent::Handle> buffers it independently of the kernel.
864		950
865	This method may invoke callbacks (and therefore the handle might be	951	This method may invoke callbacks (and therefore the handle might be
866	destroyed after it returns).	952	destroyed after it returns).
867		953
868	=cut	954	=cut
…		…
885	$self->{on_drain}($self)	971	$self->{on_drain}($self)
886	if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})	972	if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
887	&& $self->{on_drain};	973	&& $self->{on_drain};
888		974
889	delete $self->{_ww} unless length $self->{wbuf};	975	delete $self->{_ww} unless length $self->{wbuf};
890	} elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {	976	} elsif ($! != EAGAIN && $! != EINTR && $! != EWOULDBLOCK && $! != WSAEWOULDBLOCK) {
891	$self->_error ($!, 1);	977	$self->_error ($!, 1);
892	}	978	}
893	};	979	};
894		980
895	# try to write data immediately	981	# try to write data immediately
896	$cb->() unless $self->{autocork};	982	$cb->() unless $self->{autocork};
897		983
898	# if still data left in wbuf, we need to poll	984	# if still data left in wbuf, we need to poll
899	$self->{_ww} = AE::io $self->{fh}, 1, $cb	985	$self->{_ww} = AE::io $self->{fh}, 1, $cb
900	if length $self->{wbuf};	986	if length $self->{wbuf};
		987
		988	if (
		989	defined $self->{wbuf_max}
		990	&& $self->{wbuf_max} < length $self->{wbuf}
		991	) {
		992	$self->_error (Errno::ENOSPC, 1), return;
		993	}
901	};	994	};
902	}	995	}
903		996
904	our %WH;	997	our %WH;
905		998
…		…
976		1069
977	Encodes the given hash or array reference into a JSON object. Unless you	1070	Encodes the given hash or array reference into a JSON object. Unless you
978	provide your own JSON object, this means it will be encoded to JSON text	1071	provide your own JSON object, this means it will be encoded to JSON text
979	in UTF-8.	1072	in UTF-8.
980		1073
		1074	The default encoder might or might not handle every type of JSON value -
		1075	it might be limited to arrays and objects for security reasons. See the
		1076	C<json> constructor attribute for more details.
		1077
981	JSON objects (and arrays) are self-delimiting, so you can write JSON at	1078	JSON objects (and arrays) are self-delimiting, so if you only use arrays
982	one end of a handle and read them at the other end without using any	1079	and hashes, you can write JSON at one end of a handle and read them at the
983	additional framing.	1080	other end without using any additional framing.
984		1081
985	The generated JSON text is guaranteed not to contain any newlines: While	1082	The JSON text generated by the default encoder is guaranteed not to
986	this module doesn't need delimiters after or between JSON texts to be	1083	contain any newlines: While this module doesn't need delimiters after or
987	able to read them, many other languages depend on that.	1084	between JSON texts to be able to read them, many other languages depend on
		1085	them.
988		1086
989	A simple RPC protocol that interoperates easily with others is to send	1087	A simple RPC protocol that interoperates easily with other languages is
990	JSON arrays (or objects, although arrays are usually the better choice as	1088	to send JSON arrays (or objects, although arrays are usually the better
991	they mimic how function argument passing works) and a newline after each	1089	choice as they mimic how function argument passing works) and a newline
992	JSON text:	1090	after each JSON text:
993		1091
994	$handle->push_write (json => ["method", "arg1", "arg2"]); # whatever	1092	$handle->push_write (json => ["method", "arg1", "arg2"]); # whatever
995	$handle->push_write ("\012");	1093	$handle->push_write ("\012");
996		1094
997	An AnyEvent::Handle receiver would simply use the C<json> read type and	1095	An AnyEvent::Handle receiver would simply use the C<json> read type and
…		…
1000	$handle->push_read (json => sub { my $array = $_[1]; ... });	1098	$handle->push_read (json => sub { my $array = $_[1]; ... });
1001		1099
1002	Other languages could read single lines terminated by a newline and pass	1100	Other languages could read single lines terminated by a newline and pass
1003	this line into their JSON decoder of choice.	1101	this line into their JSON decoder of choice.
1004		1102
		1103	=item cbor => $perl_scalar
		1104
		1105	Encodes the given scalar into a CBOR value. Unless you provide your own
		1106	L<CBOR::XS> object, this means it will be encoded to a CBOR string not
		1107	using any extensions, if possible.
		1108
		1109	CBOR values are self-delimiting, so you can write CBOR at one end of
		1110	a handle and read them at the other end without using any additional
		1111	framing.
		1112
		1113	A simple nd very very fast RPC protocol that interoperates with
		1114	other languages is to send CBOR and receive CBOR values (arrays are
		1115	recommended):
		1116
		1117	$handle->push_write (cbor => ["method", "arg1", "arg2"]); # whatever
		1118
		1119	An AnyEvent::Handle receiver would simply use the C<cbor> read type:
		1120
		1121	$handle->push_read (cbor => sub { my $array = $_[1]; ... });
		1122
1005	=cut	1123	=cut
1006		1124
1007	sub json_coder() {	1125	sub json_coder() {
1008	eval { require JSON::XS; JSON::XS->new->utf8 }	1126	eval { require JSON::XS; JSON::XS->new->utf8 }
1009	\|\| do { require JSON; JSON->new->utf8 }	1127	\|\| do { require JSON::PP; JSON::PP->new->utf8 }
1010	}	1128	}
1011		1129
1012	register_write_type json => sub {	1130	register_write_type json => sub {
1013	my ($self, $ref) = @_;	1131	my ($self, $ref) = @_;
1014		1132
1015	my $json = $self->{json} \|\|= json_coder;	1133	($self->{json} \|\|= json_coder)
1016
1017	$json->encode ($ref)	1134	->encode ($ref)
		1135	};
		1136
		1137	sub cbor_coder() {
		1138	require CBOR::XS;
		1139	CBOR::XS->new
		1140	}
		1141
		1142	register_write_type cbor => sub {
		1143	my ($self, $scalar) = @_;
		1144
		1145	($self->{cbor} \|\|= cbor_coder)
		1146	->encode ($scalar)
1018	};	1147	};
1019		1148
1020	=item storable => $reference	1149	=item storable => $reference
1021		1150
1022	Freezes the given reference using L<Storable> and writes it to the	1151	Freezes the given reference using L<Storable> and writes it to the
…		…
1025	=cut	1154	=cut
1026		1155
1027	register_write_type storable => sub {	1156	register_write_type storable => sub {
1028	my ($self, $ref) = @_;	1157	my ($self, $ref) = @_;
1029		1158
1030	require Storable;	1159	require Storable unless $Storable::VERSION;
1031		1160
1032	pack "w/a*", Storable::nfreeze ($ref)	1161	pack "w/a*", Storable::nfreeze ($ref)
1033	};	1162	};
1034		1163
1035	=back	1164	=back
…		…
1040	before it was actually written. One way to do that is to replace your	1169	before it was actually written. One way to do that is to replace your
1041	C<on_drain> handler by a callback that shuts down the socket (and set	1170	C<on_drain> handler by a callback that shuts down the socket (and set
1042	C<low_water_mark> to C<0>). This method is a shorthand for just that, and	1171	C<low_water_mark> to C<0>). This method is a shorthand for just that, and
1043	replaces the C<on_drain> callback with:	1172	replaces the C<on_drain> callback with:
1044		1173
1045	sub { shutdown $_[0]{fh}, 1 } # for push_shutdown	1174	sub { shutdown $_[0]{fh}, 1 }
1046		1175
1047	This simply shuts down the write side and signals an EOF condition to the	1176	This simply shuts down the write side and signals an EOF condition to the
1048	the peer.	1177	the peer.
1049		1178
1050	You can rely on the normal read queue and C<on_eof> handling	1179	You can rely on the normal read queue and C<on_eof> handling
…		…
1072		1201
1073	Whenever the given C<type> is used, C<push_write> will the function with	1202	Whenever the given C<type> is used, C<push_write> will the function with
1074	the handle object and the remaining arguments.	1203	the handle object and the remaining arguments.
1075		1204
1076	The function is supposed to return a single octet string that will be	1205	The function is supposed to return a single octet string that will be
1077	appended to the write buffer, so you cna mentally treat this function as a	1206	appended to the write buffer, so you can mentally treat this function as a
1078	"arguments to on-the-wire-format" converter.	1207	"arguments to on-the-wire-format" converter.
1079		1208
1080	Example: implement a custom write type C<join> that joins the remaining	1209	Example: implement a custom write type C<join> that joins the remaining
1081	arguments using the first one.	1210	arguments using the first one.
1082		1211
…		…
1376	data.	1505	data.
1377		1506
1378	Example: read 2 bytes.	1507	Example: read 2 bytes.
1379		1508
1380	$handle->push_read (chunk => 2, sub {	1509	$handle->push_read (chunk => 2, sub {
1381	warn "yay ", unpack "H*", $_[1];	1510	say "yay " . unpack "H*", $_[1];
1382	});	1511	});
1383		1512
1384	=cut	1513	=cut
1385		1514
1386	register_read_type chunk => sub {	1515	register_read_type chunk => sub {
…		…
1416		1545
1417	register_read_type line => sub {	1546	register_read_type line => sub {
1418	my ($self, $cb, $eol) = @_;	1547	my ($self, $cb, $eol) = @_;
1419		1548
1420	if (@_ < 3) {	1549	if (@_ < 3) {
1421	# this is more than twice as fast as the generic code below	1550	# this is faster then the generic code below
1422	sub {	1551	sub {
1423	$_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return;	1552	(my $pos = index $_[0]{rbuf}, "\012") >= 0
		1553	or return;
1424		1554
		1555	(my $str = substr $_[0]{rbuf}, 0, $pos + 1, "") =~ s/(\015?\012)\Z// or die;
1425	$cb->($_[0], $1, $2);	1556	$cb->($_[0], $str, "$1");
1426	1	1557	1
1427	}	1558	}
1428	} else {	1559	} else {
1429	$eol = quotemeta $eol unless ref $eol;	1560	$eol = quotemeta $eol unless ref $eol;
1430	$eol = qr\|^(.*?)($eol)\|s;	1561	$eol = qr\|^(.*?)($eol)\|s;
1431		1562
1432	sub {	1563	sub {
1433	$_[0]{rbuf} =~ s/$eol// or return;	1564	$_[0]{rbuf} =~ s/$eol// or return;
1434		1565
1435	$cb->($_[0], $1, $2);	1566	$cb->($_[0], "$1", "$2");
1436	1	1567	1
1437	}	1568	}
1438	}	1569	}
1439	};	1570	};
1440		1571
…		…
1488		1619
1489	sub {	1620	sub {
1490	# accept	1621	# accept
1491	if ($$rbuf =~ $accept) {	1622	if ($$rbuf =~ $accept) {
1492	$data .= substr $$rbuf, 0, $+[0], "";	1623	$data .= substr $$rbuf, 0, $+[0], "";
1493	$cb->($self, $data);	1624	$cb->($_[0], $data);
1494	return 1;	1625	return 1;
1495	}	1626	}
1496		1627
1497	# reject	1628	# reject
1498	if ($reject && $$rbuf =~ $reject) {	1629	if ($reject && $$rbuf =~ $reject) {
1499	$self->_error (Errno::EBADMSG);	1630	$_[0]->_error (Errno::EBADMSG);
1500	}	1631	}
1501		1632
1502	# skip	1633	# skip
1503	if ($skip && $$rbuf =~ $skip) {	1634	if ($skip && $$rbuf =~ $skip) {
1504	$data .= substr $$rbuf, 0, $+[0], "";	1635	$data .= substr $$rbuf, 0, $+[0], "";
…		…
1520	my ($self, $cb) = @_;	1651	my ($self, $cb) = @_;
1521		1652
1522	sub {	1653	sub {
1523	unless ($_[0]{rbuf} =~ s/^(0\|[1-9][0-9]*)://) {	1654	unless ($_[0]{rbuf} =~ s/^(0\|[1-9][0-9]*)://) {
1524	if ($_[0]{rbuf} =~ /[^0-9]/) {	1655	if ($_[0]{rbuf} =~ /[^0-9]/) {
1525	$self->_error (Errno::EBADMSG);	1656	$_[0]->_error (Errno::EBADMSG);
1526	}	1657	}
1527	return;	1658	return;
1528	}	1659	}
1529		1660
1530	my $len = $1;	1661	my $len = $1;
1531		1662
1532	$self->unshift_read (chunk => $len, sub {	1663	$_[0]->unshift_read (chunk => $len, sub {
1533	my $string = $_[1];	1664	my $string = $_[1];
1534	$_[0]->unshift_read (chunk => 1, sub {	1665	$_[0]->unshift_read (chunk => 1, sub {
1535	if ($_[1] eq ",") {	1666	if ($_[1] eq ",") {
1536	$cb->($_[0], $string);	1667	$cb->($_[0], $string);
1537	} else {	1668	} else {
1538	$self->_error (Errno::EBADMSG);	1669	$_[0]->_error (Errno::EBADMSG);
1539	}	1670	}
1540	});	1671	});
1541	});	1672	});
1542		1673
1543	1	1674	1
…		…
1593	=item json => $cb->($handle, $hash_or_arrayref)	1724	=item json => $cb->($handle, $hash_or_arrayref)
1594		1725
1595	Reads a JSON object or array, decodes it and passes it to the	1726	Reads a JSON object or array, decodes it and passes it to the
1596	callback. When a parse error occurs, an C<EBADMSG> error will be raised.	1727	callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1597		1728
1598	If a C<json> object was passed to the constructor, then that will be used	1729	If a C<json> object was passed to the constructor, then that will be
1599	for the final decode, otherwise it will create a JSON coder expecting UTF-8.	1730	used for the final decode, otherwise it will create a L<JSON::XS> or
		1731	L<JSON::PP> coder object expecting UTF-8.
1600		1732
1601	This read type uses the incremental parser available with JSON version	1733	This read type uses the incremental parser available with JSON version
1602	2.09 (and JSON::XS version 2.2) and above. You have to provide a	1734	2.09 (and JSON::XS version 2.2) and above.
1603	dependency on your own: this module will load the JSON module, but
1604	AnyEvent does not depend on it itself.
1605		1735
1606	Since JSON texts are fully self-delimiting, the C<json> read and write	1736	Since JSON texts are fully self-delimiting, the C<json> read and write
1607	types are an ideal simple RPC protocol: just exchange JSON datagrams. See	1737	types are an ideal simple RPC protocol: just exchange JSON datagrams. See
1608	the C<json> write type description, above, for an actual example.	1738	the C<json> write type description, above, for an actual example.
1609		1739
…		…
1613	my ($self, $cb) = @_;	1743	my ($self, $cb) = @_;
1614		1744
1615	my $json = $self->{json} \|\|= json_coder;	1745	my $json = $self->{json} \|\|= json_coder;
1616		1746
1617	my $data;	1747	my $data;
1618	my $rbuf = \$self->{rbuf};
1619		1748
1620	sub {	1749	sub {
1621	my $ref = eval { $json->incr_parse ($self->{rbuf}) };	1750	my $ref = eval { $json->incr_parse ($_[0]{rbuf}) };
1622		1751
1623	if ($ref) {	1752	if ($ref) {
1624	$self->{rbuf} = $json->incr_text;	1753	$_[0]{rbuf} = $json->incr_text;
1625	$json->incr_text = "";	1754	$json->incr_text = "";
1626	$cb->($self, $ref);	1755	$cb->($_[0], $ref);
1627		1756
1628	1	1757	1
1629	} elsif ($@) {	1758	} elsif ($@) {
1630	# error case	1759	# error case
1631	$json->incr_skip;	1760	$json->incr_skip;
1632		1761
1633	$self->{rbuf} = $json->incr_text;	1762	$_[0]{rbuf} = $json->incr_text;
1634	$json->incr_text = "";	1763	$json->incr_text = "";
1635		1764
1636	$self->_error (Errno::EBADMSG);	1765	$_[0]->_error (Errno::EBADMSG);
1637		1766
1638	()	1767	()
1639	} else {	1768	} else {
1640	$self->{rbuf} = "";	1769	$_[0]{rbuf} = "";
1641		1770
		1771	()
		1772	}
		1773	}
		1774	};
		1775
		1776	=item cbor => $cb->($handle, $scalar)
		1777
		1778	Reads a CBOR value, decodes it and passes it to the callback. When a parse
		1779	error occurs, an C<EBADMSG> error will be raised.
		1780
		1781	If a L<CBOR::XS> object was passed to the constructor, then that will be
		1782	used for the final decode, otherwise it will create a CBOR coder without
		1783	enabling any options.
		1784
		1785	You have to provide a dependency to L<CBOR::XS> on your own: this module
		1786	will load the L<CBOR::XS> module, but AnyEvent does not depend on it
		1787	itself.
		1788
		1789	Since CBOR values are fully self-delimiting, the C<cbor> read and write
		1790	types are an ideal simple RPC protocol: just exchange CBOR datagrams. See
		1791	the C<cbor> write type description, above, for an actual example.
		1792
		1793	=cut
		1794
		1795	register_read_type cbor => sub {
		1796	my ($self, $cb) = @_;
		1797
		1798	my $cbor = $self->{cbor} \|\|= cbor_coder;
		1799
		1800	my $data;
		1801
		1802	sub {
		1803	my (@value) = eval { $cbor->incr_parse ($_[0]{rbuf}) };
		1804
		1805	if (@value) {
		1806	$cb->($_[0], @value);
		1807
		1808	1
		1809	} elsif ($@) {
		1810	# error case
		1811	$cbor->incr_reset;
		1812
		1813	$_[0]->_error (Errno::EBADMSG);
		1814
		1815	()
		1816	} else {
1642	()	1817	()
1643	}	1818	}
1644	}	1819	}
1645	};	1820	};
1646		1821
…		…
1655	=cut	1830	=cut
1656		1831
1657	register_read_type storable => sub {	1832	register_read_type storable => sub {
1658	my ($self, $cb) = @_;	1833	my ($self, $cb) = @_;
1659		1834
1660	require Storable;	1835	require Storable unless $Storable::VERSION;
1661		1836
1662	sub {	1837	sub {
1663	# when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method	1838	# when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1664	defined (my $len = eval { unpack "w", $_[0]{rbuf} })	1839	defined (my $len = eval { unpack "w", $_[0]{rbuf} })
1665	or return;	1840	or return;
…		…
1668		1843
1669	# bypass unshift if we already have the remaining chunk	1844	# bypass unshift if we already have the remaining chunk
1670	if ($format + $len <= length $_[0]{rbuf}) {	1845	if ($format + $len <= length $_[0]{rbuf}) {
1671	my $data = substr $_[0]{rbuf}, $format, $len;	1846	my $data = substr $_[0]{rbuf}, $format, $len;
1672	substr $_[0]{rbuf}, 0, $format + $len, "";	1847	substr $_[0]{rbuf}, 0, $format + $len, "";
		1848
1673	$cb->($_[0], Storable::thaw ($data));	1849	eval { $cb->($_[0], Storable::thaw ($data)); 1 }
		1850	or return $_[0]->_error (Errno::EBADMSG);
1674	} else {	1851	} else {
1675	# remove prefix	1852	# remove prefix
1676	substr $_[0]{rbuf}, 0, $format, "";	1853	substr $_[0]{rbuf}, 0, $format, "";
1677		1854
1678	# read remaining chunk	1855	# read remaining chunk
1679	$_[0]->unshift_read (chunk => $len, sub {	1856	$_[0]->unshift_read (chunk => $len, sub {
1680	if (my $ref = eval { Storable::thaw ($_[1]) }) {	1857	eval { $cb->($_[0], Storable::thaw ($_[1])); 1 }
1681	$cb->($_[0], $ref);
1682	} else {
1683	$self->_error (Errno::EBADMSG);	1858	or $_[0]->_error (Errno::EBADMSG);
1684	}
1685	});	1859	});
1686	}	1860	}
1687		1861
1688	1	1862	1
1689	}	1863	}
		1864	};
		1865
		1866	=item tls_detect => $cb->($handle, $detect, $major, $minor)
		1867
		1868	Checks the input stream for a valid SSL or TLS handshake TLSPaintext
		1869	record without consuming anything. Only SSL version 3 or higher
		1870	is handled, up to the fictituous protocol 4.x (but both SSL3+ and
		1871	SSL2-compatible framing is supported).
		1872
		1873	If it detects that the input data is likely TLS, it calls the callback
		1874	with a true value for C<$detect> and the (on-wire) TLS version as second
		1875	and third argument (C<$major> is C<3>, and C<$minor> is 0..3 for SSL
		1876	3.0, TLS 1.0, 1.1 and 1.2, respectively). If it detects the input to
		1877	be definitely not TLS, it calls the callback with a false value for
		1878	C<$detect>.
		1879
		1880	The callback could use this information to decide whether or not to start
		1881	TLS negotiation.
		1882
		1883	In all cases the data read so far is passed to the following read
		1884	handlers.
		1885
		1886	Usually you want to use the C<tls_autostart> read type instead.
		1887
		1888	If you want to design a protocol that works in the presence of TLS
		1889	dtection, make sure that any non-TLS data doesn't start with the octet 22
		1890	(ASCII SYN, 16 hex) or 128-255 (i.e. highest bit set). The checks this
		1891	read type does are a bit more strict, but might losen in the future to
		1892	accomodate protocol changes.
		1893
		1894	This read type does not rely on L<AnyEvent::TLS> (and thus, not on
		1895	L<Net::SSLeay>).
		1896
		1897	=item tls_autostart => $tls[, $tls_ctx]
		1898
		1899	Tries to detect a valid SSL or TLS handshake. If one is detected, it tries
		1900	to start tls by calling C<starttls> with the given arguments.
		1901
		1902	In practise, C<$tls> must be C<accept>, or a Net::SSLeay context that has
		1903	been configured to accept, as servers do not normally send a handshake on
		1904	their own and ths cannot be detected in this way.
		1905
		1906	See C<tls_detect> above for more details.
		1907
		1908	Example: give the client a chance to start TLS before accepting a text
		1909	line.
		1910
		1911	$hdl->push_read (tls_detect => "accept");
		1912	$hdl->push_read (line => sub {
		1913	print "received ", ($_[0]{tls} ? "encrypted" : "cleartext"), " <$_[1]>\n";
		1914	});
		1915
		1916	=cut
		1917
		1918	register_read_type tls_detect => sub {
		1919	my ($self, $cb) = @_;
		1920
		1921	sub {
		1922	# this regex matches a full or partial tls record
		1923	if (
		1924	# ssl3+: type(22=handshake) major(=3) minor(any) length_hi
		1925	$self->{rbuf} =~ /^(?:\z\| \x16 (\z\| [\x03\x04] (?:\z\| . (?:\z\| [\x00-\x40] ))))/xs
		1926	# ssl2 comapatible: len_hi len_lo type(1) major minor dummy(forlength)
		1927	or $self->{rbuf} =~ /^(?:\z\| [\x80-\xff] (?:\z\| . (?:\z\| \x01 (\z\| [\x03\x04] (?:\z\| . (?:\z\| . ))))))/xs
		1928	) {
		1929	return if 3 != length $1; # partial match, can't decide yet
		1930
		1931	# full match, valid TLS record
		1932	my ($major, $minor) = unpack "CC", $1;
		1933	$cb->($self, "accept", $major + $minor * 0.1);
		1934	} else {
		1935	# mismatch == guaranteed not TLS
		1936	$cb->($self, undef);
		1937	}
		1938
		1939	1
		1940	}
		1941	};
		1942
		1943	register_read_type tls_autostart => sub {
		1944	my ($self, @tls) = @_;
		1945
		1946	$RH{tls_detect}($self, sub {
		1947	return unless $_[1];
		1948	$_[0]->starttls (@tls);
		1949	})
1690	};	1950	};
1691		1951
1692	=back	1952	=back
1693		1953
1694	=item custom read types - Package::anyevent_read_type $handle, $cb, @args	1954	=item custom read types - Package::anyevent_read_type $handle, $cb, @args
…		…
1726	Note that AnyEvent::Handle will automatically C<start_read> for you when	1986	Note that AnyEvent::Handle will automatically C<start_read> for you when
1727	you change the C<on_read> callback or push/unshift a read callback, and it	1987	you change the C<on_read> callback or push/unshift a read callback, and it
1728	will automatically C<stop_read> for you when neither C<on_read> is set nor	1988	will automatically C<stop_read> for you when neither C<on_read> is set nor
1729	there are any read requests in the queue.	1989	there are any read requests in the queue.
1730		1990
1731	These methods will have no effect when in TLS mode (as TLS doesn't support	1991	In older versions of this module (<= 5.3), these methods had no effect,
1732	half-duplex connections).	1992	as TLS does not support half-duplex connections. In current versions they
		1993	work as expected, as this behaviour is required to avoid certain resource
		1994	attacks, where the program would be forced to read (and buffer) arbitrary
		1995	amounts of data before being able to send some data. The drawback is that
		1996	some readings of the the SSL/TLS specifications basically require this
		1997	attack to be working, as SSL/TLS implementations might stall sending data
		1998	during a rehandshake.
		1999
		2000	As a guideline, during the initial handshake, you should not stop reading,
		2001	and as a client, it might cause problems, depending on your application.
1733		2002
1734	=cut	2003	=cut
1735		2004
1736	sub stop_read {	2005	sub stop_read {
1737	my ($self) = @_;	2006	my ($self) = @_;
1738		2007
1739	delete $self->{_rw} unless $self->{tls};	2008	delete $self->{_rw};
1740	}	2009	}
1741		2010
1742	sub start_read {	2011	sub start_read {
1743	my ($self) = @_;	2012	my ($self) = @_;
1744		2013
1745	unless ($self->{_rw} \|\| $self->{_eof} \|\| !$self->{fh}) {	2014	unless ($self->{_rw} \|\| $self->{_eof} \|\| !$self->{fh}) {
1746	Scalar::Util::weaken $self;	2015	Scalar::Util::weaken $self;
1747		2016
1748	$self->{_rw} = AE::io $self->{fh}, 0, sub {	2017	$self->{_rw} = AE::io $self->{fh}, 0, sub {
1749	my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});	2018	my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1750	my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} \|\| 8192, length $$rbuf;	2019	my $len = sysread $self->{fh}, $$rbuf, $self->{read_size}, length $$rbuf;
1751		2020
1752	if ($len > 0) {	2021	if ($len > 0) {
1753	$self->{_activity} = $self->{_ractivity} = AE::now;	2022	$self->{_activity} = $self->{_ractivity} = AE::now;
1754		2023
1755	if ($self->{tls}) {	2024	if ($self->{tls}) {
…		…
1758	&_dotls ($self);	2027	&_dotls ($self);
1759	} else {	2028	} else {
1760	$self->_drain_rbuf;	2029	$self->_drain_rbuf;
1761	}	2030	}
1762		2031
		2032	if ($len == $self->{read_size}) {
		2033	$self->{read_size} *= 2;
		2034	$self->{read_size} = $self->{max_read_size} \|\| MAX_READ_SIZE
		2035	if $self->{read_size} > ($self->{max_read_size} \|\| MAX_READ_SIZE);
		2036	}
		2037
1763	} elsif (defined $len) {	2038	} elsif (defined $len) {
1764	delete $self->{_rw};	2039	delete $self->{_rw};
1765	$self->{_eof} = 1;	2040	$self->{_eof} = 1;
1766	$self->_drain_rbuf;	2041	$self->_drain_rbuf;
1767		2042
1768	} elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {	2043	} elsif ($! != EAGAIN && $! != EINTR && $! != EWOULDBLOCK && $! != WSAEWOULDBLOCK) {
1769	return $self->_error ($!, 1);	2044	return $self->_error ($!, 1);
1770	}	2045	}
1771	};	2046	};
1772	}	2047	}
1773	}	2048	}
…		…
1779	my ($self, $err) = @_;	2054	my ($self, $err) = @_;
1780		2055
1781	return $self->_error ($!, 1)	2056	return $self->_error ($!, 1)
1782	if $err == Net::SSLeay::ERROR_SYSCALL ();	2057	if $err == Net::SSLeay::ERROR_SYSCALL ();
1783		2058
1784	my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());	2059	my $err = Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
1785		2060
1786	# reduce error string to look less scary	2061	# reduce error string to look less scary
1787	$err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;	2062	$err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
1788		2063
1789	if ($self->{_on_starttls}) {	2064	if ($self->{_on_starttls}) {
…		…
1803	sub _dotls {	2078	sub _dotls {
1804	my ($self) = @_;	2079	my ($self) = @_;
1805		2080
1806	my $tmp;	2081	my $tmp;
1807		2082
1808	if (length $self->{_tls_wbuf}) {	2083	while (length $self->{_tls_wbuf}) {
1809	while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {	2084	if (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) <= 0) {
1810	substr $self->{_tls_wbuf}, 0, $tmp, "";	2085	$tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
		2086
		2087	return $self->_tls_error ($tmp)
		2088	if $tmp != $ERROR_WANT_READ
		2089	&& ($tmp != $ERROR_SYSCALL \|\| $!);
		2090
		2091	last;
1811	}	2092	}
1812		2093
1813	$tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);	2094	substr $self->{_tls_wbuf}, 0, $tmp, "";
1814	return $self->_tls_error ($tmp)
1815	if $tmp != $ERROR_WANT_READ
1816	&& ($tmp != $ERROR_SYSCALL \|\| $!);
1817	}	2095	}
1818		2096
1819	while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {	2097	while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1820	unless (length $tmp) {	2098	unless (length $tmp) {
1821	$self->{_on_starttls}	2099	$self->{_on_starttls}
…		…
1835	$self->{_tls_rbuf} .= $tmp;	2113	$self->{_tls_rbuf} .= $tmp;
1836	$self->_drain_rbuf;	2114	$self->_drain_rbuf;
1837	$self->{tls} or return; # tls session might have gone away in callback	2115	$self->{tls} or return; # tls session might have gone away in callback
1838	}	2116	}
1839		2117
1840	$tmp = Net::SSLeay::get_error ($self->{tls}, -1);	2118	$tmp = Net::SSLeay::get_error ($self->{tls}, -1); # -1 is not neccessarily correct, but Net::SSLeay doesn't tell us
1841	return $self->_tls_error ($tmp)	2119	return $self->_tls_error ($tmp)
1842	if $tmp != $ERROR_WANT_READ	2120	if $tmp != $ERROR_WANT_READ
1843	&& ($tmp != $ERROR_SYSCALL \|\| $!);	2121	&& ($tmp != $ERROR_SYSCALL \|\| $!);
1844		2122
1845	while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {	2123	while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
…		…
1855		2133
1856	=item $handle->starttls ($tls[, $tls_ctx])	2134	=item $handle->starttls ($tls[, $tls_ctx])
1857		2135
1858	Instead of starting TLS negotiation immediately when the AnyEvent::Handle	2136	Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1859	object is created, you can also do that at a later time by calling	2137	object is created, you can also do that at a later time by calling
1860	C<starttls>.	2138	C<starttls>. See the C<tls> constructor argument for general info.
1861		2139
1862	Starting TLS is currently an asynchronous operation - when you push some	2140	Starting TLS is currently an asynchronous operation - when you push some
1863	write data and then call C<< ->starttls >> then TLS negotiation will start	2141	write data and then call C<< ->starttls >> then TLS negotiation will start
1864	immediately, after which the queued write data is then sent.	2142	immediately, after which the queued write data is then sent. This might
		2143	change in future versions, so best make sure you have no outstanding write
		2144	data when calling this method.
1865		2145
1866	The first argument is the same as the C<tls> constructor argument (either	2146	The first argument is the same as the C<tls> constructor argument (either
1867	C<"connect">, C<"accept"> or an existing Net::SSLeay object).	2147	C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1868		2148
1869	The second argument is the optional C<AnyEvent::TLS> object that is used	2149	The second argument is the optional C<AnyEvent::TLS> object that is used
…		…
1891	my ($self, $tls, $ctx) = @_;	2171	my ($self, $tls, $ctx) = @_;
1892		2172
1893	Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught"	2173	Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught"
1894	if $self->{tls};	2174	if $self->{tls};
1895		2175
		2176	unless (defined $AnyEvent::TLS::VERSION) {
		2177	eval {
		2178	require Net::SSLeay;
		2179	require AnyEvent::TLS;
		2180	1
		2181	} or return $self->_error (Errno::EPROTO, 1, "TLS support not available on this system");
		2182	}
		2183
1896	$self->{tls} = $tls;	2184	$self->{tls} = $tls;
1897	$self->{tls_ctx} = $ctx if @_ > 2;	2185	$self->{tls_ctx} = $ctx if @_ > 2;
1898		2186
1899	return unless $self->{fh};	2187	return unless $self->{fh};
1900		2188
1901	require Net::SSLeay;
1902
1903	$ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();	2189	$ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1904	$ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();	2190	$ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1905		2191
1906	$tls = delete $self->{tls};	2192	$tls = delete $self->{tls};
1907	$ctx = $self->{tls_ctx};	2193	$ctx = $self->{tls_ctx};
1908		2194
1909	local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session	2195	local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
1910		2196
1911	if ("HASH" eq ref $ctx) {	2197	if ("HASH" eq ref $ctx) {
1912	require AnyEvent::TLS;
1913
1914	if ($ctx->{cache}) {	2198	if ($ctx->{cache}) {
1915	my $key = $ctx+0;	2199	my $key = $ctx+0;
1916	$ctx = $TLS_CACHE{$key} \|\|= new AnyEvent::TLS %$ctx;	2200	$ctx = $TLS_CACHE{$key} \|\|= new AnyEvent::TLS %$ctx;
1917	} else {	2201	} else {
1918	$ctx = new AnyEvent::TLS %$ctx;	2202	$ctx = new AnyEvent::TLS %$ctx;
…		…
1940	Net::SSLeay::CTX_set_mode ($tls, 1\|2);	2224	Net::SSLeay::CTX_set_mode ($tls, 1\|2);
1941		2225
1942	$self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());	2226	$self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1943	$self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());	2227	$self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1944		2228
1945	Net::SSLeay::BIO_write ($self->{_rbio}, delete $self->{rbuf});	2229	Net::SSLeay::BIO_write ($self->{_rbio}, $self->{rbuf});
		2230	$self->{rbuf} = "";
1946		2231
1947	Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});	2232	Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});
1948		2233
1949	$self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }	2234	$self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
1950	if $self->{on_starttls};	2235	if $self->{on_starttls};
…		…
1988	if $self->{tls} > 0;	2273	if $self->{tls} > 0;
1989		2274
1990	delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};	2275	delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
1991	}	2276	}
1992		2277
		2278	=item $handle->resettls
		2279
		2280	This rarely-used method simply resets and TLS state on the handle, usually
		2281	causing data loss.
		2282
		2283	One case where it may be useful is when you want to skip over the data in
		2284	the stream but you are not interested in interpreting it, so data loss is
		2285	no concern.
		2286
		2287	=cut
		2288
		2289	*resettls = \&_freetls;
		2290
1993	sub DESTROY {	2291	sub DESTROY {
1994	my ($self) = @_;	2292	my ($self) = @_;
1995		2293
1996	&_freetls;	2294	&_freetls;
1997		2295
…		…
2006	push @linger, AE::io $fh, 1, sub {	2304	push @linger, AE::io $fh, 1, sub {
2007	my $len = syswrite $fh, $wbuf, length $wbuf;	2305	my $len = syswrite $fh, $wbuf, length $wbuf;
2008		2306
2009	if ($len > 0) {	2307	if ($len > 0) {
2010	substr $wbuf, 0, $len, "";	2308	substr $wbuf, 0, $len, "";
2011	} elsif (defined $len \|\| ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK)) {	2309	} elsif (defined $len \|\| ($! != EAGAIN && $! != EINTR && $! != EWOULDBLOCK && $! != WSAEWOULDBLOCK)) {
2012	@linger = (); # end	2310	@linger = (); # end
2013	}	2311	}
2014	};	2312	};
2015	push @linger, AE::timer $linger, 0, sub {	2313	push @linger, AE::timer $linger, 0, sub {
2016	@linger = ();	2314	@linger = ();
…		…
2112		2410
2113	It is only safe to "forget" the reference inside EOF or error callbacks,	2411	It is only safe to "forget" the reference inside EOF or error callbacks,
2114	from within all other callbacks, you need to explicitly call the C<<	2412	from within all other callbacks, you need to explicitly call the C<<
2115	->destroy >> method.	2413	->destroy >> method.
2116		2414
		2415	=item Why is my C<on_eof> callback never called?
		2416
		2417	Probably because your C<on_error> callback is being called instead: When
		2418	you have outstanding requests in your read queue, then an EOF is
		2419	considered an error as you clearly expected some data.
		2420
		2421	To avoid this, make sure you have an empty read queue whenever your handle
		2422	is supposed to be "idle" (i.e. connection closes are O.K.). You can set
		2423	an C<on_read> handler that simply pushes the first read requests in the
		2424	queue.
		2425
		2426	See also the next question, which explains this in a bit more detail.
		2427
		2428	=item How can I serve requests in a loop?
		2429
		2430	Most protocols consist of some setup phase (authentication for example)
		2431	followed by a request handling phase, where the server waits for requests
		2432	and handles them, in a loop.
		2433
		2434	There are two important variants: The first (traditional, better) variant
		2435	handles requests until the server gets some QUIT command, causing it to
		2436	close the connection first (highly desirable for a busy TCP server). A
		2437	client dropping the connection is an error, which means this variant can
		2438	detect an unexpected detection close.
		2439
		2440	To handle this case, always make sure you have a non-empty read queue, by
		2441	pushing the "read request start" handler on it:
		2442
		2443	# we assume a request starts with a single line
		2444	my @start_request; @start_request = (line => sub {
		2445	my ($hdl, $line) = @_;
		2446
		2447	... handle request
		2448
		2449	# push next request read, possibly from a nested callback
		2450	$hdl->push_read (@start_request);
		2451	});
		2452
		2453	# auth done, now go into request handling loop
		2454	# now push the first @start_request
		2455	$hdl->push_read (@start_request);
		2456
		2457	By always having an outstanding C<push_read>, the handle always expects
		2458	some data and raises the C<EPIPE> error when the connction is dropped
		2459	unexpectedly.
		2460
		2461	The second variant is a protocol where the client can drop the connection
		2462	at any time. For TCP, this means that the server machine may run out of
		2463	sockets easier, and in general, it means you cannot distinguish a protocl
		2464	failure/client crash from a normal connection close. Nevertheless, these
		2465	kinds of protocols are common (and sometimes even the best solution to the
		2466	problem).
		2467
		2468	Having an outstanding read request at all times is possible if you ignore
		2469	C<EPIPE> errors, but this doesn't help with when the client drops the
		2470	connection during a request, which would still be an error.
		2471
		2472	A better solution is to push the initial request read in an C<on_read>
		2473	callback. This avoids an error, as when the server doesn't expect data
		2474	(i.e. is idly waiting for the next request, an EOF will not raise an
		2475	error, but simply result in an C<on_eof> callback. It is also a bit slower
		2476	and simpler:
		2477
		2478	# auth done, now go into request handling loop
		2479	$hdl->on_read (sub {
		2480	my ($hdl) = @_;
		2481
		2482	# called each time we receive data but the read queue is empty
		2483	# simply start read the request
		2484
		2485	$hdl->push_read (line => sub {
		2486	my ($hdl, $line) = @_;
		2487
		2488	... handle request
		2489
		2490	# do nothing special when the request has been handled, just
		2491	# let the request queue go empty.
		2492	});
		2493	});
		2494
2117	=item I get different callback invocations in TLS mode/Why can't I pause	2495	=item I get different callback invocations in TLS mode/Why can't I pause
2118	reading?	2496	reading?
2119		2497
2120	Unlike, say, TCP, TLS connections do not consist of two independent	2498	Unlike, say, TCP, TLS connections do not consist of two independent
2121	communication channels, one for each direction. Or put differently, the	2499	communication channels, one for each direction. Or put differently, the
…		…
2142	$handle->on_eof (undef);	2520	$handle->on_eof (undef);
2143	$handle->on_error (sub {	2521	$handle->on_error (sub {
2144	my $data = delete $_[0]{rbuf};	2522	my $data = delete $_[0]{rbuf};
2145	});	2523	});
2146		2524
		2525	Note that this example removes the C<rbuf> member from the handle object,
		2526	which is not normally allowed by the API. It is expressly permitted in
		2527	this case only, as the handle object needs to be destroyed afterwards.
		2528
2147	The reason to use C<on_error> is that TCP connections, due to latencies	2529	The reason to use C<on_error> is that TCP connections, due to latencies
2148	and packets loss, might get closed quite violently with an error, when in	2530	and packets loss, might get closed quite violently with an error, when in
2149	fact all data has been received.	2531	fact all data has been received.
2150		2532
2151	It is usually better to use acknowledgements when transferring data,	2533	It is usually better to use acknowledgements when transferring data,
…		…
2161	C<low_water_mark> this will be called precisely when all data has been	2543	C<low_water_mark> this will be called precisely when all data has been
2162	written to the socket:	2544	written to the socket:
2163		2545
2164	$handle->push_write (...);	2546	$handle->push_write (...);
2165	$handle->on_drain (sub {	2547	$handle->on_drain (sub {
2166	warn "all data submitted to the kernel\n";	2548	AE::log debug => "All data submitted to the kernel.";
2167	undef $handle;	2549	undef $handle;
2168	});	2550	});
2169		2551
2170	If you just want to queue some data and then signal EOF to the other side,	2552	If you just want to queue some data and then signal EOF to the other side,
2171	consider using C<< ->push_shutdown >> instead.	2553	consider using C<< ->push_shutdown >> instead.
…		…
2255	When you have intermediate CA certificates that your clients might not	2637	When you have intermediate CA certificates that your clients might not
2256	know about, just append them to the C<cert_file>.	2638	know about, just append them to the C<cert_file>.
2257		2639
2258	=back	2640	=back
2259		2641
2260
2261	=head1 SUBCLASSING AnyEvent::Handle	2642	=head1 SUBCLASSING AnyEvent::Handle
2262		2643
2263	In many cases, you might want to subclass AnyEvent::Handle.	2644	In many cases, you might want to subclass AnyEvent::Handle.
2264		2645
2265	To make this easier, a given version of AnyEvent::Handle uses these	2646	To make this easier, a given version of AnyEvent::Handle uses these
…		…
2291		2672
2292	Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>.	2673	Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>.
2293		2674
2294	=cut	2675	=cut
2295		2676
2296	1; # End of AnyEvent::Handle	2677	1
		2678

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents): Revision 1.202 by root, Sat Oct 16 02:01:54 2010 UTC vs. Revision 1.243 by root, Mon Mar 16 08:15:46 2015 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.202 by root, Sat Oct 16 02:01:54 2010 UTC vs.
Revision 1.243 by root, Mon Mar 16 08:15:46 2015 UTC