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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines