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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines