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.98 by root, Thu Oct 2 15:11:01 2008 UTC vs.
Revision 1.240 by root, Tue Dec 17 16:43:15 2013 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines