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.26 by root, Sat May 24 15:20:46 2008 UTC vs.
Revision 1.181 by root, Tue Sep 1 10:40:05 2009 UTC

1package AnyEvent::Handle;
2
3no warnings;
4use strict;
5
6use AnyEvent ();
7use AnyEvent::Util ();
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 file handles via AnyEvent
16
17This module is experimental.
18
19=cut
20
21our $VERSION = '0.04';
22 4
23=head1 SYNOPSIS 5=head1 SYNOPSIS
24 6
25 use AnyEvent; 7 use AnyEvent;
26 use AnyEvent::Handle; 8 use AnyEvent::Handle;
27 9
28 my $cv = AnyEvent->condvar; 10 my $cv = AnyEvent->condvar;
29 11
30 my $ae_fh = AnyEvent::Handle->new (fh => \*STDIN); 12 my $hdl; $hdl = new AnyEvent::Handle
31
32 #TODO
33
34 # or use the constructor to pass the callback:
35
36 my $ae_fh2 =
37 AnyEvent::Handle->new (
38 fh => \*STDIN, 13 fh => \*STDIN,
39 on_eof => sub { 14 on_error => sub {
40 $cv->broadcast; 15 my ($hdl, $fatal, $msg) = @_;
41 }, 16 warn "got error $msg\n";
42 #TODO 17 $hdl->destroy;
18 $cv->send;
43 ); 19 );
44 20
45 $cv->wait; 21 # send some request line
22 $hdl->push_write ("getinfo\015\012");
23
24 # read the response line
25 $hdl->push_read (line => sub {
26 my ($hdl, $line) = @_;
27 warn "got line <$line>\n";
28 $cv->send;
29 });
30
31 $cv->recv;
46 32
47=head1 DESCRIPTION 33=head1 DESCRIPTION
48 34
49This module is a helper module to make it easier to do event-based I/O on 35This module is a helper module to make it easier to do event-based I/O on
50filehandles. For utility functions for doing non-blocking connects and accepts 36filehandles.
51on sockets see L<AnyEvent::Util>. 37
38The L<AnyEvent::Intro> tutorial contains some well-documented
39AnyEvent::Handle examples.
52 40
53In the following, when the documentation refers to of "bytes" then this 41In the following, when the documentation refers to of "bytes" then this
54means characters. As sysread and syswrite are used for all I/O, their 42means characters. As sysread and syswrite are used for all I/O, their
55treatment of characters applies to this module as well. 43treatment of characters applies to this module as well.
56 44
45At the very minimum, you should specify C<fh> or C<connect>, and the
46C<on_error> callback.
47
57All callbacks will be invoked with the handle object as their first 48All callbacks will be invoked with the handle object as their first
58argument. 49argument.
59 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
60=head1 METHODS 65=head1 METHODS
61 66
62=over 4 67=over 4
63 68
64=item B<new (%args)> 69=item $handle = B<new> AnyEvent::TLS fh => $filehandle, key => value...
65 70
66The constructor supports these arguments (all as key => value pairs). 71The constructor supports these arguments (all as C<< key => value >> pairs).
67 72
68=over 4 73=over 4
69 74
70=item fh => $filehandle [MANDATORY] 75=item fh => $filehandle [C<fh> or C<connect> MANDATORY]
71 76
72The filehandle this L<AnyEvent::Handle> object will operate on. 77The filehandle this L<AnyEvent::Handle> object will operate on.
73
74NOTE: The filehandle will be set to non-blocking (using 78NOTE: The filehandle will be set to non-blocking mode (using
75AnyEvent::Util::fh_nonblocking). 79C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in
80that mode.
76 81
77=item on_eof => $cb->($self) 82=item connect => [$host, $service] [C<fh> or C<connect> MANDATORY]
78 83
79Set the callback to be called on EOF. 84Try to connect to the specified host and service (port), using
85C<AnyEvent::Socket::tcp_connect>. The C<$host> additionally becomes the
86default C<peername>.
80 87
81While not mandatory, it is highly recommended to set an eof callback, 88You have to specify either this parameter, or C<fh>, above.
82otherwise you might end up with a closed socket while you are still
83waiting for data.
84 89
90It is possible to push requests on the read and write queues, and modify
91properties of the stream, even while AnyEvent::Handle is connecting.
92
93When this parameter is specified, then the C<on_prepare>,
94C<on_connect_error> and C<on_connect> callbacks will be called under the
95appropriate circumstances:
96
97=over 4
98
85=item on_error => $cb->($self) 99=item on_prepare => $cb->($handle)
86 100
101This (rarely used) callback is called before a new connection is
102attempted, but after the file handle has been created. It could be used to
103prepare the file handle with parameters required for the actual connect
104(as opposed to settings that can be changed when the connection is already
105established).
106
107The return value of this callback should be the connect timeout value in
108seconds (or C<0>, or C<undef>, or the empty list, to indicate the default
109timeout is to be used).
110
111=item on_connect => $cb->($handle, $host, $port, $retry->())
112
113This callback is called when a connection has been successfully established.
114
115The actual numeric host and port (the socket peername) are passed as
116parameters, together with a retry callback.
117
118When, for some reason, the handle is not acceptable, then calling
119C<$retry> will continue with the next conenction target (in case of
120multi-homed hosts or SRV records there can be multiple connection
121endpoints). When it is called then the read and write queues, eof status,
122tls status and similar properties of the handle are being reset.
123
124In most cases, ignoring the C<$retry> parameter is the way to go.
125
126=item on_connect_error => $cb->($handle, $message)
127
128This callback is called when the conenction could not be
129established. C<$!> will contain the relevant error code, and C<$message> a
130message describing it (usually the same as C<"$!">).
131
132If this callback isn't specified, then C<on_error> will be called with a
133fatal error instead.
134
135=back
136
137=item on_error => $cb->($handle, $fatal, $message)
138
87This is the fatal error callback, that is called when, well, a fatal error 139This is the error callback, which is called when, well, some error
88occurs, such as not being able to resolve the hostname, failure to connect 140occured, such as not being able to resolve the hostname, failure to
89or a read error. 141connect or a read error.
90 142
91The object will not be in a usable state when this callback has been 143Some errors are fatal (which is indicated by C<$fatal> being true). On
92called. 144fatal errors the handle object will be destroyed (by a call to C<< ->
145destroy >>) after invoking the error callback (which means you are free to
146examine the handle object). Examples of fatal errors are an EOF condition
147with active (but unsatisifable) read watchers (C<EPIPE>) or I/O errors. In
148cases where the other side can close the connection at their will it is
149often easiest to not report C<EPIPE> errors in this callback.
150
151AnyEvent::Handle tries to find an appropriate error code for you to check
152against, but in some cases (TLS errors), this does not work well. It is
153recommended to always output the C<$message> argument in human-readable
154error messages (it's usually the same as C<"$!">).
155
156Non-fatal errors can be retried by simply returning, but it is recommended
157to simply ignore this parameter and instead abondon the handle object
158when this callback is invoked. Examples of non-fatal errors are timeouts
159C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
93 160
94On callback entrance, the value of C<$!> contains the operating system 161On callback entrance, the value of C<$!> contains the operating system
95error (or C<ENOSPC> or C<EPIPE>). 162error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
163C<EPROTO>).
96 164
97While not mandatory, it is I<highly> recommended to set this callback, as 165While not mandatory, it is I<highly> recommended to set this callback, as
98you will not be notified of errors otherwise. The default simply calls 166you will not be notified of errors otherwise. The default simply calls
99die. 167C<croak>.
100 168
101=item on_read => $cb->($self) 169=item on_read => $cb->($handle)
102 170
103This sets the default read callback, which is called when data arrives 171This sets the default read callback, which is called when data arrives
104and no read request is in the queue. 172and no read request is in the queue (unlike read queue callbacks, this
173callback will only be called when at least one octet of data is in the
174read buffer).
105 175
106To access (and remove data from) the read buffer, use the C<< ->rbuf >> 176To access (and remove data from) the read buffer, use the C<< ->rbuf >>
107method or access the C<$self->{rbuf}> member directly. 177method or access the C<< $handle->{rbuf} >> member directly. Note that you
178must not enlarge or modify the read buffer, you can only remove data at
179the beginning from it.
108 180
109When an EOF condition is detected then AnyEvent::Handle will first try to 181When an EOF condition is detected then AnyEvent::Handle will first try to
110feed all the remaining data to the queued callbacks and C<on_read> before 182feed all the remaining data to the queued callbacks and C<on_read> before
111calling the C<on_eof> callback. If no progress can be made, then a fatal 183calling the C<on_eof> callback. If no progress can be made, then a fatal
112error will be raised (with C<$!> set to C<EPIPE>). 184error will be raised (with C<$!> set to C<EPIPE>).
113 185
186Note that, unlike requests in the read queue, an C<on_read> callback
187doesn't mean you I<require> some data: if there is an EOF and there
188are outstanding read requests then an error will be flagged. With an
189C<on_read> callback, the C<on_eof> callback will be invoked.
190
191=item on_eof => $cb->($handle)
192
193Set the callback to be called when an end-of-file condition is detected,
194i.e. in the case of a socket, when the other side has closed the
195connection cleanly, and there are no outstanding read requests in the
196queue (if there are read requests, then an EOF counts as an unexpected
197connection close and will be flagged as an error).
198
199For sockets, this just means that the other side has stopped sending data,
200you can still try to write data, and, in fact, one can return from the EOF
201callback and continue writing data, as only the read part has been shut
202down.
203
204If an EOF condition has been detected but no C<on_eof> callback has been
205set, then a fatal error will be raised with C<$!> set to <0>.
206
114=item on_drain => $cb->() 207=item on_drain => $cb->($handle)
115 208
116This sets the callback that is called when the write buffer becomes empty 209This sets the callback that is called when the write buffer becomes empty
117(or when the callback is set and the buffer is empty already). 210(or when the callback is set and the buffer is empty already).
118 211
119To append to the write buffer, use the C<< ->push_write >> method. 212To append to the write buffer, use the C<< ->push_write >> method.
120 213
214This callback is useful when you don't want to put all of your write data
215into the queue at once, for example, when you want to write the contents
216of some file to the socket you might not want to read the whole file into
217memory and push it into the queue, but instead only read more data from
218the file when the write queue becomes empty.
219
220=item timeout => $fractional_seconds
221
222=item rtimeout => $fractional_seconds
223
224=item wtimeout => $fractional_seconds
225
226If non-zero, then these enables an "inactivity" timeout: whenever this
227many seconds pass without a successful read or write on the underlying
228file handle (or a call to C<timeout_reset>), the C<on_timeout> callback
229will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>
230error will be raised).
231
232There are three variants of the timeouts that work fully independent
233of each other, for both read and write, just read, and just write:
234C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks
235C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions
236C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>.
237
238Note that timeout processing is also active when you currently do not have
239any outstanding read or write requests: If you plan to keep the connection
240idle then you should disable the timout temporarily or ignore the timeout
241in the C<on_timeout> callback, in which case AnyEvent::Handle will simply
242restart the timeout.
243
244Zero (the default) disables this timeout.
245
246=item on_timeout => $cb->($handle)
247
248Called whenever the inactivity timeout passes. If you return from this
249callback, then the timeout will be reset as if some activity had happened,
250so this condition is not fatal in any way.
251
121=item rbuf_max => <bytes> 252=item rbuf_max => <bytes>
122 253
123If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) 254If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
124when the read buffer ever (strictly) exceeds this size. This is useful to 255when the read buffer ever (strictly) exceeds this size. This is useful to
125avoid denial-of-service attacks. 256avoid some forms of denial-of-service attacks.
126 257
127For example, a server accepting connections from untrusted sources should 258For example, a server accepting connections from untrusted sources should
128be configured to accept only so-and-so much data that it cannot act on 259be configured to accept only so-and-so much data that it cannot act on
129(for example, when expecting a line, an attacker could send an unlimited 260(for example, when expecting a line, an attacker could send an unlimited
130amount of data without a callback ever being called as long as the line 261amount of data without a callback ever being called as long as the line
131isn't finished). 262isn't finished).
132 263
264=item autocork => <boolean>
265
266When disabled (the default), then C<push_write> will try to immediately
267write the data to the handle, if possible. This avoids having to register
268a write watcher and wait for the next event loop iteration, but can
269be inefficient if you write multiple small chunks (on the wire, this
270disadvantage is usually avoided by your kernel's nagle algorithm, see
271C<no_delay>, but this option can save costly syscalls).
272
273When enabled, then writes will always be queued till the next event loop
274iteration. This is efficient when you do many small writes per iteration,
275but less efficient when you do a single write only per iteration (or when
276the write buffer often is full). It also increases write latency.
277
278=item no_delay => <boolean>
279
280When doing small writes on sockets, your operating system kernel might
281wait a bit for more data before actually sending it out. This is called
282the Nagle algorithm, and usually it is beneficial.
283
284In some situations you want as low a delay as possible, which can be
285accomplishd by setting this option to a true value.
286
287The default is your opertaing system's default behaviour (most likely
288enabled), this option explicitly enables or disables it, if possible.
289
133=item read_size => <bytes> 290=item read_size => <bytes>
134 291
135The default read block size (the amount of bytes this module will try to read 292The default read block size (the amount of bytes this module will
136on each [loop iteration). Default: C<4096>. 293try to read during each loop iteration, which affects memory
294requirements). Default: C<8192>.
137 295
138=item low_water_mark => <bytes> 296=item low_water_mark => <bytes>
139 297
140Sets the amount of bytes (default: C<0>) that make up an "empty" write 298Sets the amount of bytes (default: C<0>) that make up an "empty" write
141buffer: If the write reaches this size or gets even samller it is 299buffer: If the write reaches this size or gets even samller it is
142considered empty. 300considered empty.
143 301
302Sometimes it can be beneficial (for performance reasons) to add data to
303the write buffer before it is fully drained, but this is a rare case, as
304the operating system kernel usually buffers data as well, so the default
305is good in almost all cases.
306
307=item linger => <seconds>
308
309If non-zero (default: C<3600>), then the destructor of the
310AnyEvent::Handle object will check whether there is still outstanding
311write data and will install a watcher that will write this data to the
312socket. No errors will be reported (this mostly matches how the operating
313system treats outstanding data at socket close time).
314
315This will not work for partial TLS data that could not be encoded
316yet. This data will be lost. Calling the C<stoptls> method in time might
317help.
318
319=item peername => $string
320
321A string used to identify the remote site - usually the DNS hostname
322(I<not> IDN!) used to create the connection, rarely the IP address.
323
324Apart from being useful in error messages, this string is also used in TLS
325peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
326verification will be skipped when C<peername> is not specified or
327C<undef>.
328
144=item tls => "accept" | "connect" | Net::SSLeay::SSL object 329=item tls => "accept" | "connect" | Net::SSLeay::SSL object
145 330
146When this parameter is given, it enables TLS (SSL) mode, that means it 331When this parameter is given, it enables TLS (SSL) mode, that means
147will start making tls handshake and will transparently encrypt/decrypt 332AnyEvent will start a TLS handshake as soon as the conenction has been
148data. 333established and will transparently encrypt/decrypt data afterwards.
334
335All TLS protocol errors will be signalled as C<EPROTO>, with an
336appropriate error message.
149 337
150TLS mode requires Net::SSLeay to be installed (it will be loaded 338TLS mode requires Net::SSLeay to be installed (it will be loaded
151automatically when you try to create a TLS handle). 339automatically when you try to create a TLS handle): this module doesn't
340have a dependency on that module, so if your module requires it, you have
341to add the dependency yourself.
152 342
153For the TLS server side, use C<accept>, and for the TLS client side of a 343Unlike TCP, TLS has a server and client side: for the TLS server side, use
154connection, use C<connect> mode. 344C<accept>, and for the TLS client side of a connection, use C<connect>
345mode.
155 346
156You can also provide your own TLS connection object, but you have 347You can also provide your own TLS connection object, but you have
157to make sure that you call either C<Net::SSLeay::set_connect_state> 348to make sure that you call either C<Net::SSLeay::set_connect_state>
158or C<Net::SSLeay::set_accept_state> on it before you pass it to 349or C<Net::SSLeay::set_accept_state> on it before you pass it to
159AnyEvent::Handle. 350AnyEvent::Handle. Also, this module will take ownership of this connection
351object.
160 352
353At some future point, AnyEvent::Handle might switch to another TLS
354implementation, then the option to use your own session object will go
355away.
356
357B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
358passing in the wrong integer will lead to certain crash. This most often
359happens when one uses a stylish C<< tls => 1 >> and is surprised about the
360segmentation fault.
361
161See the C<starttls> method if you need to start TLs negotiation later. 362See the C<< ->starttls >> method for when need to start TLS negotiation later.
162 363
163=item tls_ctx => $ssl_ctx 364=item tls_ctx => $anyevent_tls
164 365
165Use the given Net::SSLeay::CTX object to create the new TLS connection 366Use the given C<AnyEvent::TLS> object to create the new TLS connection
166(unless a connection object was specified directly). If this parameter is 367(unless a connection object was specified directly). If this parameter is
167missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 368missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.
168 369
370Instead of an object, you can also specify a hash reference with C<< key
371=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
372new TLS context object.
373
374=item on_starttls => $cb->($handle, $success[, $error_message])
375
376This callback will be invoked when the TLS/SSL handshake has finished. If
377C<$success> is true, then the TLS handshake succeeded, otherwise it failed
378(C<on_stoptls> will not be called in this case).
379
380The session in C<< $handle->{tls} >> can still be examined in this
381callback, even when the handshake was not successful.
382
383TLS handshake failures will not cause C<on_error> to be invoked when this
384callback is in effect, instead, the error message will be passed to C<on_starttls>.
385
386Without this callback, handshake failures lead to C<on_error> being
387called, as normal.
388
389Note that you cannot call C<starttls> right again in this callback. If you
390need to do that, start an zero-second timer instead whose callback can
391then call C<< ->starttls >> again.
392
393=item on_stoptls => $cb->($handle)
394
395When a SSLv3/TLS shutdown/close notify/EOF is detected and this callback is
396set, then it will be invoked after freeing the TLS session. If it is not,
397then a TLS shutdown condition will be treated like a normal EOF condition
398on the handle.
399
400The session in C<< $handle->{tls} >> can still be examined in this
401callback.
402
403This callback will only be called on TLS shutdowns, not when the
404underlying handle signals EOF.
405
406=item json => JSON or JSON::XS object
407
408This is the json coder object used by the C<json> read and write types.
409
410If you don't supply it, then AnyEvent::Handle will create and use a
411suitable one (on demand), which will write and expect UTF-8 encoded JSON
412texts.
413
414Note that you are responsible to depend on the JSON module if you want to
415use this functionality, as AnyEvent does not have a dependency itself.
416
169=back 417=back
170 418
171=cut 419=cut
172 420
173sub new { 421sub new {
174 my $class = shift; 422 my $class = shift;
175
176 my $self = bless { @_ }, $class; 423 my $self = bless { @_ }, $class;
177 424
178 $self->{fh} or Carp::croak "mandatory argument fh is missing"; 425 if ($self->{fh}) {
426 $self->_start;
427 return unless $self->{fh}; # could be gone by now
428
429 } elsif ($self->{connect}) {
430 require AnyEvent::Socket;
431
432 $self->{peername} = $self->{connect}[0]
433 unless exists $self->{peername};
434
435 $self->{_skip_drain_rbuf} = 1;
436
437 {
438 Scalar::Util::weaken (my $self = $self);
439
440 $self->{_connect} =
441 AnyEvent::Socket::tcp_connect (
442 $self->{connect}[0],
443 $self->{connect}[1],
444 sub {
445 my ($fh, $host, $port, $retry) = @_;
446
447 if ($fh) {
448 $self->{fh} = $fh;
449
450 delete $self->{_skip_drain_rbuf};
451 $self->_start;
452
453 $self->{on_connect}
454 and $self->{on_connect}($self, $host, $port, sub {
455 delete @$self{qw(fh _tw _rtw _wtw _ww _rw _eof _queue rbuf _wbuf tls _tls_rbuf _tls_wbuf)};
456 $self->{_skip_drain_rbuf} = 1;
457 &$retry;
458 });
459
460 } else {
461 if ($self->{on_connect_error}) {
462 $self->{on_connect_error}($self, "$!");
463 $self->destroy;
464 } else {
465 $self->_error ($!, 1);
466 }
467 }
468 },
469 sub {
470 local $self->{fh} = $_[0];
471
472 $self->{on_prepare}
473 ? $self->{on_prepare}->($self)
474 : ()
475 }
476 );
477 }
478
479 } else {
480 Carp::croak "AnyEvent::Handle: either an existing fh or the connect parameter must be specified";
481 }
482
483 $self
484}
485
486sub _start {
487 my ($self) = @_;
179 488
180 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 489 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
181 490
182 if ($self->{tls}) { 491 $self->{_activity} =
183 require Net::SSLeay; 492 $self->{_ractivity} =
493 $self->{_wactivity} = AE::now;
494
495 $self->timeout (delete $self->{timeout} ) if $self->{timeout};
496 $self->rtimeout (delete $self->{rtimeout}) if $self->{rtimeout};
497 $self->wtimeout (delete $self->{wtimeout}) if $self->{wtimeout};
498
499 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
500
184 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}); 501 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
185 } 502 if $self->{tls};
186 503
187 $self->on_eof (delete $self->{on_eof} ) if $self->{on_eof};
188 $self->on_error (delete $self->{on_error}) if $self->{on_error};
189 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; 504 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain};
190 $self->on_read (delete $self->{on_read} ) if $self->{on_read};
191 505
192 $self->start_read; 506 $self->start_read
507 if $self->{on_read} || @{ $self->{_queue} };
193 508
194 $self 509 $self->_drain_wbuf;
195} 510}
196 511
197sub _shutdown {
198 my ($self) = @_;
199
200 delete $self->{rw};
201 delete $self->{ww};
202 delete $self->{fh};
203}
204
205sub error { 512sub _error {
206 my ($self) = @_; 513 my ($self, $errno, $fatal, $message) = @_;
207 514
208 { 515 $! = $errno;
209 local $!; 516 $message ||= "$!";
210 $self->_shutdown;
211 }
212 517
213 if ($self->{on_error}) { 518 if ($self->{on_error}) {
214 $self->{on_error}($self); 519 $self->{on_error}($self, $fatal, $message);
215 } else { 520 $self->destroy if $fatal;
521 } elsif ($self->{fh}) {
522 $self->destroy;
216 die "AnyEvent::Handle uncaught fatal error: $!"; 523 Carp::croak "AnyEvent::Handle uncaught error: $message";
217 } 524 }
218} 525}
219 526
220=item $fh = $handle->fh 527=item $fh = $handle->fh
221 528
222This method returns the file handle of the L<AnyEvent::Handle> object. 529This method returns the file handle used to create the L<AnyEvent::Handle> object.
223 530
224=cut 531=cut
225 532
226sub fh { $_[0]->{fh} } 533sub fh { $_[0]{fh} }
227 534
228=item $handle->on_error ($cb) 535=item $handle->on_error ($cb)
229 536
230Replace the current C<on_error> callback (see the C<on_error> constructor argument). 537Replace the current C<on_error> callback (see the C<on_error> constructor argument).
231 538
243 550
244sub on_eof { 551sub on_eof {
245 $_[0]{on_eof} = $_[1]; 552 $_[0]{on_eof} = $_[1];
246} 553}
247 554
555=item $handle->on_timeout ($cb)
556
557=item $handle->on_rtimeout ($cb)
558
559=item $handle->on_wtimeout ($cb)
560
561Replace the current C<on_timeout>, C<on_rtimeout> or C<on_wtimeout>
562callback, or disables the callback (but not the timeout) if C<$cb> =
563C<undef>. See the C<timeout> constructor argument and method.
564
565=cut
566
567# see below
568
569=item $handle->autocork ($boolean)
570
571Enables or disables the current autocork behaviour (see C<autocork>
572constructor argument). Changes will only take effect on the next write.
573
574=cut
575
576sub autocork {
577 $_[0]{autocork} = $_[1];
578}
579
580=item $handle->no_delay ($boolean)
581
582Enables or disables the C<no_delay> setting (see constructor argument of
583the same name for details).
584
585=cut
586
587sub no_delay {
588 $_[0]{no_delay} = $_[1];
589
590 eval {
591 local $SIG{__DIE__};
592 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1]
593 if $_[0]{fh};
594 };
595}
596
597=item $handle->on_starttls ($cb)
598
599Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument).
600
601=cut
602
603sub on_starttls {
604 $_[0]{on_starttls} = $_[1];
605}
606
607=item $handle->on_stoptls ($cb)
608
609Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
610
611=cut
612
613sub on_starttls {
614 $_[0]{on_stoptls} = $_[1];
615}
616
617=item $handle->rbuf_max ($max_octets)
618
619Configures the C<rbuf_max> setting (C<undef> disables it).
620
621=cut
622
623sub rbuf_max {
624 $_[0]{rbuf_max} = $_[1];
625}
626
627#############################################################################
628
629=item $handle->timeout ($seconds)
630
631=item $handle->rtimeout ($seconds)
632
633=item $handle->wtimeout ($seconds)
634
635Configures (or disables) the inactivity timeout.
636
637=item $handle->timeout_reset
638
639=item $handle->rtimeout_reset
640
641=item $handle->wtimeout_reset
642
643Reset the activity timeout, as if data was received or sent.
644
645These methods are cheap to call.
646
647=cut
648
649for my $dir ("", "r", "w") {
650 my $timeout = "${dir}timeout";
651 my $tw = "_${dir}tw";
652 my $on_timeout = "on_${dir}timeout";
653 my $activity = "_${dir}activity";
654 my $cb;
655
656 *$on_timeout = sub {
657 $_[0]{$on_timeout} = $_[1];
658 };
659
660 *$timeout = sub {
661 my ($self, $new_value) = @_;
662
663 $self->{$timeout} = $new_value;
664 delete $self->{$tw}; &$cb;
665 };
666
667 *{"${dir}timeout_reset"} = sub {
668 $_[0]{$activity} = AE::now;
669 };
670
671 # main workhorse:
672 # reset the timeout watcher, as neccessary
673 # also check for time-outs
674 $cb = sub {
675 my ($self) = @_;
676
677 if ($self->{$timeout} && $self->{fh}) {
678 my $NOW = AE::now;
679
680 # when would the timeout trigger?
681 my $after = $self->{$activity} + $self->{$timeout} - $NOW;
682
683 # now or in the past already?
684 if ($after <= 0) {
685 $self->{$activity} = $NOW;
686
687 if ($self->{$on_timeout}) {
688 $self->{$on_timeout}($self);
689 } else {
690 $self->_error (Errno::ETIMEDOUT);
691 }
692
693 # callback could have changed timeout value, optimise
694 return unless $self->{$timeout};
695
696 # calculate new after
697 $after = $self->{$timeout};
698 }
699
700 Scalar::Util::weaken $self;
701 return unless $self; # ->error could have destroyed $self
702
703 $self->{$tw} ||= AE::timer $after, 0, sub {
704 delete $self->{$tw};
705 $cb->($self);
706 };
707 } else {
708 delete $self->{$tw};
709 }
710 }
711}
712
248############################################################################# 713#############################################################################
249 714
250=back 715=back
251 716
252=head2 WRITE QUEUE 717=head2 WRITE QUEUE
273 my ($self, $cb) = @_; 738 my ($self, $cb) = @_;
274 739
275 $self->{on_drain} = $cb; 740 $self->{on_drain} = $cb;
276 741
277 $cb->($self) 742 $cb->($self)
278 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 743 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
279} 744}
280 745
281=item $handle->push_write ($data) 746=item $handle->push_write ($data)
282 747
283Queues the given scalar to be written. You can push as much data as you 748Queues the given scalar to be written. You can push as much data as you
287=cut 752=cut
288 753
289sub _drain_wbuf { 754sub _drain_wbuf {
290 my ($self) = @_; 755 my ($self) = @_;
291 756
292 unless ($self->{ww}) { 757 if (!$self->{_ww} && length $self->{wbuf}) {
758
293 Scalar::Util::weaken $self; 759 Scalar::Util::weaken $self;
760
294 my $cb = sub { 761 my $cb = sub {
295 my $len = syswrite $self->{fh}, $self->{wbuf}; 762 my $len = syswrite $self->{fh}, $self->{wbuf};
296 763
297 if ($len > 0) { 764 if (defined $len) {
298 substr $self->{wbuf}, 0, $len, ""; 765 substr $self->{wbuf}, 0, $len, "";
299 766
767 $self->{_activity} = $self->{_wactivity} = AE::now;
768
300 $self->{on_drain}($self) 769 $self->{on_drain}($self)
301 if $self->{low_water_mark} >= length $self->{wbuf} 770 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
302 && $self->{on_drain}; 771 && $self->{on_drain};
303 772
304 delete $self->{ww} unless length $self->{wbuf}; 773 delete $self->{_ww} unless length $self->{wbuf};
305 } elsif ($! != EAGAIN && $! != EINTR) { 774 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
306 $self->error; 775 $self->_error ($!, 1);
307 } 776 }
308 }; 777 };
309 778
310 $self->{ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb); 779 # try to write data immediately
780 $cb->() unless $self->{autocork};
311 781
312 $cb->($self); 782 # if still data left in wbuf, we need to poll
783 $self->{_ww} = AE::io $self->{fh}, 1, $cb
784 if length $self->{wbuf};
313 }; 785 };
786}
787
788our %WH;
789
790sub register_write_type($$) {
791 $WH{$_[0]} = $_[1];
314} 792}
315 793
316sub push_write { 794sub push_write {
317 my $self = shift; 795 my $self = shift;
318 796
797 if (@_ > 1) {
798 my $type = shift;
799
800 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write")
801 ->($self, @_);
802 }
803
319 if ($self->{filter_w}) { 804 if ($self->{tls}) {
320 $self->{filter_w}->($self, \$_[0]); 805 $self->{_tls_wbuf} .= $_[0];
806 &_dotls ($self) if $self->{fh};
321 } else { 807 } else {
322 $self->{wbuf} .= $_[0]; 808 $self->{wbuf} .= $_[0];
323 $self->_drain_wbuf; 809 $self->_drain_wbuf if $self->{fh};
324 } 810 }
325} 811}
812
813=item $handle->push_write (type => @args)
814
815Instead of formatting your data yourself, you can also let this module do
816the job by specifying a type and type-specific arguments.
817
818Predefined types are (if you have ideas for additional types, feel free to
819drop by and tell us):
820
821=over 4
822
823=item netstring => $string
824
825Formats the given value as netstring
826(http://cr.yp.to/proto/netstrings.txt, this is not a recommendation to use them).
827
828=cut
829
830register_write_type netstring => sub {
831 my ($self, $string) = @_;
832
833 (length $string) . ":$string,"
834};
835
836=item packstring => $format, $data
837
838An octet string prefixed with an encoded length. The encoding C<$format>
839uses the same format as a Perl C<pack> format, but must specify a single
840integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
841optional C<!>, C<< < >> or C<< > >> modifier).
842
843=cut
844
845register_write_type packstring => sub {
846 my ($self, $format, $string) = @_;
847
848 pack "$format/a*", $string
849};
850
851=item json => $array_or_hashref
852
853Encodes the given hash or array reference into a JSON object. Unless you
854provide your own JSON object, this means it will be encoded to JSON text
855in UTF-8.
856
857JSON objects (and arrays) are self-delimiting, so you can write JSON at
858one end of a handle and read them at the other end without using any
859additional framing.
860
861The generated JSON text is guaranteed not to contain any newlines: While
862this module doesn't need delimiters after or between JSON texts to be
863able to read them, many other languages depend on that.
864
865A simple RPC protocol that interoperates easily with others is to send
866JSON arrays (or objects, although arrays are usually the better choice as
867they mimic how function argument passing works) and a newline after each
868JSON text:
869
870 $handle->push_write (json => ["method", "arg1", "arg2"]); # whatever
871 $handle->push_write ("\012");
872
873An AnyEvent::Handle receiver would simply use the C<json> read type and
874rely on the fact that the newline will be skipped as leading whitespace:
875
876 $handle->push_read (json => sub { my $array = $_[1]; ... });
877
878Other languages could read single lines terminated by a newline and pass
879this line into their JSON decoder of choice.
880
881=cut
882
883sub json_coder() {
884 eval { require JSON::XS; JSON::XS->new->utf8 }
885 || do { require JSON; JSON->new->utf8 }
886}
887
888register_write_type json => sub {
889 my ($self, $ref) = @_;
890
891 my $json = $self->{json} ||= json_coder;
892
893 $json->encode ($ref)
894};
895
896=item storable => $reference
897
898Freezes the given reference using L<Storable> and writes it to the
899handle. Uses the C<nfreeze> format.
900
901=cut
902
903register_write_type storable => sub {
904 my ($self, $ref) = @_;
905
906 require Storable;
907
908 pack "w/a*", Storable::nfreeze ($ref)
909};
910
911=back
912
913=item $handle->push_shutdown
914
915Sometimes you know you want to close the socket after writing your data
916before it was actually written. One way to do that is to replace your
917C<on_drain> handler by a callback that shuts down the socket (and set
918C<low_water_mark> to C<0>). This method is a shorthand for just that, and
919replaces the C<on_drain> callback with:
920
921 sub { shutdown $_[0]{fh}, 1 } # for push_shutdown
922
923This simply shuts down the write side and signals an EOF condition to the
924the peer.
925
926You can rely on the normal read queue and C<on_eof> handling
927afterwards. This is the cleanest way to close a connection.
928
929=cut
930
931sub push_shutdown {
932 my ($self) = @_;
933
934 delete $self->{low_water_mark};
935 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
936}
937
938=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args)
939
940This function (not method) lets you add your own types to C<push_write>.
941Whenever the given C<type> is used, C<push_write> will invoke the code
942reference with the handle object and the remaining arguments.
943
944The code reference is supposed to return a single octet string that will
945be appended to the write buffer.
946
947Note that this is a function, and all types registered this way will be
948global, so try to use unique names.
949
950=cut
326 951
327############################################################################# 952#############################################################################
328 953
329=back 954=back
330 955
337ways, the "simple" way, using only C<on_read> and the "complex" way, using 962ways, the "simple" way, using only C<on_read> and the "complex" way, using
338a queue. 963a queue.
339 964
340In the simple case, you just install an C<on_read> callback and whenever 965In the simple case, you just install an C<on_read> callback and whenever
341new data arrives, it will be called. You can then remove some data (if 966new data arrives, it will be called. You can then remove some data (if
342enough is there) from the read buffer (C<< $handle->rbuf >>) if you want 967enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna
343or not. 968leave the data there if you want to accumulate more (e.g. when only a
969partial message has been received so far).
344 970
345In the more complex case, you want to queue multiple callbacks. In this 971In the more complex case, you want to queue multiple callbacks. In this
346case, AnyEvent::Handle will call the first queued callback each time new 972case, AnyEvent::Handle will call the first queued callback each time new
347data arrives and removes it when it has done its job (see C<push_read>, 973data arrives (also the first time it is queued) and removes it when it has
348below). 974done its job (see C<push_read>, below).
349 975
350This way you can, for example, push three line-reads, followed by reading 976This way you can, for example, push three line-reads, followed by reading
351a chunk of data, and AnyEvent::Handle will execute them in order. 977a chunk of data, and AnyEvent::Handle will execute them in order.
352 978
353Example 1: EPP protocol parser. EPP sends 4 byte length info, followed by 979Example 1: EPP protocol parser. EPP sends 4 byte length info, followed by
354the specified number of bytes which give an XML datagram. 980the specified number of bytes which give an XML datagram.
355 981
356 # in the default state, expect some header bytes 982 # in the default state, expect some header bytes
357 $handle->on_read (sub { 983 $handle->on_read (sub {
358 # some data is here, now queue the length-header-read (4 octets) 984 # some data is here, now queue the length-header-read (4 octets)
359 shift->unshift_read_chunk (4, sub { 985 shift->unshift_read (chunk => 4, sub {
360 # header arrived, decode 986 # header arrived, decode
361 my $len = unpack "N", $_[1]; 987 my $len = unpack "N", $_[1];
362 988
363 # now read the payload 989 # now read the payload
364 shift->unshift_read_chunk ($len, sub { 990 shift->unshift_read (chunk => $len, sub {
365 my $xml = $_[1]; 991 my $xml = $_[1];
366 # handle xml 992 # handle xml
367 }); 993 });
368 }); 994 });
369 }); 995 });
370 996
371Example 2: Implement a client for a protocol that replies either with 997Example 2: Implement a client for a protocol that replies either with "OK"
372"OK" and another line or "ERROR" for one request, and 64 bytes for the 998and another line or "ERROR" for the first request that is sent, and 64
373second request. Due tot he availability of a full queue, we can just 999bytes for the second request. Due to the availability of a queue, we can
374pipeline sending both requests and manipulate the queue as necessary in 1000just pipeline sending both requests and manipulate the queue as necessary
375the callbacks: 1001in the callbacks.
376 1002
377 # request one 1003When the first callback is called and sees an "OK" response, it will
1004C<unshift> another line-read. This line-read will be queued I<before> the
100564-byte chunk callback.
1006
1007 # request one, returns either "OK + extra line" or "ERROR"
378 $handle->push_write ("request 1\015\012"); 1008 $handle->push_write ("request 1\015\012");
379 1009
380 # we expect "ERROR" or "OK" as response, so push a line read 1010 # we expect "ERROR" or "OK" as response, so push a line read
381 $handle->push_read_line (sub { 1011 $handle->push_read (line => sub {
382 # if we got an "OK", we have to _prepend_ another line, 1012 # if we got an "OK", we have to _prepend_ another line,
383 # so it will be read before the second request reads its 64 bytes 1013 # so it will be read before the second request reads its 64 bytes
384 # which are already in the queue when this callback is called 1014 # which are already in the queue when this callback is called
385 # we don't do this in case we got an error 1015 # we don't do this in case we got an error
386 if ($_[1] eq "OK") { 1016 if ($_[1] eq "OK") {
387 $_[0]->unshift_read_line (sub { 1017 $_[0]->unshift_read (line => sub {
388 my $response = $_[1]; 1018 my $response = $_[1];
389 ... 1019 ...
390 }); 1020 });
391 } 1021 }
392 }); 1022 });
393 1023
394 # request two 1024 # request two, simply returns 64 octets
395 $handle->push_write ("request 2\015\012"); 1025 $handle->push_write ("request 2\015\012");
396 1026
397 # simply read 64 bytes, always 1027 # simply read 64 bytes, always
398 $handle->push_read_chunk (64, sub { 1028 $handle->push_read (chunk => 64, sub {
399 my $response = $_[1]; 1029 my $response = $_[1];
400 ... 1030 ...
401 }); 1031 });
402 1032
403=over 4 1033=over 4
404 1034
405=cut 1035=cut
406 1036
407sub _drain_rbuf { 1037sub _drain_rbuf {
408 my ($self) = @_; 1038 my ($self) = @_;
1039
1040 # avoid recursion
1041 return if $self->{_skip_drain_rbuf};
1042 local $self->{_skip_drain_rbuf} = 1;
1043
1044 while () {
1045 # we need to use a separate tls read buffer, as we must not receive data while
1046 # we are draining the buffer, and this can only happen with TLS.
1047 $self->{rbuf} .= delete $self->{_tls_rbuf}
1048 if exists $self->{_tls_rbuf};
1049
1050 my $len = length $self->{rbuf};
1051
1052 if (my $cb = shift @{ $self->{_queue} }) {
1053 unless ($cb->($self)) {
1054 # no progress can be made
1055 # (not enough data and no data forthcoming)
1056 $self->_error (Errno::EPIPE, 1), return
1057 if $self->{_eof};
1058
1059 unshift @{ $self->{_queue} }, $cb;
1060 last;
1061 }
1062 } elsif ($self->{on_read}) {
1063 last unless $len;
1064
1065 $self->{on_read}($self);
1066
1067 if (
1068 $len == length $self->{rbuf} # if no data has been consumed
1069 && !@{ $self->{_queue} } # and the queue is still empty
1070 && $self->{on_read} # but we still have on_read
1071 ) {
1072 # no further data will arrive
1073 # so no progress can be made
1074 $self->_error (Errno::EPIPE, 1), return
1075 if $self->{_eof};
1076
1077 last; # more data might arrive
1078 }
1079 } else {
1080 # read side becomes idle
1081 delete $self->{_rw} unless $self->{tls};
1082 last;
1083 }
1084 }
1085
1086 if ($self->{_eof}) {
1087 $self->{on_eof}
1088 ? $self->{on_eof}($self)
1089 : $self->_error (0, 1, "Unexpected end-of-file");
1090
1091 return;
1092 }
409 1093
410 if ( 1094 if (
411 defined $self->{rbuf_max} 1095 defined $self->{rbuf_max}
412 && $self->{rbuf_max} < length $self->{rbuf} 1096 && $self->{rbuf_max} < length $self->{rbuf}
413 ) { 1097 ) {
414 $! = &Errno::ENOSPC; return $self->error; 1098 $self->_error (Errno::ENOSPC, 1), return;
415 } 1099 }
416 1100
417 return if $self->{in_drain}; 1101 # may need to restart read watcher
418 local $self->{in_drain} = 1; 1102 unless ($self->{_rw}) {
419 1103 $self->start_read
420 while (my $len = length $self->{rbuf}) { 1104 if $self->{on_read} || @{ $self->{_queue} };
421 no strict 'refs';
422 if (my $cb = shift @{ $self->{queue} }) {
423 if (!$cb->($self)) {
424 if ($self->{eof}) {
425 # no progress can be made (not enough data and no data forthcoming)
426 $! = &Errno::EPIPE; return $self->error;
427 }
428
429 unshift @{ $self->{queue} }, $cb;
430 return;
431 }
432 } elsif ($self->{on_read}) {
433 $self->{on_read}($self);
434
435 if (
436 $self->{eof} # if no further data will arrive
437 && $len == length $self->{rbuf} # and no data has been consumed
438 && !@{ $self->{queue} } # and the queue is still empty
439 && $self->{on_read} # and we still want to read data
440 ) {
441 # then no progress can be made
442 $! = &Errno::EPIPE; return $self->error;
443 }
444 } else {
445 # read side becomes idle
446 delete $self->{rw};
447 return;
448 }
449 }
450
451 if ($self->{eof}) {
452 $self->_shutdown;
453 $self->{on_eof}($self)
454 if $self->{on_eof};
455 } 1105 }
456} 1106}
457 1107
458=item $handle->on_read ($cb) 1108=item $handle->on_read ($cb)
459 1109
465 1115
466sub on_read { 1116sub on_read {
467 my ($self, $cb) = @_; 1117 my ($self, $cb) = @_;
468 1118
469 $self->{on_read} = $cb; 1119 $self->{on_read} = $cb;
1120 $self->_drain_rbuf if $cb;
470} 1121}
471 1122
472=item $handle->rbuf 1123=item $handle->rbuf
473 1124
474Returns the read buffer (as a modifiable lvalue). 1125Returns the read buffer (as a modifiable lvalue).
475 1126
476You can access the read buffer directly as the C<< ->{rbuf} >> member, if 1127You can access the read buffer directly as the C<< ->{rbuf} >>
477you want. 1128member, if you want. However, the only operation allowed on the
1129read buffer (apart from looking at it) is removing data from its
1130beginning. Otherwise modifying or appending to it is not allowed and will
1131lead to hard-to-track-down bugs.
478 1132
479NOTE: The read buffer should only be used or modified if the C<on_read>, 1133NOTE: The read buffer should only be used or modified if the C<on_read>,
480C<push_read> or C<unshift_read> methods are used. The other read methods 1134C<push_read> or C<unshift_read> methods are used. The other read methods
481automatically manage the read buffer. 1135automatically manage the read buffer.
482 1136
505interested in (which can be none at all) and return a true value. After returning 1159interested in (which can be none at all) and return a true value. After returning
506true, it will be removed from the queue. 1160true, it will be removed from the queue.
507 1161
508=cut 1162=cut
509 1163
1164our %RH;
1165
1166sub register_read_type($$) {
1167 $RH{$_[0]} = $_[1];
1168}
1169
510sub push_read { 1170sub push_read {
511 my ($self, $cb) = @_; 1171 my $self = shift;
1172 my $cb = pop;
512 1173
1174 if (@_) {
1175 my $type = shift;
1176
1177 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_read")
1178 ->($self, $cb, @_);
1179 }
1180
513 push @{ $self->{queue} }, $cb; 1181 push @{ $self->{_queue} }, $cb;
514 $self->_drain_rbuf; 1182 $self->_drain_rbuf;
515} 1183}
516 1184
517sub unshift_read { 1185sub unshift_read {
518 my ($self, $cb) = @_; 1186 my $self = shift;
1187 my $cb = pop;
519 1188
1189 if (@_) {
1190 my $type = shift;
1191
1192 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::unshift_read")
1193 ->($self, $cb, @_);
1194 }
1195
520 push @{ $self->{queue} }, $cb; 1196 unshift @{ $self->{_queue} }, $cb;
521 $self->_drain_rbuf; 1197 $self->_drain_rbuf;
522} 1198}
523 1199
524=item $handle->push_read_chunk ($len, $cb->($self, $data)) 1200=item $handle->push_read (type => @args, $cb)
525 1201
526=item $handle->unshift_read_chunk ($len, $cb->($self, $data)) 1202=item $handle->unshift_read (type => @args, $cb)
527 1203
528Append the given callback to the end of the queue (C<push_read_chunk>) or 1204Instead of providing a callback that parses the data itself you can chose
529prepend it (C<unshift_read_chunk>). 1205between a number of predefined parsing formats, for chunks of data, lines
1206etc.
530 1207
531The callback will be called only once C<$len> bytes have been read, and 1208Predefined types are (if you have ideas for additional types, feel free to
532these C<$len> bytes will be passed to the callback. 1209drop by and tell us):
533 1210
534=cut 1211=over 4
535 1212
536sub _read_chunk($$) { 1213=item chunk => $octets, $cb->($handle, $data)
1214
1215Invoke the callback only once C<$octets> bytes have been read. Pass the
1216data read to the callback. The callback will never be called with less
1217data.
1218
1219Example: read 2 bytes.
1220
1221 $handle->push_read (chunk => 2, sub {
1222 warn "yay ", unpack "H*", $_[1];
1223 });
1224
1225=cut
1226
1227register_read_type chunk => sub {
537 my ($self, $len, $cb) = @_; 1228 my ($self, $cb, $len) = @_;
538 1229
539 sub { 1230 sub {
540 $len <= length $_[0]{rbuf} or return; 1231 $len <= length $_[0]{rbuf} or return;
541 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, ""); 1232 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, "");
542 1 1233 1
543 } 1234 }
544} 1235};
545 1236
546sub push_read_chunk { 1237=item line => [$eol, ]$cb->($handle, $line, $eol)
547 $_[0]->push_read (&_read_chunk);
548}
549
550
551sub unshift_read_chunk {
552 $_[0]->unshift_read (&_read_chunk);
553}
554
555=item $handle->push_read_line ([$eol, ]$cb->($self, $line, $eol))
556
557=item $handle->unshift_read_line ([$eol, ]$cb->($self, $line, $eol))
558
559Append the given callback to the end of the queue (C<push_read_line>) or
560prepend it (C<unshift_read_line>).
561 1238
562The callback will be called only once a full line (including the end of 1239The callback will be called only once a full line (including the end of
563line marker, C<$eol>) has been read. This line (excluding the end of line 1240line marker, C<$eol>) has been read. This line (excluding the end of line
564marker) will be passed to the callback as second argument (C<$line>), and 1241marker) will be passed to the callback as second argument (C<$line>), and
565the end of line marker as the third argument (C<$eol>). 1242the end of line marker as the third argument (C<$eol>).
576Partial lines at the end of the stream will never be returned, as they are 1253Partial lines at the end of the stream will never be returned, as they are
577not marked by the end of line marker. 1254not marked by the end of line marker.
578 1255
579=cut 1256=cut
580 1257
581sub _read_line($$) { 1258register_read_type line => sub {
582 my $self = shift; 1259 my ($self, $cb, $eol) = @_;
583 my $cb = pop;
584 my $eol = @_ ? shift : qr|(\015?\012)|;
585 my $pos;
586 1260
1261 if (@_ < 3) {
1262 # this is more than twice as fast as the generic code below
1263 sub {
1264 $_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return;
1265
1266 $cb->($_[0], $1, $2);
1267 1
1268 }
1269 } else {
587 $eol = quotemeta $eol unless ref $eol; 1270 $eol = quotemeta $eol unless ref $eol;
588 $eol = qr|^(.*?)($eol)|s; 1271 $eol = qr|^(.*?)($eol)|s;
1272
1273 sub {
1274 $_[0]{rbuf} =~ s/$eol// or return;
1275
1276 $cb->($_[0], $1, $2);
1277 1
1278 }
1279 }
1280};
1281
1282=item regex => $accept[, $reject[, $skip], $cb->($handle, $data)
1283
1284Makes a regex match against the regex object C<$accept> and returns
1285everything up to and including the match.
1286
1287Example: read a single line terminated by '\n'.
1288
1289 $handle->push_read (regex => qr<\n>, sub { ... });
1290
1291If C<$reject> is given and not undef, then it determines when the data is
1292to be rejected: it is matched against the data when the C<$accept> regex
1293does not match and generates an C<EBADMSG> error when it matches. This is
1294useful to quickly reject wrong data (to avoid waiting for a timeout or a
1295receive buffer overflow).
1296
1297Example: expect a single decimal number followed by whitespace, reject
1298anything else (not the use of an anchor).
1299
1300 $handle->push_read (regex => qr<^[0-9]+\s>, qr<[^0-9]>, sub { ... });
1301
1302If C<$skip> is given and not C<undef>, then it will be matched against
1303the receive buffer when neither C<$accept> nor C<$reject> match,
1304and everything preceding and including the match will be accepted
1305unconditionally. This is useful to skip large amounts of data that you
1306know cannot be matched, so that the C<$accept> or C<$reject> regex do not
1307have to start matching from the beginning. This is purely an optimisation
1308and is usually worth only when you expect more than a few kilobytes.
1309
1310Example: expect a http header, which ends at C<\015\012\015\012>. Since we
1311expect the header to be very large (it isn't in practise, but...), we use
1312a skip regex to skip initial portions. The skip regex is tricky in that
1313it only accepts something not ending in either \015 or \012, as these are
1314required for the accept regex.
1315
1316 $handle->push_read (regex =>
1317 qr<\015\012\015\012>,
1318 undef, # no reject
1319 qr<^.*[^\015\012]>,
1320 sub { ... });
1321
1322=cut
1323
1324register_read_type regex => sub {
1325 my ($self, $cb, $accept, $reject, $skip) = @_;
1326
1327 my $data;
1328 my $rbuf = \$self->{rbuf};
589 1329
590 sub { 1330 sub {
591 $_[0]{rbuf} =~ s/$eol// or return; 1331 # accept
1332 if ($$rbuf =~ $accept) {
1333 $data .= substr $$rbuf, 0, $+[0], "";
1334 $cb->($self, $data);
1335 return 1;
1336 }
1337
1338 # reject
1339 if ($reject && $$rbuf =~ $reject) {
1340 $self->_error (Errno::EBADMSG);
1341 }
592 1342
593 $cb->($_[0], $1, $2); 1343 # skip
1344 if ($skip && $$rbuf =~ $skip) {
1345 $data .= substr $$rbuf, 0, $+[0], "";
1346 }
1347
1348 ()
1349 }
1350};
1351
1352=item netstring => $cb->($handle, $string)
1353
1354A netstring (http://cr.yp.to/proto/netstrings.txt, this is not an endorsement).
1355
1356Throws an error with C<$!> set to EBADMSG on format violations.
1357
1358=cut
1359
1360register_read_type netstring => sub {
1361 my ($self, $cb) = @_;
1362
1363 sub {
1364 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) {
1365 if ($_[0]{rbuf} =~ /[^0-9]/) {
1366 $self->_error (Errno::EBADMSG);
1367 }
1368 return;
1369 }
1370
1371 my $len = $1;
1372
1373 $self->unshift_read (chunk => $len, sub {
1374 my $string = $_[1];
1375 $_[0]->unshift_read (chunk => 1, sub {
1376 if ($_[1] eq ",") {
1377 $cb->($_[0], $string);
1378 } else {
1379 $self->_error (Errno::EBADMSG);
1380 }
1381 });
1382 });
1383
594 1 1384 1
595 } 1385 }
596} 1386};
597 1387
598sub push_read_line { 1388=item packstring => $format, $cb->($handle, $string)
599 $_[0]->push_read (&_read_line);
600}
601 1389
602sub unshift_read_line { 1390An octet string prefixed with an encoded length. The encoding C<$format>
603 $_[0]->unshift_read (&_read_line); 1391uses the same format as a Perl C<pack> format, but must specify a single
604} 1392integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
1393optional C<!>, C<< < >> or C<< > >> modifier).
1394
1395For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
1396EPP uses a prefix of C<N> (4 octtes).
1397
1398Example: read a block of data prefixed by its length in BER-encoded
1399format (very efficient).
1400
1401 $handle->push_read (packstring => "w", sub {
1402 my ($handle, $data) = @_;
1403 });
1404
1405=cut
1406
1407register_read_type packstring => sub {
1408 my ($self, $cb, $format) = @_;
1409
1410 sub {
1411 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1412 defined (my $len = eval { unpack $format, $_[0]{rbuf} })
1413 or return;
1414
1415 $format = length pack $format, $len;
1416
1417 # bypass unshift if we already have the remaining chunk
1418 if ($format + $len <= length $_[0]{rbuf}) {
1419 my $data = substr $_[0]{rbuf}, $format, $len;
1420 substr $_[0]{rbuf}, 0, $format + $len, "";
1421 $cb->($_[0], $data);
1422 } else {
1423 # remove prefix
1424 substr $_[0]{rbuf}, 0, $format, "";
1425
1426 # read remaining chunk
1427 $_[0]->unshift_read (chunk => $len, $cb);
1428 }
1429
1430 1
1431 }
1432};
1433
1434=item json => $cb->($handle, $hash_or_arrayref)
1435
1436Reads a JSON object or array, decodes it and passes it to the
1437callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1438
1439If a C<json> object was passed to the constructor, then that will be used
1440for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1441
1442This read type uses the incremental parser available with JSON version
14432.09 (and JSON::XS version 2.2) and above. You have to provide a
1444dependency on your own: this module will load the JSON module, but
1445AnyEvent does not depend on it itself.
1446
1447Since JSON texts are fully self-delimiting, the C<json> read and write
1448types are an ideal simple RPC protocol: just exchange JSON datagrams. See
1449the C<json> write type description, above, for an actual example.
1450
1451=cut
1452
1453register_read_type json => sub {
1454 my ($self, $cb) = @_;
1455
1456 my $json = $self->{json} ||= json_coder;
1457
1458 my $data;
1459 my $rbuf = \$self->{rbuf};
1460
1461 sub {
1462 my $ref = eval { $json->incr_parse ($self->{rbuf}) };
1463
1464 if ($ref) {
1465 $self->{rbuf} = $json->incr_text;
1466 $json->incr_text = "";
1467 $cb->($self, $ref);
1468
1469 1
1470 } elsif ($@) {
1471 # error case
1472 $json->incr_skip;
1473
1474 $self->{rbuf} = $json->incr_text;
1475 $json->incr_text = "";
1476
1477 $self->_error (Errno::EBADMSG);
1478
1479 ()
1480 } else {
1481 $self->{rbuf} = "";
1482
1483 ()
1484 }
1485 }
1486};
1487
1488=item storable => $cb->($handle, $ref)
1489
1490Deserialises a L<Storable> frozen representation as written by the
1491C<storable> write type (BER-encoded length prefix followed by nfreeze'd
1492data).
1493
1494Raises C<EBADMSG> error if the data could not be decoded.
1495
1496=cut
1497
1498register_read_type storable => sub {
1499 my ($self, $cb) = @_;
1500
1501 require Storable;
1502
1503 sub {
1504 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1505 defined (my $len = eval { unpack "w", $_[0]{rbuf} })
1506 or return;
1507
1508 my $format = length pack "w", $len;
1509
1510 # bypass unshift if we already have the remaining chunk
1511 if ($format + $len <= length $_[0]{rbuf}) {
1512 my $data = substr $_[0]{rbuf}, $format, $len;
1513 substr $_[0]{rbuf}, 0, $format + $len, "";
1514 $cb->($_[0], Storable::thaw ($data));
1515 } else {
1516 # remove prefix
1517 substr $_[0]{rbuf}, 0, $format, "";
1518
1519 # read remaining chunk
1520 $_[0]->unshift_read (chunk => $len, sub {
1521 if (my $ref = eval { Storable::thaw ($_[1]) }) {
1522 $cb->($_[0], $ref);
1523 } else {
1524 $self->_error (Errno::EBADMSG);
1525 }
1526 });
1527 }
1528
1529 1
1530 }
1531};
1532
1533=back
1534
1535=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args)
1536
1537This function (not method) lets you add your own types to C<push_read>.
1538
1539Whenever the given C<type> is used, C<push_read> will invoke the code
1540reference with the handle object, the callback and the remaining
1541arguments.
1542
1543The code reference is supposed to return a callback (usually a closure)
1544that works as a plain read callback (see C<< ->push_read ($cb) >>).
1545
1546It should invoke the passed callback when it is done reading (remember to
1547pass C<$handle> as first argument as all other callbacks do that).
1548
1549Note that this is a function, and all types registered this way will be
1550global, so try to use unique names.
1551
1552For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>,
1553search for C<register_read_type>)).
605 1554
606=item $handle->stop_read 1555=item $handle->stop_read
607 1556
608=item $handle->start_read 1557=item $handle->start_read
609 1558
610In rare cases you actually do not want to read anything from the 1559In rare cases you actually do not want to read anything from the
611socket. In this case you can call C<stop_read>. Neither C<on_read> no 1560socket. In this case you can call C<stop_read>. Neither C<on_read> nor
612any queued callbacks will be executed then. To start reading again, call 1561any queued callbacks will be executed then. To start reading again, call
613C<start_read>. 1562C<start_read>.
614 1563
1564Note that AnyEvent::Handle will automatically C<start_read> for you when
1565you change the C<on_read> callback or push/unshift a read callback, and it
1566will automatically C<stop_read> for you when neither C<on_read> is set nor
1567there are any read requests in the queue.
1568
1569These methods will have no effect when in TLS mode (as TLS doesn't support
1570half-duplex connections).
1571
615=cut 1572=cut
616 1573
617sub stop_read { 1574sub stop_read {
618 my ($self) = @_; 1575 my ($self) = @_;
619 1576
620 delete $self->{rw}; 1577 delete $self->{_rw} unless $self->{tls};
621} 1578}
622 1579
623sub start_read { 1580sub start_read {
624 my ($self) = @_; 1581 my ($self) = @_;
625 1582
626 unless ($self->{rw} || $self->{eof}) { 1583 unless ($self->{_rw} || $self->{_eof}) {
627 Scalar::Util::weaken $self; 1584 Scalar::Util::weaken $self;
628 1585
629 $self->{rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 1586 $self->{_rw} = AE::io $self->{fh}, 0, sub {
630 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 1587 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
631 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1588 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;
632 1589
633 if ($len > 0) { 1590 if ($len > 0) {
634 $self->{filter_r} 1591 $self->{_activity} = $self->{_ractivity} = AE::now;
635 ? $self->{filter_r}->($self, $rbuf) 1592
1593 if ($self->{tls}) {
1594 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1595
1596 &_dotls ($self);
1597 } else {
636 : $self->_drain_rbuf; 1598 $self->_drain_rbuf;
1599 }
637 1600
638 } elsif (defined $len) { 1601 } elsif (defined $len) {
639 delete $self->{rw}; 1602 delete $self->{_rw};
640 $self->{eof} = 1; 1603 $self->{_eof} = 1;
641 $self->_drain_rbuf; 1604 $self->_drain_rbuf;
642 1605
643 } elsif ($! != EAGAIN && $! != EINTR) { 1606 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
644 return $self->error; 1607 return $self->_error ($!, 1);
645 } 1608 }
646 }); 1609 };
647 } 1610 }
648} 1611}
649 1612
1613our $ERROR_SYSCALL;
1614our $ERROR_WANT_READ;
1615
1616sub _tls_error {
1617 my ($self, $err) = @_;
1618
1619 return $self->_error ($!, 1)
1620 if $err == Net::SSLeay::ERROR_SYSCALL ();
1621
1622 my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
1623
1624 # reduce error string to look less scary
1625 $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
1626
1627 if ($self->{_on_starttls}) {
1628 (delete $self->{_on_starttls})->($self, undef, $err);
1629 &_freetls;
1630 } else {
1631 &_freetls;
1632 $self->_error (Errno::EPROTO, 1, $err);
1633 }
1634}
1635
1636# poll the write BIO and send the data if applicable
1637# also decode read data if possible
1638# this is basiclaly our TLS state machine
1639# more efficient implementations are possible with openssl,
1640# but not with the buggy and incomplete Net::SSLeay.
650sub _dotls { 1641sub _dotls {
651 my ($self) = @_; 1642 my ($self) = @_;
652 1643
1644 my $tmp;
1645
653 if (length $self->{tls_wbuf}) { 1646 if (length $self->{_tls_wbuf}) {
654 while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{tls_wbuf})) > 0) { 1647 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
655 substr $self->{tls_wbuf}, 0, $len, ""; 1648 substr $self->{_tls_wbuf}, 0, $tmp, "";
656 } 1649 }
657 }
658 1650
1651 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
1652 return $self->_tls_error ($tmp)
1653 if $tmp != $ERROR_WANT_READ
1654 && ($tmp != $ERROR_SYSCALL || $!);
1655 }
1656
659 if (defined (my $buf = Net::SSLeay::BIO_read ($self->{tls_wbio}))) { 1657 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1658 unless (length $tmp) {
1659 $self->{_on_starttls}
1660 and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
1661 &_freetls;
1662
1663 if ($self->{on_stoptls}) {
1664 $self->{on_stoptls}($self);
1665 return;
1666 } else {
1667 # let's treat SSL-eof as we treat normal EOF
1668 delete $self->{_rw};
1669 $self->{_eof} = 1;
1670 }
1671 }
1672
1673 $self->{_tls_rbuf} .= $tmp;
1674 $self->_drain_rbuf;
1675 $self->{tls} or return; # tls session might have gone away in callback
1676 }
1677
1678 $tmp = Net::SSLeay::get_error ($self->{tls}, -1);
1679 return $self->_tls_error ($tmp)
1680 if $tmp != $ERROR_WANT_READ
1681 && ($tmp != $ERROR_SYSCALL || $!);
1682
1683 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
660 $self->{wbuf} .= $buf; 1684 $self->{wbuf} .= $tmp;
661 $self->_drain_wbuf; 1685 $self->_drain_wbuf;
662 } 1686 }
663 1687
664 while (defined (my $buf = Net::SSLeay::read ($self->{tls}))) { 1688 $self->{_on_starttls}
665 $self->{rbuf} .= $buf; 1689 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
666 $self->_drain_rbuf; 1690 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
667 }
668
669 my $err = Net::SSLeay::get_error ($self->{tls}, -1);
670
671 if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
672 if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
673 $self->error;
674 } elsif ($err == Net::SSLeay::ERROR_SSL ()) {
675 $! = &Errno::EIO;
676 $self->error;
677 }
678
679 # all others are fine for our purposes
680 }
681} 1691}
682 1692
683=item $handle->starttls ($tls[, $tls_ctx]) 1693=item $handle->starttls ($tls[, $tls_ctx])
684 1694
685Instead of starting TLS negotiation immediately when the AnyEvent::Handle 1695Instead of starting TLS negotiation immediately when the AnyEvent::Handle
686object is created, you can also do that at a later time by calling 1696object is created, you can also do that at a later time by calling
687C<starttls>. 1697C<starttls>.
688 1698
1699Starting TLS is currently an asynchronous operation - when you push some
1700write data and then call C<< ->starttls >> then TLS negotiation will start
1701immediately, after which the queued write data is then sent.
1702
689The first argument is the same as the C<tls> constructor argument (either 1703The first argument is the same as the C<tls> constructor argument (either
690C<"connect">, C<"accept"> or an existing Net::SSLeay object). 1704C<"connect">, C<"accept"> or an existing Net::SSLeay object).
691 1705
692The second argument is the optional C<Net::SSLeay::CTX> object that is 1706The second argument is the optional C<AnyEvent::TLS> object that is used
693used when AnyEvent::Handle has to create its own TLS connection object. 1707when AnyEvent::Handle has to create its own TLS connection object, or
1708a hash reference with C<< key => value >> pairs that will be used to
1709construct a new context.
694 1710
695=cut 1711The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1712context in C<< $handle->{tls_ctx} >> after this call and can be used or
1713changed to your liking. Note that the handshake might have already started
1714when this function returns.
696 1715
697# TODO: maybe document... 1716Due to bugs in OpenSSL, it might or might not be possible to do multiple
1717handshakes on the same stream. Best do not attempt to use the stream after
1718stopping TLS.
1719
1720=cut
1721
1722our %TLS_CACHE; #TODO not yet documented, should we?
1723
698sub starttls { 1724sub starttls {
699 my ($self, $ssl, $ctx) = @_; 1725 my ($self, $tls, $ctx) = @_;
700 1726
701 $self->stoptls; 1727 Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught"
1728 if $self->{tls};
702 1729
703 if ($ssl eq "accept") { 1730 $self->{tls} = $tls;
704 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1731 $self->{tls_ctx} = $ctx if @_ > 2;
705 Net::SSLeay::set_accept_state ($ssl); 1732
706 } elsif ($ssl eq "connect") { 1733 return unless $self->{fh};
707 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1734
708 Net::SSLeay::set_connect_state ($ssl); 1735 require Net::SSLeay;
1736
1737 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1738 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1739
1740 $tls = delete $self->{tls};
1741 $ctx = $self->{tls_ctx};
1742
1743 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
1744
1745 if ("HASH" eq ref $ctx) {
1746 require AnyEvent::TLS;
1747
1748 if ($ctx->{cache}) {
1749 my $key = $ctx+0;
1750 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
1751 } else {
1752 $ctx = new AnyEvent::TLS %$ctx;
1753 }
1754 }
709 } 1755
710 1756 $self->{tls_ctx} = $ctx || TLS_CTX ();
711 $self->{tls} = $ssl; 1757 $self->{tls} = $tls = $self->{tls_ctx}->_get_session ($tls, $self, $self->{peername});
712 1758
713 # basically, this is deep magic (because SSL_read should have the same issues) 1759 # basically, this is deep magic (because SSL_read should have the same issues)
714 # but the openssl maintainers basically said: "trust us, it just works". 1760 # but the openssl maintainers basically said: "trust us, it just works".
715 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 1761 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
716 # and mismaintained ssleay-module doesn't even offer them). 1762 # and mismaintained ssleay-module doesn't even offer them).
1763 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
1764 #
1765 # in short: this is a mess.
1766 #
1767 # note that we do not try to keep the length constant between writes as we are required to do.
1768 # we assume that most (but not all) of this insanity only applies to non-blocking cases,
1769 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
1770 # have identity issues in that area.
717 Net::SSLeay::CTX_set_mode ($self->{tls}, 1771# Net::SSLeay::CTX_set_mode ($ssl,
718 (eval { Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 1772# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
719 | (eval { Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 1773# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
1774 Net::SSLeay::CTX_set_mode ($tls, 1|2);
720 1775
721 $self->{tls_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1776 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
722 $self->{tls_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1777 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
723 1778
1779 Net::SSLeay::BIO_write ($self->{_rbio}, delete $self->{rbuf});
1780
724 Net::SSLeay::set_bio ($ssl, $self->{tls_rbio}, $self->{tls_wbio}); 1781 Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});
725 1782
726 $self->{filter_w} = sub { 1783 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
727 $_[0]{tls_wbuf} .= ${$_[1]}; 1784 if $self->{on_starttls};
728 &_dotls; 1785
729 }; 1786 &_dotls; # need to trigger the initial handshake
730 $self->{filter_r} = sub { 1787 $self->start_read; # make sure we actually do read
731 Net::SSLeay::BIO_write ($_[0]{tls_rbio}, ${$_[1]});
732 &_dotls;
733 };
734} 1788}
735 1789
736=item $handle->stoptls 1790=item $handle->stoptls
737 1791
738Destroys the SSL connection, if any. Partial read or write data will be 1792Shuts down the SSL connection - this makes a proper EOF handshake by
739lost. 1793sending a close notify to the other side, but since OpenSSL doesn't
1794support non-blocking shut downs, it is not guarenteed that you can re-use
1795the stream afterwards.
740 1796
741=cut 1797=cut
742 1798
743sub stoptls { 1799sub stoptls {
744 my ($self) = @_; 1800 my ($self) = @_;
745 1801
746 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 1802 if ($self->{tls}) {
747 delete $self->{tls_rbio}; 1803 Net::SSLeay::shutdown ($self->{tls});
748 delete $self->{tls_wbio}; 1804
749 delete $self->{tls_wbuf}; 1805 &_dotls;
750 delete $self->{filter_r}; 1806
751 delete $self->{filter_w}; 1807# # we don't give a shit. no, we do, but we can't. no...#d#
1808# # we, we... have to use openssl :/#d#
1809# &_freetls;#d#
1810 }
1811}
1812
1813sub _freetls {
1814 my ($self) = @_;
1815
1816 return unless $self->{tls};
1817
1818 $self->{tls_ctx}->_put_session (delete $self->{tls})
1819 if $self->{tls} > 0;
1820
1821 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
752} 1822}
753 1823
754sub DESTROY { 1824sub DESTROY {
755 my $self = shift; 1825 my ($self) = @_;
756 1826
757 $self->stoptls; 1827 &_freetls;
1828
1829 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1830
1831 if ($linger && length $self->{wbuf} && $self->{fh}) {
1832 my $fh = delete $self->{fh};
1833 my $wbuf = delete $self->{wbuf};
1834
1835 my @linger;
1836
1837 push @linger, AE::io $fh, 1, sub {
1838 my $len = syswrite $fh, $wbuf, length $wbuf;
1839
1840 if ($len > 0) {
1841 substr $wbuf, 0, $len, "";
1842 } else {
1843 @linger = (); # end
1844 }
1845 };
1846 push @linger, AE::timer $linger, 0, sub {
1847 @linger = ();
1848 };
1849 }
1850}
1851
1852=item $handle->destroy
1853
1854Shuts down the handle object as much as possible - this call ensures that
1855no further callbacks will be invoked and as many resources as possible
1856will be freed. Any method you will call on the handle object after
1857destroying it in this way will be silently ignored (and it will return the
1858empty list).
1859
1860Normally, you can just "forget" any references to an AnyEvent::Handle
1861object and it will simply shut down. This works in fatal error and EOF
1862callbacks, as well as code outside. It does I<NOT> work in a read or write
1863callback, so when you want to destroy the AnyEvent::Handle object from
1864within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
1865that case.
1866
1867Destroying the handle object in this way has the advantage that callbacks
1868will be removed as well, so if those are the only reference holders (as
1869is common), then one doesn't need to do anything special to break any
1870reference cycles.
1871
1872The handle might still linger in the background and write out remaining
1873data, as specified by the C<linger> option, however.
1874
1875=cut
1876
1877sub destroy {
1878 my ($self) = @_;
1879
1880 $self->DESTROY;
1881 %$self = ();
1882 bless $self, "AnyEvent::Handle::destroyed";
1883}
1884
1885sub AnyEvent::Handle::destroyed::AUTOLOAD {
1886 #nop
758} 1887}
759 1888
760=item AnyEvent::Handle::TLS_CTX 1889=item AnyEvent::Handle::TLS_CTX
761 1890
762This function creates and returns the Net::SSLeay::CTX object used by 1891This function creates and returns the AnyEvent::TLS object used by default
763default for TLS mode. 1892for TLS mode.
764 1893
765The context is created like this: 1894The context is created by calling L<AnyEvent::TLS> without any arguments.
766
767 Net::SSLeay::load_error_strings;
768 Net::SSLeay::SSLeay_add_ssl_algorithms;
769 Net::SSLeay::randomize;
770
771 my $CTX = Net::SSLeay::CTX_new;
772
773 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL
774 1895
775=cut 1896=cut
776 1897
777our $TLS_CTX; 1898our $TLS_CTX;
778 1899
779sub TLS_CTX() { 1900sub TLS_CTX() {
780 $TLS_CTX || do { 1901 $TLS_CTX ||= do {
781 require Net::SSLeay; 1902 require AnyEvent::TLS;
782 1903
783 Net::SSLeay::load_error_strings (); 1904 new AnyEvent::TLS
784 Net::SSLeay::SSLeay_add_ssl_algorithms ();
785 Net::SSLeay::randomize ();
786
787 $TLS_CTX = Net::SSLeay::CTX_new ();
788
789 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ());
790
791 $TLS_CTX
792 } 1905 }
793} 1906}
794 1907
795=back 1908=back
796 1909
1910
1911=head1 NONFREQUENTLY ASKED QUESTIONS
1912
1913=over 4
1914
1915=item I C<undef> the AnyEvent::Handle reference inside my callback and
1916still get further invocations!
1917
1918That's because AnyEvent::Handle keeps a reference to itself when handling
1919read or write callbacks.
1920
1921It is only safe to "forget" the reference inside EOF or error callbacks,
1922from within all other callbacks, you need to explicitly call the C<<
1923->destroy >> method.
1924
1925=item I get different callback invocations in TLS mode/Why can't I pause
1926reading?
1927
1928Unlike, say, TCP, TLS connections do not consist of two independent
1929communication channels, one for each direction. Or put differently. The
1930read and write directions are not independent of each other: you cannot
1931write data unless you are also prepared to read, and vice versa.
1932
1933This can mean than, in TLS mode, you might get C<on_error> or C<on_eof>
1934callback invocations when you are not expecting any read data - the reason
1935is that AnyEvent::Handle always reads in TLS mode.
1936
1937During the connection, you have to make sure that you always have a
1938non-empty read-queue, or an C<on_read> watcher. At the end of the
1939connection (or when you no longer want to use it) you can call the
1940C<destroy> method.
1941
1942=item How do I read data until the other side closes the connection?
1943
1944If you just want to read your data into a perl scalar, the easiest way
1945to achieve this is by setting an C<on_read> callback that does nothing,
1946clearing the C<on_eof> callback and in the C<on_error> callback, the data
1947will be in C<$_[0]{rbuf}>:
1948
1949 $handle->on_read (sub { });
1950 $handle->on_eof (undef);
1951 $handle->on_error (sub {
1952 my $data = delete $_[0]{rbuf};
1953 });
1954
1955The reason to use C<on_error> is that TCP connections, due to latencies
1956and packets loss, might get closed quite violently with an error, when in
1957fact, all data has been received.
1958
1959It is usually better to use acknowledgements when transferring data,
1960to make sure the other side hasn't just died and you got the data
1961intact. This is also one reason why so many internet protocols have an
1962explicit QUIT command.
1963
1964=item I don't want to destroy the handle too early - how do I wait until
1965all data has been written?
1966
1967After writing your last bits of data, set the C<on_drain> callback
1968and destroy the handle in there - with the default setting of
1969C<low_water_mark> this will be called precisely when all data has been
1970written to the socket:
1971
1972 $handle->push_write (...);
1973 $handle->on_drain (sub {
1974 warn "all data submitted to the kernel\n";
1975 undef $handle;
1976 });
1977
1978If you just want to queue some data and then signal EOF to the other side,
1979consider using C<< ->push_shutdown >> instead.
1980
1981=item I want to contact a TLS/SSL server, I don't care about security.
1982
1983If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
1984simply connect to it and then create the AnyEvent::Handle with the C<tls>
1985parameter:
1986
1987 tcp_connect $host, $port, sub {
1988 my ($fh) = @_;
1989
1990 my $handle = new AnyEvent::Handle
1991 fh => $fh,
1992 tls => "connect",
1993 on_error => sub { ... };
1994
1995 $handle->push_write (...);
1996 };
1997
1998=item I want to contact a TLS/SSL server, I do care about security.
1999
2000Then you should additionally enable certificate verification, including
2001peername verification, if the protocol you use supports it (see
2002L<AnyEvent::TLS>, C<verify_peername>).
2003
2004E.g. for HTTPS:
2005
2006 tcp_connect $host, $port, sub {
2007 my ($fh) = @_;
2008
2009 my $handle = new AnyEvent::Handle
2010 fh => $fh,
2011 peername => $host,
2012 tls => "connect",
2013 tls_ctx => { verify => 1, verify_peername => "https" },
2014 ...
2015
2016Note that you must specify the hostname you connected to (or whatever
2017"peername" the protocol needs) as the C<peername> argument, otherwise no
2018peername verification will be done.
2019
2020The above will use the system-dependent default set of trusted CA
2021certificates. If you want to check against a specific CA, add the
2022C<ca_file> (or C<ca_cert>) arguments to C<tls_ctx>:
2023
2024 tls_ctx => {
2025 verify => 1,
2026 verify_peername => "https",
2027 ca_file => "my-ca-cert.pem",
2028 },
2029
2030=item I want to create a TLS/SSL server, how do I do that?
2031
2032Well, you first need to get a server certificate and key. You have
2033three options: a) ask a CA (buy one, use cacert.org etc.) b) create a
2034self-signed certificate (cheap. check the search engine of your choice,
2035there are many tutorials on the net) or c) make your own CA (tinyca2 is a
2036nice program for that purpose).
2037
2038Then create a file with your private key (in PEM format, see
2039L<AnyEvent::TLS>), followed by the certificate (also in PEM format). The
2040file should then look like this:
2041
2042 -----BEGIN RSA PRIVATE KEY-----
2043 ...header data
2044 ... lots of base64'y-stuff
2045 -----END RSA PRIVATE KEY-----
2046
2047 -----BEGIN CERTIFICATE-----
2048 ... lots of base64'y-stuff
2049 -----END CERTIFICATE-----
2050
2051The important bits are the "PRIVATE KEY" and "CERTIFICATE" parts. Then
2052specify this file as C<cert_file>:
2053
2054 tcp_server undef, $port, sub {
2055 my ($fh) = @_;
2056
2057 my $handle = new AnyEvent::Handle
2058 fh => $fh,
2059 tls => "accept",
2060 tls_ctx => { cert_file => "my-server-keycert.pem" },
2061 ...
2062
2063When you have intermediate CA certificates that your clients might not
2064know about, just append them to the C<cert_file>.
2065
2066=back
2067
2068
2069=head1 SUBCLASSING AnyEvent::Handle
2070
2071In many cases, you might want to subclass AnyEvent::Handle.
2072
2073To make this easier, a given version of AnyEvent::Handle uses these
2074conventions:
2075
2076=over 4
2077
2078=item * all constructor arguments become object members.
2079
2080At least initially, when you pass a C<tls>-argument to the constructor it
2081will end up in C<< $handle->{tls} >>. Those members might be changed or
2082mutated later on (for example C<tls> will hold the TLS connection object).
2083
2084=item * other object member names are prefixed with an C<_>.
2085
2086All object members not explicitly documented (internal use) are prefixed
2087with an underscore character, so the remaining non-C<_>-namespace is free
2088for use for subclasses.
2089
2090=item * all members not documented here and not prefixed with an underscore
2091are free to use in subclasses.
2092
2093Of course, new versions of AnyEvent::Handle may introduce more "public"
2094member variables, but thats just life, at least it is documented.
2095
2096=back
2097
797=head1 AUTHOR 2098=head1 AUTHOR
798 2099
799Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>. 2100Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>.
800 2101
801=cut 2102=cut

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines