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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines