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.35 by root, Mon May 26 05:46:35 2008 UTC vs.
Revision 1.174 by root, Sat Aug 8 20:52:06 2009 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines