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.61 by root, Fri Jun 6 10:23:50 2008 UTC vs.
Revision 1.238 by root, Tue Dec 10 15:54:51 2013 UTC

1package AnyEvent::Handle;
2
3no warnings;
4use strict;
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.14;
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
38The L<AnyEvent::Intro> tutorial contains some well-documented
39AnyEvent::Handle examples.
40
54In the following, when the documentation refers to of "bytes" then this 41In the following, where the documentation refers to "bytes", it means
55means characters. As sysread and syswrite are used for all I/O, their 42characters. As sysread and syswrite are used for all I/O, their
56treatment 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.
57 47
58All callbacks will be invoked with the handle object as their first 48All callbacks will be invoked with the handle object as their first
59argument. 49argument.
60 50
51=cut
52
53package AnyEvent::Handle;
54
55use Scalar::Util ();
56use List::Util ();
57use Carp ();
58use Errno qw(EAGAIN EINTR);
59
60use AnyEvent (); BEGIN { AnyEvent::common_sense }
61use AnyEvent::Util qw(WSAEWOULDBLOCK);
62
63our $VERSION = $AnyEvent::VERSION;
64
65sub _load_func($) {
66 my $func = $_[0];
67
68 unless (defined &$func) {
69 my $pkg = $func;
70 do {
71 $pkg =~ s/::[^:]+$//
72 or return;
73 eval "require $pkg";
74 } until defined &$func;
75 }
76
77 \&$func
78}
79
80sub MAX_READ_SIZE() { 131072 }
81
61=head1 METHODS 82=head1 METHODS
62 83
63=over 4 84=over 4
64 85
65=item B<new (%args)> 86=item $handle = B<new> AnyEvent::Handle fh => $filehandle, key => value...
66 87
67The constructor supports these arguments (all as key => value pairs). 88The constructor supports these arguments (all as C<< key => value >> pairs).
68 89
69=over 4 90=over 4
70 91
71=item fh => $filehandle [MANDATORY] 92=item fh => $filehandle [C<fh> or C<connect> MANDATORY]
72 93
73The filehandle this L<AnyEvent::Handle> object will operate on. 94The filehandle this L<AnyEvent::Handle> object will operate on.
74
75NOTE: The filehandle will be set to non-blocking (using 95NOTE: The filehandle will be set to non-blocking mode (using
76AnyEvent::Util::fh_nonblocking). 96C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in
97that mode.
77 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
78=item on_eof => $cb->($handle) 116=item on_prepare => $cb->($handle)
79 117
80Set the callback to be called when an end-of-file condition is detcted, 118This (rarely used) callback is called before a new connection is
81i.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
82connection 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).
83 123
84While not mandatory, it is highly recommended to set an eof callback, 124The return value of this callback should be the connect timeout value in
85otherwise you might end up with a closed socket while you are still 125seconds (or C<0>, or C<undef>, or the empty list, to indicate that the
86waiting for data. 126default timeout is to be used).
87 127
128=item on_connect => $cb->($handle, $host, $port, $retry->())
129
130This callback is called when a connection has been successfully established.
131
132The peer's numeric host and port (the socket peername) are passed as
133parameters, together with a retry callback. At the time it is called the
134read and write queues, EOF status, TLS status and similar properties of
135the handle will have been reset.
136
137It is not allowed to use the read or write queues while the handle object
138is connecting.
139
140If, for some reason, the handle is not acceptable, calling C<$retry> will
141continue with the next connection target (in case of multi-homed hosts or
142SRV records there can be multiple connection endpoints). The C<$retry>
143callback can be invoked after the connect callback returns, i.e. one can
144start a handshake and then decide to retry with the next host if the
145handshake fails.
146
147In most cases, you should ignore the C<$retry> parameter.
148
149=item on_connect_error => $cb->($handle, $message)
150
151This callback is called when the connection could not be
152established. C<$!> will contain the relevant error code, and C<$message> a
153message describing it (usually the same as C<"$!">).
154
155If this callback isn't specified, then C<on_error> will be called with a
156fatal error instead.
157
158=back
159
88=item on_error => $cb->($handle, $fatal) 160=item on_error => $cb->($handle, $fatal, $message)
89 161
90This is the error callback, which is called when, well, some error 162This is the error callback, which is called when, well, some error
91occured, such as not being able to resolve the hostname, failure to 163occured, such as not being able to resolve the hostname, failure to
92connect or a read error. 164connect, or a read error.
93 165
94Some 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
95fatal errors the handle object will be shut down and will not be 167fatal errors the handle object will be destroyed (by a call to C<< ->
168destroy >>) after invoking the error callback (which means you are free to
169examine the handle object). Examples of fatal errors are an EOF condition
170with active (but unsatisfiable) read watchers (C<EPIPE>) or I/O errors. In
171cases where the other side can close the connection at will, it is
172often easiest to not report C<EPIPE> errors in this callback.
173
174AnyEvent::Handle tries to find an appropriate error code for you to check
175against, but in some cases (TLS errors), this does not work well.
176
177If you report the error to the user, it is recommended to always output
178the C<$message> argument in human-readable error messages (you don't need
179to report C<"$!"> if you report C<$message>).
180
181If you want to react programmatically to the error, then looking at C<$!>
182and comparing it against some of the documented C<Errno> values is usually
183better than looking at the C<$message>.
184
96usable. Non-fatal errors can be retried by simply returning, but it is 185Non-fatal errors can be retried by returning, but it is recommended
97recommended to simply ignore this parameter and instead abondon the handle 186to simply ignore this parameter and instead abondon the handle object
98object when this callback is invoked. 187when this callback is invoked. Examples of non-fatal errors are timeouts
188C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
99 189
100On callback entrance, the value of C<$!> contains the operating system 190On entry to the callback, the value of C<$!> contains the operating
101error (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>).
102 193
103While 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
104you will not be notified of errors otherwise. The default simply calls 195you will not be notified of errors otherwise. The default just calls
105C<croak>. 196C<croak>.
106 197
107=item on_read => $cb->($handle) 198=item on_read => $cb->($handle)
108 199
109This sets the default read callback, which is called when data arrives 200This sets the default read callback, which is called when data arrives
110and 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
111callback 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
112read buffer). 203read buffer).
113 204
114To 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 >>
115method 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.
116 209
210You can also call C<< ->push_read (...) >> or any other function that
211modifies the read queue. Or do both. Or ...
212
117When an EOF condition is detected then AnyEvent::Handle will first try to 213When an EOF condition is detected, AnyEvent::Handle will first try to
118feed 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
119calling 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
120error will be raised (with C<$!> set to C<EPIPE>). 216error will be raised (with C<$!> set to C<EPIPE>).
121 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
122=item on_drain => $cb->($handle) 239=item on_drain => $cb->($handle)
123 240
124This 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
125(or when the callback is set and the buffer is empty already). 242empty (and immediately when the handle object is created).
126 243
127To append to the write buffer, use the C<< ->push_write >> method. 244To append to the write buffer, use the C<< ->push_write >> method.
128 245
246This callback is useful when you don't want to put all of your write data
247into the queue at once, for example, when you want to write the contents
248of some file to the socket you might not want to read the whole file into
249memory and push it into the queue, but instead only read more data from
250the file when the write queue becomes empty.
251
129=item timeout => $fractional_seconds 252=item timeout => $fractional_seconds
130 253
254=item rtimeout => $fractional_seconds
255
256=item wtimeout => $fractional_seconds
257
131If non-zero, then this enables an "inactivity" timeout: whenever this many 258If non-zero, then these enables an "inactivity" timeout: whenever this
132seconds pass without a successful read or write on the underlying file 259many seconds pass without a successful read or write on the underlying
133handle, 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
134missing, an C<ETIMEDOUT> error will be raised). 261will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>
262error will be raised).
135 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
136Note 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
137any outstanding read or write requests: If you plan to keep the connection 272outstanding read or write requests: If you plan to keep the connection
138idle then you should disable the timout temporarily or ignore the timeout 273idle then you should disable the timeout temporarily or ignore the
139in the C<on_timeout> callback. 274timeout in the corresponding C<on_timeout> callback, in which case
275AnyEvent::Handle will simply restart the timeout.
140 276
141Zero (the default) disables this timeout. 277Zero (the default) disables the corresponding timeout.
142 278
143=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)
144 284
145Called whenever the inactivity timeout passes. If you return from this 285Called whenever the inactivity timeout passes. If you return from this
146callback, 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,
147so this condition is not fatal in any way. 287so this condition is not fatal in any way.
148 288
149=item rbuf_max => <bytes> 289=item rbuf_max => <bytes>
150 290
151If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) 291If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
152when the read buffer ever (strictly) exceeds this size. This is useful to 292when the read buffer ever (strictly) exceeds this size. This is useful to
153avoid denial-of-service attacks. 293avoid some forms of denial-of-service attacks.
154 294
155For example, a server accepting connections from untrusted sources should 295For example, a server accepting connections from untrusted sources should
156be 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
157(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
158amount 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
159isn't finished). 299isn't finished).
160 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
316=item autocork => <boolean>
317
318When disabled (the default), C<push_write> will try to immediately
319write the data to the handle if possible. This avoids having to register
320a write watcher and wait for the next event loop iteration, but can
321be inefficient if you write multiple small chunks (on the wire, this
322disadvantage is usually avoided by your kernel's nagle algorithm, see
323C<no_delay>, but this option can save costly syscalls).
324
325When enabled, writes will always be queued till the next event loop
326iteration. This is efficient when you do many small writes per iteration,
327but less efficient when you do a single write only per iteration (or when
328the write buffer often is full). It also increases write latency.
329
330=item no_delay => <boolean>
331
332When doing small writes on sockets, your operating system kernel might
333wait a bit for more data before actually sending it out. This is called
334the Nagle algorithm, and usually it is beneficial.
335
336In some situations you want as low a delay as possible, which can be
337accomplishd by setting this option to a true value.
338
339The default is your operating system's default behaviour (most likely
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.
373
161=item read_size => <bytes> 374=item read_size => <bytes>
162 375
163The default read block size (the amount of bytes this module will try to read 376The initial read block size, the number of bytes this module will try
164during each (loop iteration). Default: C<8192>. 377to read during each loop iteration. Each handle object will consume
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.
165 388
166=item low_water_mark => <bytes> 389=item low_water_mark => <bytes>
167 390
168Sets 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
169buffer: 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
170considered empty. 393considered empty.
171 394
395Sometimes it can be beneficial (for performance reasons) to add data to
396the write buffer before it is fully drained, but this is a rare case, as
397the operating system kernel usually buffers data as well, so the default
398is good in almost all cases.
399
400=item linger => <seconds>
401
402If this is non-zero (default: C<3600>), the destructor of the
403AnyEvent::Handle object will check whether there is still outstanding
404write data and will install a watcher that will write this data to the
405socket. No errors will be reported (this mostly matches how the operating
406system treats outstanding data at socket close time).
407
408This will not work for partial TLS data that could not be encoded
409yet. This data will be lost. Calling the C<stoptls> method in time might
410help.
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
172=item tls => "accept" | "connect" | Net::SSLeay::SSL object 422=item tls => "accept" | "connect" | Net::SSLeay::SSL object
173 423
174When this parameter is given, it enables TLS (SSL) mode, that means it 424When this parameter is given, it enables TLS (SSL) mode, that means
175will start making tls handshake and will transparently encrypt/decrypt 425AnyEvent will start a TLS handshake as soon as the connection has been
176data. 426established and will transparently encrypt/decrypt data afterwards.
427
428All TLS protocol errors will be signalled as C<EPROTO>, with an
429appropriate error message.
177 430
178TLS mode requires Net::SSLeay to be installed (it will be loaded 431TLS mode requires Net::SSLeay to be installed (it will be loaded
179automatically when you try to create a TLS handle). 432automatically when you try to create a TLS handle): this module doesn't
433have a dependency on that module, so if your module requires it, you have
434to add the dependency yourself. If Net::SSLeay cannot be loaded or is too
435old, you get an C<EPROTO> error.
180 436
181For the TLS server side, use C<accept>, and for the TLS client side of a 437Unlike TCP, TLS has a server and client side: for the TLS server side, use
182connection, use C<connect> mode. 438C<accept>, and for the TLS client side of a connection, use C<connect>
439mode.
183 440
184You can also provide your own TLS connection object, but you have 441You can also provide your own TLS connection object, but you have
185to 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>
186or 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
187AnyEvent::Handle. 444AnyEvent::Handle. Also, this module will take ownership of this connection
445object.
188 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
189See the C<starttls> method if you need to start TLs negotiation later. 456Use the C<< ->starttls >> method if you need to start TLS negotiation later.
190 457
191=item tls_ctx => $ssl_ctx 458=item tls_ctx => $anyevent_tls
192 459
193Use the given Net::SSLeay::CTX object to create the new TLS connection 460Use the given C<AnyEvent::TLS> object to create the new TLS connection
194(unless a connection object was specified directly). If this parameter is 461(unless a connection object was specified directly). If this
195missing, 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>.
196 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
197=item json => JSON or JSON::XS object 501=item json => L<JSON> or L<JSON::XS> object
198 502
199This 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.
200 504
201If 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
202suitable one, which will write and expect UTF-8 encoded JSON texts. 506suitable one (on demand), which will write and expect UTF-8 encoded JSON
507texts.
203 508
204Note 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
205use this functionality, as AnyEvent does not have a dependency itself. 510to use this functionality, as AnyEvent does not have a dependency on it
511itself.
206 512
207=item filter_r => $cb 513=item cbor => L<CBOR::XS> object
208 514
209=item filter_w => $cb 515This is the cbor coder object used by the C<cbor> read and write types.
210 516
211These exist, but are undocumented at this time. 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.
212 524
213=back 525=back
214 526
215=cut 527=cut
216 528
217sub new { 529sub new {
218 my $class = shift; 530 my $class = shift;
219
220 my $self = bless { @_ }, $class; 531 my $self = bless { @_ }, $class;
221 532
222 $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;
223 604
224 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 605 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
225 606
226 if ($self->{tls}) { 607 $self->{_activity} =
227 require Net::SSLeay; 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
228 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}); 624 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
229 } 625 if $self->{tls};
230 626
231 $self->{_activity} = AnyEvent->now;
232 $self->_timeout;
233
234 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; 627 $self->on_drain (delete $self->{on_drain} ) if $self->{on_drain};
235 628
236 $self 629 $self->start_read
237} 630 if $self->{on_read} || @{ $self->{_queue} };
238 631
239sub _shutdown { 632 $self->_drain_wbuf;
240 my ($self) = @_;
241
242 delete $self->{_tw};
243 delete $self->{_rw};
244 delete $self->{_ww};
245 delete $self->{fh};
246
247 $self->stoptls;
248} 633}
249 634
250sub _error { 635sub _error {
251 my ($self, $errno, $fatal) = @_; 636 my ($self, $errno, $fatal, $message) = @_;
252
253 $self->_shutdown
254 if $fatal;
255 637
256 $! = $errno; 638 $! = $errno;
639 $message ||= "$!";
257 640
258 if ($self->{on_error}) { 641 if ($self->{on_error}) {
259 $self->{on_error}($self, $fatal); 642 $self->{on_error}($self, $fatal, $message);
260 } else { 643 $self->destroy if $fatal;
644 } elsif ($self->{fh} || $self->{connect}) {
645 $self->destroy;
261 Carp::croak "AnyEvent::Handle uncaught error: $!"; 646 Carp::croak "AnyEvent::Handle uncaught error: $message";
262 } 647 }
263} 648}
264 649
265=item $fh = $handle->fh 650=item $fh = $handle->fh
266 651
267This method returns the file handle of the L<AnyEvent::Handle> object. 652This method returns the file handle used to create the L<AnyEvent::Handle> object.
268 653
269=cut 654=cut
270 655
271sub fh { $_[0]{fh} } 656sub fh { $_[0]{fh} }
272 657
290 $_[0]{on_eof} = $_[1]; 675 $_[0]{on_eof} = $_[1];
291} 676}
292 677
293=item $handle->on_timeout ($cb) 678=item $handle->on_timeout ($cb)
294 679
295Replace the current C<on_timeout> callback, or disables the callback 680=item $handle->on_rtimeout ($cb)
296(but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor
297argument.
298 681
299=cut 682=item $handle->on_wtimeout ($cb)
300 683
684Replace the current C<on_timeout>, C<on_rtimeout> or C<on_wtimeout>
685callback, or disables the callback (but not the timeout) if C<$cb> =
686C<undef>. See the C<timeout> constructor argument and method.
687
688=cut
689
690# see below
691
692=item $handle->autocork ($boolean)
693
694Enables or disables the current autocork behaviour (see C<autocork>
695constructor argument). Changes will only take effect on the next write.
696
697=cut
698
699sub autocork {
700 $_[0]{autocork} = $_[1];
701}
702
703=item $handle->no_delay ($boolean)
704
705Enables or disables the C<no_delay> setting (see constructor argument of
706the same name for details).
707
708=cut
709
710sub no_delay {
711 $_[0]{no_delay} = $_[1];
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
727 eval {
728 local $SIG{__DIE__};
729 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
730 if $_[0]{fh};
731 };
732}
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
301sub on_timeout { 784sub on_stoptls {
302 $_[0]{on_timeout} = $_[1]; 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];
303} 804}
304 805
305############################################################################# 806#############################################################################
306 807
307=item $handle->timeout ($seconds) 808=item $handle->timeout ($seconds)
308 809
810=item $handle->rtimeout ($seconds)
811
812=item $handle->wtimeout ($seconds)
813
309Configures (or disables) the inactivity timeout. 814Configures (or disables) the inactivity timeout.
310 815
311=cut 816The timeout will be checked instantly, so this method might destroy the
817handle before it returns.
312 818
313sub 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 {
314 my ($self, $timeout) = @_; 843 my ($self, $new_value) = @_;
315 844
845 $new_value >= 0
846 or Carp::croak "AnyEvent::Handle->$timeout called with negative timeout ($new_value), caught";
847
316 $self->{timeout} = $timeout; 848 $self->{$timeout} = $new_value;
317 $self->_timeout; 849 delete $self->{$tw}; &$cb;
318} 850 };
319 851
852 *{"${dir}timeout_reset"} = sub {
853 $_[0]{$activity} = AE::now;
854 };
855
856 # main workhorse:
320# reset the timeout watcher, as neccessary 857 # reset the timeout watcher, as neccessary
321# also check for time-outs 858 # also check for time-outs
322sub _timeout { 859 $cb = sub {
323 my ($self) = @_; 860 my ($self) = @_;
324 861
325 if ($self->{timeout}) { 862 if ($self->{$timeout} && $self->{fh}) {
326 my $NOW = AnyEvent->now; 863 my $NOW = AE::now;
327 864
328 # when would the timeout trigger? 865 # when would the timeout trigger?
329 my $after = $self->{_activity} + $self->{timeout} - $NOW; 866 my $after = $self->{$activity} + $self->{$timeout} - $NOW;
330 867
331 # now or in the past already? 868 # now or in the past already?
332 if ($after <= 0) { 869 if ($after <= 0) {
333 $self->{_activity} = $NOW; 870 $self->{$activity} = $NOW;
334 871
335 if ($self->{on_timeout}) { 872 if ($self->{$on_timeout}) {
336 $self->{on_timeout}($self); 873 $self->{$on_timeout}($self);
337 } else { 874 } else {
338 $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};
339 } 883 }
340 884
341 # callback could have changed timeout value, optimise 885 Scalar::Util::weaken $self;
342 return unless $self->{timeout}; 886 return unless $self; # ->error could have destroyed $self
343 887
344 # calculate new after 888 $self->{$tw} ||= AE::timer $after, 0, sub {
345 $after = $self->{timeout}; 889 delete $self->{$tw};
890 $cb->($self);
891 };
892 } else {
893 delete $self->{$tw};
346 } 894 }
347
348 Scalar::Util::weaken $self;
349 return unless $self; # ->error could have destroyed $self
350
351 $self->{_tw} ||= AnyEvent->timer (after => $after, cb => sub {
352 delete $self->{_tw};
353 $self->_timeout;
354 });
355 } else {
356 delete $self->{_tw};
357 } 895 }
358} 896}
359 897
360############################################################################# 898#############################################################################
361 899
368 906
369The 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
370AnyEvent::Handle will automatically try to get rid of it for you. 908AnyEvent::Handle will automatically try to get rid of it for you.
371 909
372When 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
373water mark, the C<on_drain> callback will be invoked. 911water mark, the C<on_drain> callback will be invoked once.
374 912
375=over 4 913=over 4
376 914
377=item $handle->on_drain ($cb) 915=item $handle->on_drain ($cb)
378 916
379Sets 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
380C<on_drain> in the constructor). 918C<on_drain> in the constructor).
381 919
920This method may invoke callbacks (and therefore the handle might be
921destroyed after it returns).
922
382=cut 923=cut
383 924
384sub on_drain { 925sub on_drain {
385 my ($self, $cb) = @_; 926 my ($self, $cb) = @_;
386 927
387 $self->{on_drain} = $cb; 928 $self->{on_drain} = $cb;
388 929
389 $cb->($self) 930 $cb->($self)
390 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 931 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
391} 932}
392 933
393=item $handle->push_write ($data) 934=item $handle->push_write ($data)
394 935
395Queues 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
396want (only limited by the available memory), as C<AnyEvent::Handle> 937you want (only limited by the available memory and C<wbuf_max>), as
397buffers 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).
398 942
399=cut 943=cut
400 944
401sub _drain_wbuf { 945sub _drain_wbuf {
402 my ($self) = @_; 946 my ($self) = @_;
406 Scalar::Util::weaken $self; 950 Scalar::Util::weaken $self;
407 951
408 my $cb = sub { 952 my $cb = sub {
409 my $len = syswrite $self->{fh}, $self->{wbuf}; 953 my $len = syswrite $self->{fh}, $self->{wbuf};
410 954
411 if ($len >= 0) { 955 if (defined $len) {
412 substr $self->{wbuf}, 0, $len, ""; 956 substr $self->{wbuf}, 0, $len, "";
413 957
414 $self->{_activity} = AnyEvent->now; 958 $self->{_activity} = $self->{_wactivity} = AE::now;
415 959
416 $self->{on_drain}($self) 960 $self->{on_drain}($self)
417 if $self->{low_water_mark} >= length $self->{wbuf} 961 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
418 && $self->{on_drain}; 962 && $self->{on_drain};
419 963
420 delete $self->{_ww} unless length $self->{wbuf}; 964 delete $self->{_ww} unless length $self->{wbuf};
421 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 965 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
422 $self->_error ($!, 1); 966 $self->_error ($!, 1);
423 } 967 }
424 }; 968 };
425 969
426 # try to write data immediately 970 # try to write data immediately
427 $cb->(); 971 $cb->() unless $self->{autocork};
428 972
429 # if still data left in wbuf, we need to poll 973 # if still data left in wbuf, we need to poll
430 $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb) 974 $self->{_ww} = AE::io $self->{fh}, 1, $cb
431 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 }
432 }; 983 };
433} 984}
434 985
435our %WH; 986our %WH;
436 987
988# deprecated
437sub register_write_type($$) { 989sub register_write_type($$) {
438 $WH{$_[0]} = $_[1]; 990 $WH{$_[0]} = $_[1];
439} 991}
440 992
441sub push_write { 993sub push_write {
442 my $self = shift; 994 my $self = shift;
443 995
444 if (@_ > 1) { 996 if (@_ > 1) {
445 my $type = shift; 997 my $type = shift;
446 998
999 @_ = ($WH{$type} ||= _load_func "$type\::anyevent_write_type"
447 @_ = ($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")
448 ->($self, @_); 1001 ->($self, @_);
449 } 1002 }
450 1003
1004 # we downgrade here to avoid hard-to-track-down bugs,
1005 # and diagnose the problem earlier and better.
1006
451 if ($self->{filter_w}) { 1007 if ($self->{tls}) {
452 $self->{filter_w}($self, \$_[0]); 1008 utf8::downgrade $self->{_tls_wbuf} .= $_[0];
1009 &_dotls ($self) if $self->{fh};
453 } else { 1010 } else {
454 $self->{wbuf} .= $_[0]; 1011 utf8::downgrade $self->{wbuf} .= $_[0];
455 $self->_drain_wbuf; 1012 $self->_drain_wbuf if $self->{fh};
456 } 1013 }
457} 1014}
458 1015
459=item $handle->push_write (type => @args) 1016=item $handle->push_write (type => @args)
460 1017
461Instead of formatting your data yourself, you can also let this module do 1018Instead of formatting your data yourself, you can also let this module
462the 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).
463 1023
464Predefined 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
465drop by and tell us): 1025drop by and tell us):
466 1026
467=over 4 1027=over 4
474=cut 1034=cut
475 1035
476register_write_type netstring => sub { 1036register_write_type netstring => sub {
477 my ($self, $string) = @_; 1037 my ($self, $string) = @_;
478 1038
479 sprintf "%d:%s,", (length $string), $string 1039 (length $string) . ":$string,"
480}; 1040};
481 1041
482=item packstring => $format, $data 1042=item packstring => $format, $data
483 1043
484An octet string prefixed with an encoded length. The encoding C<$format> 1044An octet string prefixed with an encoded length. The encoding C<$format>
489=cut 1049=cut
490 1050
491register_write_type packstring => sub { 1051register_write_type packstring => sub {
492 my ($self, $format, $string) = @_; 1052 my ($self, $format, $string) = @_;
493 1053
494 pack "$format/a", $string 1054 pack "$format/a*", $string
495}; 1055};
496 1056
497=item json => $array_or_hashref 1057=item json => $array_or_hashref
498 1058
499Encodes the given hash or array reference into a JSON object. Unless you 1059Encodes the given hash or array reference into a JSON object. Unless you
506 1066
507The generated JSON text is guaranteed not to contain any newlines: While 1067The generated JSON text is guaranteed not to contain any newlines: While
508this 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
509able to read them, many other languages depend on that. 1069able to read them, many other languages depend on that.
510 1070
511A simple RPC protocol that interoperates easily with others is to send 1071A simple RPC protocol that interoperates easily with other languages is
512JSON arrays (or objects, although arrays are usually the better choice as 1072to send JSON arrays (or objects, although arrays are usually the better
513they mimic how function argument passing works) and a newline after each 1073choice as they mimic how function argument passing works) and a newline
514JSON text: 1074after each JSON text:
515 1075
516 $handle->push_write (json => ["method", "arg1", "arg2"]); # whatever 1076 $handle->push_write (json => ["method", "arg1", "arg2"]); # whatever
517 $handle->push_write ("\012"); 1077 $handle->push_write ("\012");
518 1078
519An 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
522 $handle->push_read (json => sub { my $array = $_[1]; ... }); 1082 $handle->push_read (json => sub { my $array = $_[1]; ... });
523 1083
524Other languages could read single lines terminated by a newline and pass 1084Other languages could read single lines terminated by a newline and pass
525this line into their JSON decoder of choice. 1085this line into their JSON decoder of choice.
526 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
527=cut 1107=cut
1108
1109sub json_coder() {
1110 eval { require JSON::XS; JSON::XS->new->utf8 }
1111 || do { require JSON; JSON->new->utf8 }
1112}
528 1113
529register_write_type json => sub { 1114register_write_type json => sub {
530 my ($self, $ref) = @_; 1115 my ($self, $ref) = @_;
531 1116
532 require JSON; 1117 ($self->{json} ||= json_coder)
533 1118 ->encode ($ref)
534 $self->{json} ? $self->{json}->encode ($ref)
535 : JSON::encode_json ($ref)
536}; 1119};
537 1120
1121sub cbor_coder() {
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)
1131};
1132
1133=item storable => $reference
1134
1135Freezes the given reference using L<Storable> and writes it to the
1136handle. Uses the C<nfreeze> format.
1137
1138=cut
1139
1140register_write_type storable => sub {
1141 my ($self, $ref) = @_;
1142
1143 require Storable unless $Storable::VERSION;
1144
1145 pack "w/a*", Storable::nfreeze ($ref)
1146};
1147
538=back 1148=back
539 1149
540=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 1150=item $handle->push_shutdown
541 1151
542This 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
543Whenever 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
544reference with the handle object and the remaining arguments. 1187the handle object and the remaining arguments.
545 1188
546The 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
547be 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.
548 1192
549Note 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
550global, 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 }
551 1209
552=cut 1210=cut
553 1211
554############################################################################# 1212#############################################################################
555 1213
564ways, 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
565a queue. 1223a queue.
566 1224
567In 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
568new 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
569enough is there) from the read buffer (C<< $handle->rbuf >>) if you want 1227enough is there) from the read buffer (C<< $handle->rbuf >>). Or you can
570or not. 1228leave the data there if you want to accumulate more (e.g. when only a
1229partial message has been received so far), or change the read queue with
1230e.g. C<push_read>.
571 1231
572In 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
573case, AnyEvent::Handle will call the first queued callback each time new 1233case, AnyEvent::Handle will call the first queued callback each time new
574data 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
575done its job (see C<push_read>, below). 1235done its job (see C<push_read>, below).
576 1236
577This 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
578a chunk of data, and AnyEvent::Handle will execute them in order. 1238a chunk of data, and AnyEvent::Handle will execute them in order.
579 1239
593 # handle xml 1253 # handle xml
594 }); 1254 });
595 }); 1255 });
596 }); 1256 });
597 1257
598Example 2: Implement a client for a protocol that replies either with 1258Example 2: Implement a client for a protocol that replies either with "OK"
599"OK" and another line or "ERROR" for one request, and 64 bytes for the 1259and another line or "ERROR" for the first request that is sent, and 64
600second request. Due tot he availability of a full queue, we can just 1260bytes for the second request. Due to the availability of a queue, we can
601pipeline sending both requests and manipulate the queue as necessary in 1261just pipeline sending both requests and manipulate the queue as necessary
602the callbacks: 1262in the callbacks.
603 1263
604 # request one 1264When the first callback is called and sees an "OK" response, it will
1265C<unshift> another line-read. This line-read will be queued I<before> the
126664-byte chunk callback.
1267
1268 # request one, returns either "OK + extra line" or "ERROR"
605 $handle->push_write ("request 1\015\012"); 1269 $handle->push_write ("request 1\015\012");
606 1270
607 # we expect "ERROR" or "OK" as response, so push a line read 1271 # we expect "ERROR" or "OK" as response, so push a line read
608 $handle->push_read (line => sub { 1272 $handle->push_read (line => sub {
609 # if we got an "OK", we have to _prepend_ another line, 1273 # if we got an "OK", we have to _prepend_ another line,
616 ... 1280 ...
617 }); 1281 });
618 } 1282 }
619 }); 1283 });
620 1284
621 # request two 1285 # request two, simply returns 64 octets
622 $handle->push_write ("request 2\015\012"); 1286 $handle->push_write ("request 2\015\012");
623 1287
624 # simply read 64 bytes, always 1288 # simply read 64 bytes, always
625 $handle->push_read (chunk => 64, sub { 1289 $handle->push_read (chunk => 64, sub {
626 my $response = $_[1]; 1290 my $response = $_[1];
632=cut 1296=cut
633 1297
634sub _drain_rbuf { 1298sub _drain_rbuf {
635 my ($self) = @_; 1299 my ($self) = @_;
636 1300
1301 # avoid recursion
1302 return if $self->{_skip_drain_rbuf};
637 local $self->{_in_drain} = 1; 1303 local $self->{_skip_drain_rbuf} = 1;
638
639 if (
640 defined $self->{rbuf_max}
641 && $self->{rbuf_max} < length $self->{rbuf}
642 ) {
643 return $self->_error (&Errno::ENOSPC, 1);
644 }
645 1304
646 while () { 1305 while () {
647 no strict 'refs'; 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};
648 1310
649 my $len = length $self->{rbuf}; 1311 my $len = length $self->{rbuf};
650 1312
651 if (my $cb = shift @{ $self->{_queue} }) { 1313 if (my $cb = shift @{ $self->{_queue} }) {
652 unless ($cb->($self)) { 1314 unless ($cb->($self)) {
653 if ($self->{_eof}) { 1315 # no progress can be made
654 # no progress can be made (not enough data and no data forthcoming) 1316 # (not enough data and no data forthcoming)
655 $self->_error (&Errno::EPIPE, 1), last; 1317 $self->_error (Errno::EPIPE, 1), return
656 } 1318 if $self->{_eof};
657 1319
658 unshift @{ $self->{_queue} }, $cb; 1320 unshift @{ $self->{_queue} }, $cb;
659 last; 1321 last;
660 } 1322 }
661 } elsif ($self->{on_read}) { 1323 } elsif ($self->{on_read}) {
668 && !@{ $self->{_queue} } # and the queue is still empty 1330 && !@{ $self->{_queue} } # and the queue is still empty
669 && $self->{on_read} # but we still have on_read 1331 && $self->{on_read} # but we still have on_read
670 ) { 1332 ) {
671 # no further data will arrive 1333 # no further data will arrive
672 # so no progress can be made 1334 # so no progress can be made
673 $self->_error (&Errno::EPIPE, 1), last 1335 $self->_error (Errno::EPIPE, 1), return
674 if $self->{_eof}; 1336 if $self->{_eof};
675 1337
676 last; # more data might arrive 1338 last; # more data might arrive
677 } 1339 }
678 } else { 1340 } else {
679 # read side becomes idle 1341 # read side becomes idle
680 delete $self->{_rw}; 1342 delete $self->{_rw} unless $self->{tls};
681 last; 1343 last;
682 } 1344 }
683 } 1345 }
684 1346
1347 if ($self->{_eof}) {
1348 $self->{on_eof}
685 $self->{on_eof}($self) 1349 ? $self->{on_eof}($self)
686 if $self->{_eof} && $self->{on_eof}; 1350 : $self->_error (0, 1, "Unexpected end-of-file");
1351
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;
1360 }
687 1361
688 # may need to restart read watcher 1362 # may need to restart read watcher
689 unless ($self->{_rw}) { 1363 unless ($self->{_rw}) {
690 $self->start_read 1364 $self->start_read
691 if $self->{on_read} || @{ $self->{_queue} }; 1365 if $self->{on_read} || @{ $self->{_queue} };
696 1370
697This 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
698the 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
699constructor. 1373constructor.
700 1374
1375This method may invoke callbacks (and therefore the handle might be
1376destroyed after it returns).
1377
701=cut 1378=cut
702 1379
703sub on_read { 1380sub on_read {
704 my ($self, $cb) = @_; 1381 my ($self, $cb) = @_;
705 1382
706 $self->{on_read} = $cb; 1383 $self->{on_read} = $cb;
707 $self->_drain_rbuf if $cb && !$self->{_in_drain}; 1384 $self->_drain_rbuf if $cb;
708} 1385}
709 1386
710=item $handle->rbuf 1387=item $handle->rbuf
711 1388
712Returns 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).
713 1392
714You 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)
715you 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.
716 1396
717NOTE: 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>
718C<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
719automatically 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.
720 1401
721=cut 1402=cut
722 1403
723sub rbuf : lvalue { 1404sub rbuf : lvalue {
724 $_[0]{rbuf} 1405 $_[0]{rbuf}
741 1422
742If 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
743interested 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
744true, it will be removed from the queue. 1425true, it will be removed from the queue.
745 1426
1427These methods may invoke callbacks (and therefore the handle might be
1428destroyed after it returns).
1429
746=cut 1430=cut
747 1431
748our %RH; 1432our %RH;
749 1433
750sub register_read_type($$) { 1434sub register_read_type($$) {
756 my $cb = pop; 1440 my $cb = pop;
757 1441
758 if (@_) { 1442 if (@_) {
759 my $type = shift; 1443 my $type = shift;
760 1444
1445 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
761 $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")
762 ->($self, $cb, @_); 1447 ->($self, $cb, @_);
763 } 1448 }
764 1449
765 push @{ $self->{_queue} }, $cb; 1450 push @{ $self->{_queue} }, $cb;
766 $self->_drain_rbuf unless $self->{_in_drain}; 1451 $self->_drain_rbuf;
767} 1452}
768 1453
769sub unshift_read { 1454sub unshift_read {
770 my $self = shift; 1455 my $self = shift;
771 my $cb = pop; 1456 my $cb = pop;
772 1457
773 if (@_) { 1458 if (@_) {
774 my $type = shift; 1459 my $type = shift;
775 1460
1461 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
776 $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")
777 ->($self, $cb, @_); 1463 ->($self, $cb, @_);
778 } 1464 }
779 1465
780
781 unshift @{ $self->{_queue} }, $cb; 1466 unshift @{ $self->{_queue} }, $cb;
782 $self->_drain_rbuf unless $self->{_in_drain}; 1467 $self->_drain_rbuf;
783} 1468}
784 1469
785=item $handle->push_read (type => @args, $cb) 1470=item $handle->push_read (type => @args, $cb)
786 1471
787=item $handle->unshift_read (type => @args, $cb) 1472=item $handle->unshift_read (type => @args, $cb)
788 1473
789Instead 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
790between a number of predefined parsing formats, for chunks of data, lines 1475between a number of predefined parsing formats, for chunks of data, lines
791etc. 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).
792 1479
793Predefined 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
794drop by and tell us): 1481drop by and tell us):
795 1482
796=over 4 1483=over 4
802data. 1489data.
803 1490
804Example: read 2 bytes. 1491Example: read 2 bytes.
805 1492
806 $handle->push_read (chunk => 2, sub { 1493 $handle->push_read (chunk => 2, sub {
807 warn "yay ", unpack "H*", $_[1]; 1494 say "yay " . unpack "H*", $_[1];
808 }); 1495 });
809 1496
810=cut 1497=cut
811 1498
812register_read_type chunk => sub { 1499register_read_type chunk => sub {
817 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, ""); 1504 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, "");
818 1 1505 1
819 } 1506 }
820}; 1507};
821 1508
822# compatibility with older API
823sub push_read_chunk {
824 $_[0]->push_read (chunk => $_[1], $_[2]);
825}
826
827sub unshift_read_chunk {
828 $_[0]->unshift_read (chunk => $_[1], $_[2]);
829}
830
831=item line => [$eol, ]$cb->($handle, $line, $eol) 1509=item line => [$eol, ]$cb->($handle, $line, $eol)
832 1510
833The callback will be called only once a full line (including the end of 1511The callback will be called only once a full line (including the end of
834line marker, C<$eol>) has been read. This line (excluding the end of line 1512line marker, C<$eol>) has been read. This line (excluding the end of line
835marker) will be passed to the callback as second argument (C<$line>), and 1513marker) will be passed to the callback as second argument (C<$line>), and
850=cut 1528=cut
851 1529
852register_read_type line => sub { 1530register_read_type line => sub {
853 my ($self, $cb, $eol) = @_; 1531 my ($self, $cb, $eol) = @_;
854 1532
855 $eol = qr|(\015?\012)| if @_ < 3; 1533 if (@_ < 3) {
1534 # this is faster then the generic code below
1535 sub {
1536 (my $pos = index $_[0]{rbuf}, "\012") >= 0
1537 or return;
1538
1539 (my $str = substr $_[0]{rbuf}, 0, $pos + 1, "") =~ s/(\015?\012)\Z// or die;
1540 $cb->($_[0], $str, "$1");
1541 1
1542 }
1543 } else {
856 $eol = quotemeta $eol unless ref $eol; 1544 $eol = quotemeta $eol unless ref $eol;
857 $eol = qr|^(.*?)($eol)|s; 1545 $eol = qr|^(.*?)($eol)|s;
858 1546
859 sub { 1547 sub {
860 $_[0]{rbuf} =~ s/$eol// or return; 1548 $_[0]{rbuf} =~ s/$eol// or return;
861 1549
862 $cb->($_[0], $1, $2); 1550 $cb->($_[0], "$1", "$2");
1551 1
863 1 1552 }
864 } 1553 }
865}; 1554};
866
867# compatibility with older API
868sub push_read_line {
869 my $self = shift;
870 $self->push_read (line => @_);
871}
872
873sub unshift_read_line {
874 my $self = shift;
875 $self->unshift_read (line => @_);
876}
877 1555
878=item regex => $accept[, $reject[, $skip], $cb->($handle, $data) 1556=item regex => $accept[, $reject[, $skip], $cb->($handle, $data)
879 1557
880Makes a regex match against the regex object C<$accept> and returns 1558Makes a regex match against the regex object C<$accept> and returns
881everything up to and including the match. 1559everything up to and including the match.
899the receive buffer when neither C<$accept> nor C<$reject> match, 1577the receive buffer when neither C<$accept> nor C<$reject> match,
900and everything preceding and including the match will be accepted 1578and everything preceding and including the match will be accepted
901unconditionally. This is useful to skip large amounts of data that you 1579unconditionally. This is useful to skip large amounts of data that you
902know 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
903have to start matching from the beginning. This is purely an optimisation 1581have to start matching from the beginning. This is purely an optimisation
904and 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.
905 1583
906Example: 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
907expect 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
908a 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
909it 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
910required for the accept regex. 1588required for the accept regex.
911 1589
912 $handle->push_read (regex => 1590 $handle->push_read (regex =>
925 1603
926 sub { 1604 sub {
927 # accept 1605 # accept
928 if ($$rbuf =~ $accept) { 1606 if ($$rbuf =~ $accept) {
929 $data .= substr $$rbuf, 0, $+[0], ""; 1607 $data .= substr $$rbuf, 0, $+[0], "";
930 $cb->($self, $data); 1608 $cb->($_[0], $data);
931 return 1; 1609 return 1;
932 } 1610 }
933 1611
934 # reject 1612 # reject
935 if ($reject && $$rbuf =~ $reject) { 1613 if ($reject && $$rbuf =~ $reject) {
936 $self->_error (&Errno::EBADMSG); 1614 $_[0]->_error (Errno::EBADMSG);
937 } 1615 }
938 1616
939 # skip 1617 # skip
940 if ($skip && $$rbuf =~ $skip) { 1618 if ($skip && $$rbuf =~ $skip) {
941 $data .= substr $$rbuf, 0, $+[0], ""; 1619 $data .= substr $$rbuf, 0, $+[0], "";
957 my ($self, $cb) = @_; 1635 my ($self, $cb) = @_;
958 1636
959 sub { 1637 sub {
960 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) { 1638 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) {
961 if ($_[0]{rbuf} =~ /[^0-9]/) { 1639 if ($_[0]{rbuf} =~ /[^0-9]/) {
962 $self->_error (&Errno::EBADMSG); 1640 $_[0]->_error (Errno::EBADMSG);
963 } 1641 }
964 return; 1642 return;
965 } 1643 }
966 1644
967 my $len = $1; 1645 my $len = $1;
968 1646
969 $self->unshift_read (chunk => $len, sub { 1647 $_[0]->unshift_read (chunk => $len, sub {
970 my $string = $_[1]; 1648 my $string = $_[1];
971 $_[0]->unshift_read (chunk => 1, sub { 1649 $_[0]->unshift_read (chunk => 1, sub {
972 if ($_[1] eq ",") { 1650 if ($_[1] eq ",") {
973 $cb->($_[0], $string); 1651 $cb->($_[0], $string);
974 } else { 1652 } else {
975 $self->_error (&Errno::EBADMSG); 1653 $_[0]->_error (Errno::EBADMSG);
976 } 1654 }
977 }); 1655 });
978 }); 1656 });
979 1657
980 1 1658 1
986An octet string prefixed with an encoded length. The encoding C<$format> 1664An octet string prefixed with an encoded length. The encoding C<$format>
987uses the same format as a Perl C<pack> format, but must specify a single 1665uses the same format as a Perl C<pack> format, but must specify a single
988integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an 1666integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
989optional C<!>, C<< < >> or C<< > >> modifier). 1667optional C<!>, C<< < >> or C<< > >> modifier).
990 1668
991DNS over TCP uses a prefix of C<n>, EPP uses a prefix of C<N>. 1669For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
1670EPP uses a prefix of C<N> (4 octtes).
992 1671
993Example: read a block of data prefixed by its length in BER-encoded 1672Example: read a block of data prefixed by its length in BER-encoded
994format (very efficient). 1673format (very efficient).
995 1674
996 $handle->push_read (packstring => "w", sub { 1675 $handle->push_read (packstring => "w", sub {
1002register_read_type packstring => sub { 1681register_read_type packstring => sub {
1003 my ($self, $cb, $format) = @_; 1682 my ($self, $cb, $format) = @_;
1004 1683
1005 sub { 1684 sub {
1006 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method 1685 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1007 defined (my $len = eval { unpack $format, $_[0]->{rbuf} }) 1686 defined (my $len = eval { unpack $format, $_[0]{rbuf} })
1008 or return; 1687 or return;
1009 1688
1689 $format = length pack $format, $len;
1690
1691 # bypass unshift if we already have the remaining chunk
1692 if ($format + $len <= length $_[0]{rbuf}) {
1693 my $data = substr $_[0]{rbuf}, $format, $len;
1694 substr $_[0]{rbuf}, 0, $format + $len, "";
1695 $cb->($_[0], $data);
1696 } else {
1010 # remove prefix 1697 # remove prefix
1011 substr $_[0]->{rbuf}, 0, (length pack $format, $len), ""; 1698 substr $_[0]{rbuf}, 0, $format, "";
1012 1699
1013 # read rest 1700 # read remaining chunk
1014 $_[0]->unshift_read (chunk => $len, $cb); 1701 $_[0]->unshift_read (chunk => $len, $cb);
1702 }
1015 1703
1016 1 1704 1
1017 } 1705 }
1018}; 1706};
1019 1707
1020=item json => $cb->($handle, $hash_or_arrayref) 1708=item json => $cb->($handle, $hash_or_arrayref)
1021 1709
1022Reads 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.
1023 1712
1024If 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
1025for 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.
1026 1715
1027This read type uses the incremental parser available with JSON version 1716This read type uses the incremental parser available with JSON version
1034the C<json> write type description, above, for an actual example. 1723the C<json> write type description, above, for an actual example.
1035 1724
1036=cut 1725=cut
1037 1726
1038register_read_type json => sub { 1727register_read_type json => sub {
1039 my ($self, $cb, $accept, $reject, $skip) = @_; 1728 my ($self, $cb) = @_;
1040 1729
1041 require JSON; 1730 my $json = $self->{json} ||= json_coder;
1042 1731
1043 my $data; 1732 my $data;
1044 my $rbuf = \$self->{rbuf};
1045
1046 my $json = $self->{json} ||= JSON->new->utf8;
1047 1733
1048 sub { 1734 sub {
1049 my $ref = $json->incr_parse ($self->{rbuf}); 1735 my $ref = eval { $json->incr_parse ($_[0]{rbuf}) };
1050 1736
1051 if ($ref) { 1737 if ($ref) {
1052 $self->{rbuf} = $json->incr_text; 1738 $_[0]{rbuf} = $json->incr_text;
1053 $json->incr_text = ""; 1739 $json->incr_text = "";
1054 $cb->($self, $ref); 1740 $cb->($_[0], $ref);
1055 1741
1056 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 ()
1057 } else { 1753 } else {
1058 $self->{rbuf} = ""; 1754 $_[0]{rbuf} = "";
1755
1059 () 1756 ()
1060 } 1757 }
1061 } 1758 }
1062}; 1759};
1063 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 {
1802 ()
1803 }
1804 }
1805};
1806
1807=item storable => $cb->($handle, $ref)
1808
1809Deserialises a L<Storable> frozen representation as written by the
1810C<storable> write type (BER-encoded length prefix followed by nfreeze'd
1811data).
1812
1813Raises C<EBADMSG> error if the data could not be decoded.
1814
1815=cut
1816
1817register_read_type storable => sub {
1818 my ($self, $cb) = @_;
1819
1820 require Storable unless $Storable::VERSION;
1821
1822 sub {
1823 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1824 defined (my $len = eval { unpack "w", $_[0]{rbuf} })
1825 or return;
1826
1827 my $format = length pack "w", $len;
1828
1829 # bypass unshift if we already have the remaining chunk
1830 if ($format + $len <= length $_[0]{rbuf}) {
1831 my $data = substr $_[0]{rbuf}, $format, $len;
1832 substr $_[0]{rbuf}, 0, $format + $len, "";
1833
1834 eval { $cb->($_[0], Storable::thaw ($data)); 1 }
1835 or return $_[0]->_error (Errno::EBADMSG);
1836 } else {
1837 # remove prefix
1838 substr $_[0]{rbuf}, 0, $format, "";
1839
1840 # read remaining chunk
1841 $_[0]->unshift_read (chunk => $len, sub {
1842 eval { $cb->($_[0], Storable::thaw ($_[1])); 1 }
1843 or $_[0]->_error (Errno::EBADMSG);
1844 });
1845 }
1846
1847 1
1848 }
1849};
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
1064=back 1937=back
1065 1938
1066=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args) 1939=item custom read types - Package::anyevent_read_type $handle, $cb, @args
1067 1940
1068This 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).
1069 1946
1070Whenever 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
1071reference with the handle object, the callback and the remaining 1948handle object, the original callback and the remaining arguments.
1072arguments.
1073 1949
1074The code reference is supposed to return a callback (usually a closure) 1950The function is supposed to return a callback (usually a closure) that
1075that 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.
1076 1954
1077It should invoke the passed callback when it is done reading (remember to 1955It should invoke the original callback when it is done reading (remember
1078pass 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).
1079 1958
1080Note that this is a function, and all types registered this way will be
1081global, so try to use unique names.
1082
1083For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>, 1959For examples, see the source of this module (F<perldoc -m
1084search for C<register_read_type>)). 1960AnyEvent::Handle>, search for C<register_read_type>)).
1085 1961
1086=item $handle->stop_read 1962=item $handle->stop_read
1087 1963
1088=item $handle->start_read 1964=item $handle->start_read
1089 1965
1095Note that AnyEvent::Handle will automatically C<start_read> for you when 1971Note that AnyEvent::Handle will automatically C<start_read> for you when
1096you 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
1097will 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
1098there are any read requests in the queue. 1974there are any read requests in the queue.
1099 1975
1976In older versions of this module (<= 5.3), these methods had no effect,
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.
1987
1100=cut 1988=cut
1101 1989
1102sub stop_read { 1990sub stop_read {
1103 my ($self) = @_; 1991 my ($self) = @_;
1104 1992
1106} 1994}
1107 1995
1108sub start_read { 1996sub start_read {
1109 my ($self) = @_; 1997 my ($self) = @_;
1110 1998
1111 unless ($self->{_rw} || $self->{_eof}) { 1999 unless ($self->{_rw} || $self->{_eof} || !$self->{fh}) {
1112 Scalar::Util::weaken $self; 2000 Scalar::Util::weaken $self;
1113 2001
1114 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 2002 $self->{_rw} = AE::io $self->{fh}, 0, sub {
1115 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 2003 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1116 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 2004 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size}, length $$rbuf;
1117 2005
1118 if ($len > 0) { 2006 if ($len > 0) {
1119 $self->{_activity} = AnyEvent->now; 2007 $self->{_activity} = $self->{_ractivity} = AE::now;
1120 2008
1121 $self->{filter_r} 2009 if ($self->{tls}) {
1122 ? $self->{filter_r}($self, $rbuf) 2010 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1123 : $self->{_in_drain} || $self->_drain_rbuf; 2011
2012 &_dotls ($self);
2013 } else {
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);
2021 }
1124 2022
1125 } elsif (defined $len) { 2023 } elsif (defined $len) {
1126 delete $self->{_rw}; 2024 delete $self->{_rw};
1127 $self->{_eof} = 1; 2025 $self->{_eof} = 1;
1128 $self->_drain_rbuf unless $self->{_in_drain}; 2026 $self->_drain_rbuf;
1129 2027
1130 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 2028 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
1131 return $self->_error ($!, 1); 2029 return $self->_error ($!, 1);
1132 } 2030 }
1133 }); 2031 };
1134 } 2032 }
1135} 2033}
1136 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);
2055 }
2056}
2057
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.
1137sub _dotls { 2063sub _dotls {
1138 my ($self) = @_; 2064 my ($self) = @_;
1139 2065
1140 my $buf; 2066 my $tmp;
1141 2067
1142 if (length $self->{_tls_wbuf}) { 2068 if (length $self->{_tls_wbuf}) {
1143 while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { 2069 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
1144 substr $self->{_tls_wbuf}, 0, $len, ""; 2070 substr $self->{_tls_wbuf}, 0, $tmp, "";
1145 } 2071 }
1146 }
1147 2072
2073 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
2074 return $self->_tls_error ($tmp)
2075 if $tmp != $ERROR_WANT_READ
2076 && ($tmp != $ERROR_SYSCALL || $!);
2077 }
2078
2079 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
2080 unless (length $tmp) {
2081 $self->{_on_starttls}
2082 and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
2083 &_freetls;
2084
2085 if ($self->{on_stoptls}) {
2086 $self->{on_stoptls}($self);
2087 return;
2088 } else {
2089 # let's treat SSL-eof as we treat normal EOF
2090 delete $self->{_rw};
2091 $self->{_eof} = 1;
2092 }
2093 }
2094
2095 $self->{_tls_rbuf} .= $tmp;
2096 $self->_drain_rbuf;
2097 $self->{tls} or return; # tls session might have gone away in callback
2098 }
2099
2100 $tmp = Net::SSLeay::get_error ($self->{tls}, -1);
2101 return $self->_tls_error ($tmp)
2102 if $tmp != $ERROR_WANT_READ
2103 && ($tmp != $ERROR_SYSCALL || $!);
2104
1148 if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { 2105 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1149 $self->{wbuf} .= $buf; 2106 $self->{wbuf} .= $tmp;
1150 $self->_drain_wbuf; 2107 $self->_drain_wbuf;
2108 $self->{tls} or return; # tls session might have gone away in callback
1151 } 2109 }
1152 2110
1153 while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { 2111 $self->{_on_starttls}
1154 if (length $buf) { 2112 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1155 $self->{rbuf} .= $buf; 2113 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
1156 $self->_drain_rbuf unless $self->{_in_drain};
1157 } else {
1158 # let's treat SSL-eof as we treat normal EOF
1159 $self->{_eof} = 1;
1160 $self->_shutdown;
1161 return;
1162 }
1163 }
1164
1165 my $err = Net::SSLeay::get_error ($self->{tls}, -1);
1166
1167 if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
1168 if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
1169 return $self->_error ($!, 1);
1170 } elsif ($err == Net::SSLeay::ERROR_SSL ()) {
1171 return $self->_error (&Errno::EIO, 1);
1172 }
1173
1174 # all others are fine for our purposes
1175 }
1176} 2114}
1177 2115
1178=item $handle->starttls ($tls[, $tls_ctx]) 2116=item $handle->starttls ($tls[, $tls_ctx])
1179 2117
1180Instead of starting TLS negotiation immediately when the AnyEvent::Handle 2118Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1181object is created, you can also do that at a later time by calling 2119object is created, you can also do that at a later time by calling
1182C<starttls>. 2120C<starttls>. See the C<tls> constructor argument for general info.
2121
2122Starting TLS is currently an asynchronous operation - when you push some
2123write data and then call C<< ->starttls >> then TLS negotiation will start
2124immediately, after which the queued write data is then sent. This might
2125change in future versions, so best make sure you have no outstanding write
2126data when calling this method.
1183 2127
1184The first argument is the same as the C<tls> constructor argument (either 2128The first argument is the same as the C<tls> constructor argument (either
1185C<"connect">, C<"accept"> or an existing Net::SSLeay object). 2129C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1186 2130
1187The second argument is the optional C<Net::SSLeay::CTX> object that is 2131The second argument is the optional C<AnyEvent::TLS> object that is used
1188used when AnyEvent::Handle has to create its own TLS connection object. 2132when AnyEvent::Handle has to create its own TLS connection object, or
2133a hash reference with C<< key => value >> pairs that will be used to
2134construct a new context.
1189 2135
1190The TLS connection object will end up in C<< $handle->{tls} >> after this 2136The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1191call and can be used or changed to your liking. Note that the handshake 2137context in C<< $handle->{tls_ctx} >> after this call and can be used or
1192might have already started when this function returns. 2138changed to your liking. Note that the handshake might have already started
2139when this function returns.
1193 2140
2141Due to bugs in OpenSSL, it might or might not be possible to do multiple
2142handshakes on the same stream. It is best to not attempt to use the
2143stream after stopping TLS.
2144
2145This method may invoke callbacks (and therefore the handle might be
2146destroyed after it returns).
2147
1194=cut 2148=cut
2149
2150our %TLS_CACHE; #TODO not yet documented, should we?
1195 2151
1196sub starttls { 2152sub starttls {
1197 my ($self, $ssl, $ctx) = @_; 2153 my ($self, $tls, $ctx) = @_;
1198 2154
1199 $self->stoptls; 2155 Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught"
2156 if $self->{tls};
1200 2157
1201 if ($ssl eq "accept") { 2158 unless (defined $AnyEvent::TLS::VERSION) {
1202 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 2159 eval {
1203 Net::SSLeay::set_accept_state ($ssl); 2160 require Net::SSLeay;
1204 } elsif ($ssl eq "connect") { 2161 require AnyEvent::TLS;
1205 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 2162 1
1206 Net::SSLeay::set_connect_state ($ssl); 2163 } or return $self->_error (Errno::EPROTO, 1, "TLS support not available on this system");
2164 }
2165
2166 $self->{tls} = $tls;
2167 $self->{tls_ctx} = $ctx if @_ > 2;
2168
2169 return unless $self->{fh};
2170
2171 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
2172 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
2173
2174 $tls = delete $self->{tls};
2175 $ctx = $self->{tls_ctx};
2176
2177 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
2178
2179 if ("HASH" eq ref $ctx) {
2180 if ($ctx->{cache}) {
2181 my $key = $ctx+0;
2182 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
2183 } else {
2184 $ctx = new AnyEvent::TLS %$ctx;
2185 }
2186 }
1207 } 2187
1208 2188 $self->{tls_ctx} = $ctx || TLS_CTX ();
1209 $self->{tls} = $ssl; 2189 $self->{tls} = $tls = $self->{tls_ctx}->_get_session ($tls, $self, $self->{peername});
1210 2190
1211 # basically, this is deep magic (because SSL_read should have the same issues) 2191 # basically, this is deep magic (because SSL_read should have the same issues)
1212 # but the openssl maintainers basically said: "trust us, it just works". 2192 # but the openssl maintainers basically said: "trust us, it just works".
1213 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 2193 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
1214 # and mismaintained ssleay-module doesn't even offer them). 2194 # and mismaintained ssleay-module doesn't even offer them).
1215 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html 2195 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
2196 #
2197 # in short: this is a mess.
2198 #
2199 # note that we do not try to keep the length constant between writes as we are required to do.
2200 # we assume that most (but not all) of this insanity only applies to non-blocking cases,
2201 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
2202 # have identity issues in that area.
1216 Net::SSLeay::CTX_set_mode ($self->{tls}, 2203# Net::SSLeay::CTX_set_mode ($ssl,
1217 (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 2204# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1218 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 2205# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
2206 Net::SSLeay::CTX_set_mode ($tls, 1|2);
1219 2207
1220 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 2208 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1221 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 2209 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1222 2210
2211 Net::SSLeay::BIO_write ($self->{_rbio}, $self->{rbuf});
2212 $self->{rbuf} = "";
2213
1223 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); 2214 Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});
1224 2215
1225 $self->{filter_w} = sub { 2216 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
1226 $_[0]{_tls_wbuf} .= ${$_[1]}; 2217 if $self->{on_starttls};
1227 &_dotls; 2218
1228 }; 2219 &_dotls; # need to trigger the initial handshake
1229 $self->{filter_r} = sub { 2220 $self->start_read; # make sure we actually do read
1230 Net::SSLeay::BIO_write ($_[0]{_rbio}, ${$_[1]});
1231 &_dotls;
1232 };
1233} 2221}
1234 2222
1235=item $handle->stoptls 2223=item $handle->stoptls
1236 2224
1237Destroys the SSL connection, if any. Partial read or write data will be 2225Shuts down the SSL connection - this makes a proper EOF handshake by
1238lost. 2226sending a close notify to the other side, but since OpenSSL doesn't
2227support non-blocking shut downs, it is not guaranteed that you can re-use
2228the stream afterwards.
2229
2230This method may invoke callbacks (and therefore the handle might be
2231destroyed after it returns).
1239 2232
1240=cut 2233=cut
1241 2234
1242sub stoptls { 2235sub stoptls {
1243 my ($self) = @_; 2236 my ($self) = @_;
1244 2237
1245 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 2238 if ($self->{tls} && $self->{fh}) {
2239 Net::SSLeay::shutdown ($self->{tls});
1246 2240
1247 delete $self->{_rbio}; 2241 &_dotls;
1248 delete $self->{_wbio}; 2242
1249 delete $self->{_tls_wbuf}; 2243# # we don't give a shit. no, we do, but we can't. no...#d#
1250 delete $self->{filter_r}; 2244# # we, we... have to use openssl :/#d#
1251 delete $self->{filter_w}; 2245# &_freetls;#d#
2246 }
1252} 2247}
2248
2249sub _freetls {
2250 my ($self) = @_;
2251
2252 return unless $self->{tls};
2253
2254 $self->{tls_ctx}->_put_session (delete $self->{tls})
2255 if $self->{tls} > 0;
2256
2257 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
2258}
2259
2260=item $handle->resettls
2261
2262This rarely-used method simply resets and TLS state on the handle, usually
2263causing data loss.
2264
2265One case where it may be useful is when you want to skip over the data in
2266the stream but you are not interested in interpreting it, so data loss is
2267no concern.
2268
2269=cut
2270
2271*resettls = \&_freetls;
1253 2272
1254sub DESTROY { 2273sub DESTROY {
1255 my $self = shift; 2274 my ($self) = @_;
1256 2275
1257 $self->stoptls; 2276 &_freetls;
2277
2278 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
2279
2280 if ($linger && length $self->{wbuf} && $self->{fh}) {
2281 my $fh = delete $self->{fh};
2282 my $wbuf = delete $self->{wbuf};
2283
2284 my @linger;
2285
2286 push @linger, AE::io $fh, 1, sub {
2287 my $len = syswrite $fh, $wbuf, length $wbuf;
2288
2289 if ($len > 0) {
2290 substr $wbuf, 0, $len, "";
2291 } elsif (defined $len || ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK)) {
2292 @linger = (); # end
2293 }
2294 };
2295 push @linger, AE::timer $linger, 0, sub {
2296 @linger = ();
2297 };
2298 }
1258} 2299}
2300
2301=item $handle->destroy
2302
2303Shuts down the handle object as much as possible - this call ensures that
2304no further callbacks will be invoked and as many resources as possible
2305will be freed. Any method you will call on the handle object after
2306destroying it in this way will be silently ignored (and it will return the
2307empty list).
2308
2309Normally, you can just "forget" any references to an AnyEvent::Handle
2310object and it will simply shut down. This works in fatal error and EOF
2311callbacks, as well as code outside. It does I<NOT> work in a read or write
2312callback, so when you want to destroy the AnyEvent::Handle object from
2313within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
2314that case.
2315
2316Destroying the handle object in this way has the advantage that callbacks
2317will be removed as well, so if those are the only reference holders (as
2318is common), then one doesn't need to do anything special to break any
2319reference cycles.
2320
2321The handle might still linger in the background and write out remaining
2322data, as specified by the C<linger> option, however.
2323
2324=cut
2325
2326sub destroy {
2327 my ($self) = @_;
2328
2329 $self->DESTROY;
2330 %$self = ();
2331 bless $self, "AnyEvent::Handle::destroyed";
2332}
2333
2334sub AnyEvent::Handle::destroyed::AUTOLOAD {
2335 #nop
2336}
2337
2338=item $handle->destroyed
2339
2340Returns false as long as the handle hasn't been destroyed by a call to C<<
2341->destroy >>, true otherwise.
2342
2343Can be useful to decide whether the handle is still valid after some
2344callback possibly destroyed the handle. For example, C<< ->push_write >>,
2345C<< ->starttls >> and other methods can call user callbacks, which in turn
2346can destroy the handle, so work can be avoided by checking sometimes:
2347
2348 $hdl->starttls ("accept");
2349 return if $hdl->destroyed;
2350 $hdl->push_write (...
2351
2352Note that the call to C<push_write> will silently be ignored if the handle
2353has been destroyed, so often you can just ignore the possibility of the
2354handle being destroyed.
2355
2356=cut
2357
2358sub destroyed { 0 }
2359sub AnyEvent::Handle::destroyed::destroyed { 1 }
1259 2360
1260=item AnyEvent::Handle::TLS_CTX 2361=item AnyEvent::Handle::TLS_CTX
1261 2362
1262This function creates and returns the Net::SSLeay::CTX object used by 2363This function creates and returns the AnyEvent::TLS object used by default
1263default for TLS mode. 2364for TLS mode.
1264 2365
1265The context is created like this: 2366The context is created by calling L<AnyEvent::TLS> without any arguments.
1266
1267 Net::SSLeay::load_error_strings;
1268 Net::SSLeay::SSLeay_add_ssl_algorithms;
1269 Net::SSLeay::randomize;
1270
1271 my $CTX = Net::SSLeay::CTX_new;
1272
1273 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL
1274 2367
1275=cut 2368=cut
1276 2369
1277our $TLS_CTX; 2370our $TLS_CTX;
1278 2371
1279sub TLS_CTX() { 2372sub TLS_CTX() {
1280 $TLS_CTX || do { 2373 $TLS_CTX ||= do {
1281 require Net::SSLeay; 2374 require AnyEvent::TLS;
1282 2375
1283 Net::SSLeay::load_error_strings (); 2376 new AnyEvent::TLS
1284 Net::SSLeay::SSLeay_add_ssl_algorithms (); 2377 }
1285 Net::SSLeay::randomize (); 2378}
1286 2379
1287 $TLS_CTX = Net::SSLeay::CTX_new (); 2380=back
1288 2381
1289 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ());
1290 2382
1291 $TLS_CTX 2383=head1 NONFREQUENTLY ASKED QUESTIONS
2384
2385=over 4
2386
2387=item I C<undef> the AnyEvent::Handle reference inside my callback and
2388still get further invocations!
2389
2390That's because AnyEvent::Handle keeps a reference to itself when handling
2391read or write callbacks.
2392
2393It is only safe to "forget" the reference inside EOF or error callbacks,
2394from within all other callbacks, you need to explicitly call the C<<
2395->destroy >> method.
2396
2397=item Why is my C<on_eof> callback never called?
2398
2399Probably because your C<on_error> callback is being called instead: When
2400you have outstanding requests in your read queue, then an EOF is
2401considered an error as you clearly expected some data.
2402
2403To avoid this, make sure you have an empty read queue whenever your handle
2404is supposed to be "idle" (i.e. connection closes are O.K.). You can set
2405an C<on_read> handler that simply pushes the first read requests in the
2406queue.
2407
2408See also the next question, which explains this in a bit more detail.
2409
2410=item How can I serve requests in a loop?
2411
2412Most protocols consist of some setup phase (authentication for example)
2413followed by a request handling phase, where the server waits for requests
2414and handles them, in a loop.
2415
2416There are two important variants: The first (traditional, better) variant
2417handles requests until the server gets some QUIT command, causing it to
2418close the connection first (highly desirable for a busy TCP server). A
2419client dropping the connection is an error, which means this variant can
2420detect an unexpected detection close.
2421
2422To handle this case, always make sure you have a non-empty read queue, by
2423pushing the "read request start" handler on it:
2424
2425 # we assume a request starts with a single line
2426 my @start_request; @start_request = (line => sub {
2427 my ($hdl, $line) = @_;
2428
2429 ... handle request
2430
2431 # push next request read, possibly from a nested callback
2432 $hdl->push_read (@start_request);
2433 });
2434
2435 # auth done, now go into request handling loop
2436 # now push the first @start_request
2437 $hdl->push_read (@start_request);
2438
2439By always having an outstanding C<push_read>, the handle always expects
2440some data and raises the C<EPIPE> error when the connction is dropped
2441unexpectedly.
2442
2443The second variant is a protocol where the client can drop the connection
2444at any time. For TCP, this means that the server machine may run out of
2445sockets easier, and in general, it means you cannot distinguish a protocl
2446failure/client crash from a normal connection close. Nevertheless, these
2447kinds of protocols are common (and sometimes even the best solution to the
2448problem).
2449
2450Having an outstanding read request at all times is possible if you ignore
2451C<EPIPE> errors, but this doesn't help with when the client drops the
2452connection during a request, which would still be an error.
2453
2454A better solution is to push the initial request read in an C<on_read>
2455callback. This avoids an error, as when the server doesn't expect data
2456(i.e. is idly waiting for the next request, an EOF will not raise an
2457error, but simply result in an C<on_eof> callback. It is also a bit slower
2458and simpler:
2459
2460 # auth done, now go into request handling loop
2461 $hdl->on_read (sub {
2462 my ($hdl) = @_;
2463
2464 # called each time we receive data but the read queue is empty
2465 # simply start read the request
2466
2467 $hdl->push_read (line => sub {
2468 my ($hdl, $line) = @_;
2469
2470 ... handle request
2471
2472 # do nothing special when the request has been handled, just
2473 # let the request queue go empty.
2474 });
2475 });
2476
2477=item I get different callback invocations in TLS mode/Why can't I pause
2478reading?
2479
2480Unlike, say, TCP, TLS connections do not consist of two independent
2481communication channels, one for each direction. Or put differently, the
2482read and write directions are not independent of each other: you cannot
2483write data unless you are also prepared to read, and vice versa.
2484
2485This means that, in TLS mode, you might get C<on_error> or C<on_eof>
2486callback invocations when you are not expecting any read data - the reason
2487is that AnyEvent::Handle always reads in TLS mode.
2488
2489During the connection, you have to make sure that you always have a
2490non-empty read-queue, or an C<on_read> watcher. At the end of the
2491connection (or when you no longer want to use it) you can call the
2492C<destroy> method.
2493
2494=item How do I read data until the other side closes the connection?
2495
2496If you just want to read your data into a perl scalar, the easiest way
2497to achieve this is by setting an C<on_read> callback that does nothing,
2498clearing the C<on_eof> callback and in the C<on_error> callback, the data
2499will be in C<$_[0]{rbuf}>:
2500
2501 $handle->on_read (sub { });
2502 $handle->on_eof (undef);
2503 $handle->on_error (sub {
2504 my $data = delete $_[0]{rbuf};
2505 });
2506
2507Note that this example removes the C<rbuf> member from the handle object,
2508which is not normally allowed by the API. It is expressly permitted in
2509this case only, as the handle object needs to be destroyed afterwards.
2510
2511The reason to use C<on_error> is that TCP connections, due to latencies
2512and packets loss, might get closed quite violently with an error, when in
2513fact all data has been received.
2514
2515It is usually better to use acknowledgements when transferring data,
2516to make sure the other side hasn't just died and you got the data
2517intact. This is also one reason why so many internet protocols have an
2518explicit QUIT command.
2519
2520=item I don't want to destroy the handle too early - how do I wait until
2521all data has been written?
2522
2523After writing your last bits of data, set the C<on_drain> callback
2524and destroy the handle in there - with the default setting of
2525C<low_water_mark> this will be called precisely when all data has been
2526written to the socket:
2527
2528 $handle->push_write (...);
2529 $handle->on_drain (sub {
2530 AE::log debug => "All data submitted to the kernel.";
2531 undef $handle;
2532 });
2533
2534If you just want to queue some data and then signal EOF to the other side,
2535consider using C<< ->push_shutdown >> instead.
2536
2537=item I want to contact a TLS/SSL server, I don't care about security.
2538
2539If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
2540connect to it and then create the AnyEvent::Handle with the C<tls>
2541parameter:
2542
2543 tcp_connect $host, $port, sub {
2544 my ($fh) = @_;
2545
2546 my $handle = new AnyEvent::Handle
2547 fh => $fh,
2548 tls => "connect",
2549 on_error => sub { ... };
2550
2551 $handle->push_write (...);
1292 } 2552 };
1293} 2553
2554=item I want to contact a TLS/SSL server, I do care about security.
2555
2556Then you should additionally enable certificate verification, including
2557peername verification, if the protocol you use supports it (see
2558L<AnyEvent::TLS>, C<verify_peername>).
2559
2560E.g. for HTTPS:
2561
2562 tcp_connect $host, $port, sub {
2563 my ($fh) = @_;
2564
2565 my $handle = new AnyEvent::Handle
2566 fh => $fh,
2567 peername => $host,
2568 tls => "connect",
2569 tls_ctx => { verify => 1, verify_peername => "https" },
2570 ...
2571
2572Note that you must specify the hostname you connected to (or whatever
2573"peername" the protocol needs) as the C<peername> argument, otherwise no
2574peername verification will be done.
2575
2576The above will use the system-dependent default set of trusted CA
2577certificates. If you want to check against a specific CA, add the
2578C<ca_file> (or C<ca_cert>) arguments to C<tls_ctx>:
2579
2580 tls_ctx => {
2581 verify => 1,
2582 verify_peername => "https",
2583 ca_file => "my-ca-cert.pem",
2584 },
2585
2586=item I want to create a TLS/SSL server, how do I do that?
2587
2588Well, you first need to get a server certificate and key. You have
2589three options: a) ask a CA (buy one, use cacert.org etc.) b) create a
2590self-signed certificate (cheap. check the search engine of your choice,
2591there are many tutorials on the net) or c) make your own CA (tinyca2 is a
2592nice program for that purpose).
2593
2594Then create a file with your private key (in PEM format, see
2595L<AnyEvent::TLS>), followed by the certificate (also in PEM format). The
2596file should then look like this:
2597
2598 -----BEGIN RSA PRIVATE KEY-----
2599 ...header data
2600 ... lots of base64'y-stuff
2601 -----END RSA PRIVATE KEY-----
2602
2603 -----BEGIN CERTIFICATE-----
2604 ... lots of base64'y-stuff
2605 -----END CERTIFICATE-----
2606
2607The important bits are the "PRIVATE KEY" and "CERTIFICATE" parts. Then
2608specify this file as C<cert_file>:
2609
2610 tcp_server undef, $port, sub {
2611 my ($fh) = @_;
2612
2613 my $handle = new AnyEvent::Handle
2614 fh => $fh,
2615 tls => "accept",
2616 tls_ctx => { cert_file => "my-server-keycert.pem" },
2617 ...
2618
2619When you have intermediate CA certificates that your clients might not
2620know about, just append them to the C<cert_file>.
1294 2621
1295=back 2622=back
1296 2623
1297=head1 SUBCLASSING AnyEvent::Handle 2624=head1 SUBCLASSING AnyEvent::Handle
1298 2625
1304=over 4 2631=over 4
1305 2632
1306=item * all constructor arguments become object members. 2633=item * all constructor arguments become object members.
1307 2634
1308At least initially, when you pass a C<tls>-argument to the constructor it 2635At least initially, when you pass a C<tls>-argument to the constructor it
1309will end up in C<< $handle->{tls} >>. Those members might be changes or 2636will end up in C<< $handle->{tls} >>. Those members might be changed or
1310mutated later on (for example C<tls> will hold the TLS connection object). 2637mutated later on (for example C<tls> will hold the TLS connection object).
1311 2638
1312=item * other object member names are prefixed with an C<_>. 2639=item * other object member names are prefixed with an C<_>.
1313 2640
1314All object members not explicitly documented (internal use) are prefixed 2641All object members not explicitly documented (internal use) are prefixed
1317 2644
1318=item * all members not documented here and not prefixed with an underscore 2645=item * all members not documented here and not prefixed with an underscore
1319are free to use in subclasses. 2646are free to use in subclasses.
1320 2647
1321Of course, new versions of AnyEvent::Handle may introduce more "public" 2648Of course, new versions of AnyEvent::Handle may introduce more "public"
1322member variables, but thats just life, at least it is documented. 2649member variables, but that's just life. At least it is documented.
1323 2650
1324=back 2651=back
1325 2652
1326=head1 AUTHOR 2653=head1 AUTHOR
1327 2654
1328Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>. 2655Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>.
1329 2656
1330=cut 2657=cut
1331 2658
13321; # End of AnyEvent::Handle 26591
2660

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines