ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/lib/AnyEvent/Handle.pm
(Generate patch)

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.139 by root, Sun Jul 5 23:39:48 2009 UTC vs.
Revision 1.240 by root, Tue Dec 17 16:43:15 2013 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines