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.19 by root, Sat May 24 05:57:11 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 ();
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 filehandles via AnyEvent 12AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent
16 13
17This module is experimental.
18
19=cut 14=cut
20 15
21our $VERSION = '0.04'; 16our $VERSION = 4.91;
22 17
23=head1 SYNOPSIS 18=head1 SYNOPSIS
24 19
25 use AnyEvent; 20 use AnyEvent;
26 use AnyEvent::Handle; 21 use AnyEvent::Handle;
27 22
28 my $cv = AnyEvent->condvar; 23 my $cv = AnyEvent->condvar;
29 24
30 my $ae_fh = AnyEvent::Handle->new (fh => \*STDIN); 25 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, 26 fh => \*STDIN,
39 on_eof => sub { 27 on_error => sub {
40 $cv->broadcast; 28 my ($hdl, $fatal, $msg) = @_;
41 }, 29 warn "got error $msg\n";
42 #TODO 30 $hdl->destroy;
31 $cv->send;
43 ); 32 );
44 33
45 $cv->wait; 34 # send some request line
35 $hdl->push_write ("getinfo\015\012");
36
37 # read the response line
38 $hdl->push_read (line => sub {
39 my ($hdl, $line) = @_;
40 warn "got line <$line>\n";
41 $cv->send;
42 });
43
44 $cv->recv;
46 45
47=head1 DESCRIPTION 46=head1 DESCRIPTION
48 47
49This 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
50filehandles. For utility functions for doing non-blocking connects and accepts 49filehandles.
51on sockets see L<AnyEvent::Util>. 50
51The L<AnyEvent::Intro> tutorial contains some well-documented
52AnyEvent::Handle examples.
52 53
53In the following, when the documentation refers to of "bytes" then this 54In the following, when the documentation refers to of "bytes" then this
54means 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
55treatment of characters applies to this module as well. 56treatment of characters applies to this module as well.
56 57
58At the very minimum, you should specify C<fh> or C<connect>, and the
59C<on_error> callback.
60
57All callbacks will be invoked with the handle object as their first 61All callbacks will be invoked with the handle object as their first
58argument. 62argument.
59 63
60=head1 METHODS 64=head1 METHODS
61 65
62=over 4 66=over 4
63 67
64=item B<new (%args)> 68=item $handle = B<new> AnyEvent::TLS fh => $filehandle, key => value...
65 69
66The constructor supports these arguments (all as key => value pairs). 70The constructor supports these arguments (all as C<< key => value >> pairs).
67 71
68=over 4 72=over 4
69 73
70=item fh => $filehandle [MANDATORY] 74=item fh => $filehandle [C<fh> or C<connect> MANDATORY]
71 75
72The filehandle this L<AnyEvent::Handle> object will operate on. 76The filehandle this L<AnyEvent::Handle> object will operate on.
73
74NOTE: The filehandle will be set to non-blocking (using 77NOTE: The filehandle will be set to non-blocking mode (using
75AnyEvent::Util::fh_nonblocking). 78C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in
79that mode.
76 80
77=item on_eof => $cb->($self) 81=item connect => [$host, $service] [C<fh> or C<connect> MANDATORY]
78 82
79Set 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>.
80 86
81While not mandatory, it is highly recommended to set an eof callback, 87You 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 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
85=item on_error => $cb->($self) 98=item on_prepare => $cb->($handle)
86 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
87This 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
88ocurs, such as not being able to resolve the hostname, failure to connect 139occured, such as not being able to resolve the hostname, failure to
89or a read error. 140connect or a read error.
90 141
91The 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
92called. 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>).
93 159
94On callback entrance, the value of C<$!> contains the operating system 160On callback entrance, the value of C<$!> contains the operating system
95error (or C<ENOSPC> or C<EPIPE>). 161error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
162C<EPROTO>).
96 163
97While 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
98you will not be notified of errors otherwise. The default simply calls 165you will not be notified of errors otherwise. The default simply calls
99die. 166C<croak>.
100 167
101=item on_read => $cb->($self) 168=item on_read => $cb->($handle)
102 169
103This sets the default read callback, which is called when data arrives 170This sets the default read callback, which is called when data arrives
104and 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).
105 174
106To 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 >>
107method or acces sthe 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.
108 179
109When 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
110feed 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
111calling 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
112error will be raised (with C<$!> set to C<EPIPE>). 183error will be raised (with C<$!> set to C<EPIPE>).
113 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
114=item on_drain => $cb->() 206=item on_drain => $cb->($handle)
115 207
116This 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
117(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).
118 210
119To append to the write buffer, use the C<< ->push_write >> method. 211To append to the write buffer, use the C<< ->push_write >> method.
120 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
121=item rbuf_max => <bytes> 240=item rbuf_max => <bytes>
122 241
123If 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>)
124when 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
125avoid denial-of-service attacks. 244avoid some forms of denial-of-service attacks.
126 245
127For example, a server accepting connections from untrusted sources should 246For example, a server accepting connections from untrusted sources should
128be 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
129(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
130amount 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
131isn't finished). 250isn't finished).
132 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
133=item read_size => <bytes> 278=item read_size => <bytes>
134 279
135The 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
136on each [loop iteration). Default: C<4096>. 281try to read during each loop iteration, which affects memory
282requirements). Default: C<8192>.
137 283
138=item low_water_mark => <bytes> 284=item low_water_mark => <bytes>
139 285
140Sets 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
141buffer: 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
142considered empty. 288considered empty.
143 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
144=item tls => "accept" | "connect" | Net::SSLeay::SSL object 317=item tls => "accept" | "connect" | Net::SSLeay::SSL object
145 318
146When this parameter is given, it enables TLS (SSL) mode, that means it 319When this parameter is given, it enables TLS (SSL) mode, that means
147will start making tls handshake and will transparently encrypt/decrypt 320AnyEvent will start a TLS handshake as soon as the conenction has been
148data. 321established and will transparently encrypt/decrypt data afterwards.
149 322
150For the TLS server side, use C<accept>, and for the TLS client side of a 323All TLS protocol errors will be signalled as C<EPROTO>, with an
151connection, use C<connect> mode. 324appropriate error message.
325
326TLS mode requires Net::SSLeay to be installed (it will be loaded
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.
330
331Unlike TCP, TLS has a server and client side: for the TLS server side, use
332C<accept>, and for the TLS client side of a connection, use C<connect>
333mode.
152 334
153You can also provide your own TLS connection object, but you have 335You can also provide your own TLS connection object, but you have
154to 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>
155or 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
156AnyEvent::Handle. 338AnyEvent::Handle. Also, this module will take ownership of this connection
339object.
157 340
158=item tls_ctx => $ssl_ctx 341At some future point, AnyEvent::Handle might switch to another TLS
342implementation, then the option to use your own session object will go
343away.
159 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
350See the C<< ->starttls >> method for when need to start TLS negotiation later.
351
352=item tls_ctx => $anyevent_tls
353
160Use 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
161(unless a connection object was specified directly). If this parameter is 355(unless a connection object was specified directly). If this parameter is
162missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 356missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.
163 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
164=back 405=back
165 406
166=cut 407=cut
167 408
168sub new { 409sub new {
169 my $class = shift; 410 my $class = shift;
170
171 my $self = bless { @_ }, $class; 411 my $self = bless { @_ }, $class;
172 412
173 $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) = @_;
174 476
175 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 477 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
176 478
177 if ($self->{tls}) { 479 $self->{_activity} = AnyEvent->now;
178 require Net::SSLeay; 480 $self->_timeout;
481
482 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
483
179 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}); 484 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
180 } 485 if $self->{tls};
181 486
182 $self->on_eof (delete $self->{on_eof} ) if $self->{on_eof};
183 $self->on_error (delete $self->{on_error}) if $self->{on_error};
184 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; 487 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain};
185 $self->on_read (delete $self->{on_read} ) if $self->{on_read};
186 488
187 $self->start_read; 489 $self->start_read
490 if $self->{on_read} || @{ $self->{_queue} };
188 491
189 $self 492 $self->_drain_wbuf;
190} 493}
191 494
192sub _shutdown { 495#sub _shutdown {
193 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#}
194 503
195 delete $self->{rw};
196 delete $self->{ww};
197 delete $self->{fh};
198}
199
200sub error { 504sub _error {
201 my ($self) = @_; 505 my ($self, $errno, $fatal, $message) = @_;
202 506
203 { 507 $! = $errno;
204 local $!; 508 $message ||= "$!";
205 $self->_shutdown;
206 }
207 509
208 if ($self->{on_error}) { 510 if ($self->{on_error}) {
209 $self->{on_error}($self); 511 $self->{on_error}($self, $fatal, $message);
210 } else { 512 $self->destroy if $fatal;
513 } elsif ($self->{fh}) {
514 $self->destroy;
211 die "AnyEvent::Handle uncaught fatal error: $!"; 515 Carp::croak "AnyEvent::Handle uncaught error: $message";
212 } 516 }
213} 517}
214 518
215=item $fh = $handle->fh 519=item $fh = $handle->fh
216 520
217This method returns the filehandle of the L<AnyEvent::Handle> object. 521This method returns the file handle used to create the L<AnyEvent::Handle> object.
218 522
219=cut 523=cut
220 524
221sub fh { $_[0]->{fh} } 525sub fh { $_[0]{fh} }
222 526
223=item $handle->on_error ($cb) 527=item $handle->on_error ($cb)
224 528
225Replace 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).
226 530
238 542
239sub on_eof { 543sub on_eof {
240 $_[0]{on_eof} = $_[1]; 544 $_[0]{on_eof} = $_[1];
241} 545}
242 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
243############################################################################# 673#############################################################################
244 674
245=back 675=back
246 676
247=head2 WRITE QUEUE 677=head2 WRITE QUEUE
250for reading. 680for reading.
251 681
252The write queue is very simple: you can add data to its end, and 682The write queue is very simple: you can add data to its end, and
253AnyEvent::Handle will automatically try to get rid of it for you. 683AnyEvent::Handle will automatically try to get rid of it for you.
254 684
255When data could be writtena nd the write buffer is shorter then the low 685When data could be written and the write buffer is shorter then the low
256water mark, the C<on_drain> callback will be invoked. 686water mark, the C<on_drain> callback will be invoked.
257 687
258=over 4 688=over 4
259 689
260=item $handle->on_drain ($cb) 690=item $handle->on_drain ($cb)
268 my ($self, $cb) = @_; 698 my ($self, $cb) = @_;
269 699
270 $self->{on_drain} = $cb; 700 $self->{on_drain} = $cb;
271 701
272 $cb->($self) 702 $cb->($self)
273 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 703 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
274} 704}
275 705
276=item $handle->push_write ($data) 706=item $handle->push_write ($data)
277 707
278Queues 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
282=cut 712=cut
283 713
284sub _drain_wbuf { 714sub _drain_wbuf {
285 my ($self) = @_; 715 my ($self) = @_;
286 716
287 unless ($self->{ww}) { 717 if (!$self->{_ww} && length $self->{wbuf}) {
718
288 Scalar::Util::weaken $self; 719 Scalar::Util::weaken $self;
720
289 my $cb = sub { 721 my $cb = sub {
290 my $len = syswrite $self->{fh}, $self->{wbuf}; 722 my $len = syswrite $self->{fh}, $self->{wbuf};
291 723
292 if ($len > 0) { 724 if (defined $len) {
293 substr $self->{wbuf}, 0, $len, ""; 725 substr $self->{wbuf}, 0, $len, "";
294 726
727 $self->{_activity} = AnyEvent->now;
728
295 $self->{on_drain}($self) 729 $self->{on_drain}($self)
296 if $self->{low_water_mark} >= length $self->{wbuf} 730 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
297 && $self->{on_drain}; 731 && $self->{on_drain};
298 732
299 delete $self->{ww} unless length $self->{wbuf}; 733 delete $self->{_ww} unless length $self->{wbuf};
300 } elsif ($! != EAGAIN && $! != EINTR) { 734 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
301 $self->error; 735 $self->_error ($!, 1);
302 } 736 }
303 }; 737 };
304 738
739 # try to write data immediately
740 $cb->() unless $self->{autocork};
741
742 # if still data left in wbuf, we need to poll
305 $self->{ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb); 743 $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb)
306 744 if length $self->{wbuf};
307 $cb->($self);
308 }; 745 };
746}
747
748our %WH;
749
750sub register_write_type($$) {
751 $WH{$_[0]} = $_[1];
309} 752}
310 753
311sub push_write { 754sub push_write {
312 my $self = shift; 755 my $self = shift;
313 756
757 if (@_ > 1) {
758 my $type = shift;
759
760 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write")
761 ->($self, @_);
762 }
763
314 if ($self->{filter_w}) { 764 if ($self->{tls}) {
315 $self->{filter_w}->($self, \$_[0]); 765 $self->{_tls_wbuf} .= $_[0];
766 &_dotls ($self) if $self->{fh};
316 } else { 767 } else {
317 $self->{wbuf} .= $_[0]; 768 $self->{wbuf} .= $_[0];
318 $self->_drain_wbuf; 769 $self->_drain_wbuf if $self->{fh};
319 } 770 }
320} 771}
772
773=item $handle->push_write (type => @args)
774
775Instead of formatting your data yourself, you can also let this module do
776the job by specifying a type and type-specific arguments.
777
778Predefined types are (if you have ideas for additional types, feel free to
779drop by and tell us):
780
781=over 4
782
783=item netstring => $string
784
785Formats the given value as netstring
786(http://cr.yp.to/proto/netstrings.txt, this is not a recommendation to use them).
787
788=cut
789
790register_write_type netstring => sub {
791 my ($self, $string) = @_;
792
793 (length $string) . ":$string,"
794};
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
894=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args)
895
896This function (not method) lets you add your own types to C<push_write>.
897Whenever the given C<type> is used, C<push_write> will invoke the code
898reference with the handle object and the remaining arguments.
899
900The code reference is supposed to return a single octet string that will
901be appended to the write buffer.
902
903Note that this is a function, and all types registered this way will be
904global, so try to use unique names.
905
906=cut
321 907
322############################################################################# 908#############################################################################
323 909
324=back 910=back
325 911
332ways, 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
333a queue. 919a queue.
334 920
335In 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
336new 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
337enough 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
338or not. 924leave the data there if you want to accumulate more (e.g. when only a
925partial message has been received so far).
339 926
340In 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
341case, AnyEvent::Handle will call the first queued callback each time new 928case, AnyEvent::Handle will call the first queued callback each time new
342data 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
343below). 930done its job (see C<push_read>, below).
344 931
345This 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
346a chunk of data, and AnyEvent::Handle will execute them in order. 933a chunk of data, and AnyEvent::Handle will execute them in order.
347 934
348Example 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
349the specified number of bytes which give an XML datagram. 936the specified number of bytes which give an XML datagram.
350 937
351 # in the default state, expect some header bytes 938 # in the default state, expect some header bytes
352 $handle->on_read (sub { 939 $handle->on_read (sub {
353 # 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)
354 shift->unshift_read_chunk (4, sub { 941 shift->unshift_read (chunk => 4, sub {
355 # header arrived, decode 942 # header arrived, decode
356 my $len = unpack "N", $_[1]; 943 my $len = unpack "N", $_[1];
357 944
358 # now read the payload 945 # now read the payload
359 shift->unshift_read_chunk ($len, sub { 946 shift->unshift_read (chunk => $len, sub {
360 my $xml = $_[1]; 947 my $xml = $_[1];
361 # handle xml 948 # handle xml
362 }); 949 });
363 }); 950 });
364 }); 951 });
365 952
366Example 2: Implement a client for a protocol that replies either with 953Example 2: Implement a client for a protocol that replies either with "OK"
367"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
368second 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
369pipeline sending both requests and manipulate the queue as necessary in 956just pipeline sending both requests and manipulate the queue as necessary
370the callbacks: 957in the callbacks.
371 958
372 # 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"
373 $handle->push_write ("request 1\015\012"); 964 $handle->push_write ("request 1\015\012");
374 965
375 # 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
376 $handle->push_read_line (sub { 967 $handle->push_read (line => sub {
377 # if we got an "OK", we have to _prepend_ another line, 968 # if we got an "OK", we have to _prepend_ another line,
378 # 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
379 # which are already in the queue when this callback is called 970 # which are already in the queue when this callback is called
380 # we don't do this in case we got an error 971 # we don't do this in case we got an error
381 if ($_[1] eq "OK") { 972 if ($_[1] eq "OK") {
382 $_[0]->unshift_read_line (sub { 973 $_[0]->unshift_read (line => sub {
383 my $response = $_[1]; 974 my $response = $_[1];
384 ... 975 ...
385 }); 976 });
386 } 977 }
387 }); 978 });
388 979
389 # request two 980 # request two, simply returns 64 octets
390 $handle->push_write ("request 2\015\012"); 981 $handle->push_write ("request 2\015\012");
391 982
392 # simply read 64 bytes, always 983 # simply read 64 bytes, always
393 $handle->push_read_chunk (64, sub { 984 $handle->push_read (chunk => 64, sub {
394 my $response = $_[1]; 985 my $response = $_[1];
395 ... 986 ...
396 }); 987 });
397 988
398=over 4 989=over 4
399 990
400=cut 991=cut
401 992
402sub _drain_rbuf { 993sub _drain_rbuf {
403 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 }
404 1049
405 if ( 1050 if (
406 defined $self->{rbuf_max} 1051 defined $self->{rbuf_max}
407 && $self->{rbuf_max} < length $self->{rbuf} 1052 && $self->{rbuf_max} < length $self->{rbuf}
408 ) { 1053 ) {
409 $! = &Errno::ENOSPC; return $self->error; 1054 $self->_error (Errno::ENOSPC, 1), return;
410 } 1055 }
411 1056
412 return if $self->{in_drain}; 1057 # may need to restart read watcher
413 local $self->{in_drain} = 1; 1058 unless ($self->{_rw}) {
414 1059 $self->start_read
415 while (my $len = length $self->{rbuf}) { 1060 if $self->{on_read} || @{ $self->{_queue} };
416 no strict 'refs';
417 if (my $cb = shift @{ $self->{queue} }) {
418 if (!$cb->($self)) {
419 if ($self->{eof}) {
420 # no progress can be made (not enough data and no data forthcoming)
421 $! = &Errno::EPIPE; return $self->error;
422 }
423
424 unshift @{ $self->{queue} }, $cb;
425 return;
426 }
427 } elsif ($self->{on_read}) {
428 $self->{on_read}($self);
429
430 if (
431 $self->{eof} # if no further data will arrive
432 && $len == length $self->{rbuf} # and no data has been consumed
433 && !@{ $self->{queue} } # and the queue is still empty
434 && $self->{on_read} # and we still want to read data
435 ) {
436 # then no progress can be made
437 $! = &Errno::EPIPE; return $self->error;
438 }
439 } else {
440 # read side becomes idle
441 delete $self->{rw};
442 return;
443 }
444 }
445
446 if ($self->{eof}) {
447 $self->_shutdown;
448 $self->{on_eof}($self)
449 if $self->{on_eof};
450 } 1061 }
451} 1062}
452 1063
453=item $handle->on_read ($cb) 1064=item $handle->on_read ($cb)
454 1065
460 1071
461sub on_read { 1072sub on_read {
462 my ($self, $cb) = @_; 1073 my ($self, $cb) = @_;
463 1074
464 $self->{on_read} = $cb; 1075 $self->{on_read} = $cb;
1076 $self->_drain_rbuf if $cb;
465} 1077}
466 1078
467=item $handle->rbuf 1079=item $handle->rbuf
468 1080
469Returns the read buffer (as a modifiable lvalue). 1081Returns the read buffer (as a modifiable lvalue).
470 1082
471You can access the read buffer directly as the C<< ->{rbuf} >> member, if 1083You can access the read buffer directly as the C<< ->{rbuf} >>
472you 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.
473 1088
474NOTE: 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>,
475C<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
476automatically manage the read buffer. 1091automatically manage the read buffer.
477 1092
488Append the given callback to the end of the queue (C<push_read>) or 1103Append the given callback to the end of the queue (C<push_read>) or
489prepend it (C<unshift_read>). 1104prepend it (C<unshift_read>).
490 1105
491The callback is called each time some additional read data arrives. 1106The callback is called each time some additional read data arrives.
492 1107
493It must check wether enough data is in the read buffer already. 1108It must check whether enough data is in the read buffer already.
494 1109
495If not enough data is available, it must return the empty list or a false 1110If not enough data is available, it must return the empty list or a false
496value, in which case it will be called repeatedly until enough data is 1111value, in which case it will be called repeatedly until enough data is
497available (or an error condition is detected). 1112available (or an error condition is detected).
498 1113
500interested in (which can be none at all) and return a true value. After returning 1115interested in (which can be none at all) and return a true value. After returning
501true, it will be removed from the queue. 1116true, it will be removed from the queue.
502 1117
503=cut 1118=cut
504 1119
1120our %RH;
1121
1122sub register_read_type($$) {
1123 $RH{$_[0]} = $_[1];
1124}
1125
505sub push_read { 1126sub push_read {
506 my ($self, $cb) = @_; 1127 my $self = shift;
1128 my $cb = pop;
507 1129
1130 if (@_) {
1131 my $type = shift;
1132
1133 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_read")
1134 ->($self, $cb, @_);
1135 }
1136
508 push @{ $self->{queue} }, $cb; 1137 push @{ $self->{_queue} }, $cb;
509 $self->_drain_rbuf; 1138 $self->_drain_rbuf;
510} 1139}
511 1140
512sub unshift_read { 1141sub unshift_read {
513 my ($self, $cb) = @_; 1142 my $self = shift;
1143 my $cb = pop;
514 1144
1145 if (@_) {
1146 my $type = shift;
1147
1148 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::unshift_read")
1149 ->($self, $cb, @_);
1150 }
1151
1152
515 push @{ $self->{queue} }, $cb; 1153 unshift @{ $self->{_queue} }, $cb;
516 $self->_drain_rbuf; 1154 $self->_drain_rbuf;
517} 1155}
518 1156
519=item $handle->push_read_chunk ($len, $cb->($self, $data)) 1157=item $handle->push_read (type => @args, $cb)
520 1158
521=item $handle->unshift_read_chunk ($len, $cb->($self, $data)) 1159=item $handle->unshift_read (type => @args, $cb)
522 1160
523Append the given callback to the end of the queue (C<push_read_chunk>) or 1161Instead of providing a callback that parses the data itself you can chose
524prepend it (C<unshift_read_chunk>). 1162between a number of predefined parsing formats, for chunks of data, lines
1163etc.
525 1164
526The callback will be called only once C<$len> bytes have been read, and 1165Predefined types are (if you have ideas for additional types, feel free to
527these C<$len> bytes will be passed to the callback. 1166drop by and tell us):
528 1167
529=cut 1168=over 4
530 1169
531sub _read_chunk($$) { 1170=item chunk => $octets, $cb->($handle, $data)
1171
1172Invoke the callback only once C<$octets> bytes have been read. Pass the
1173data read to the callback. The callback will never be called with less
1174data.
1175
1176Example: read 2 bytes.
1177
1178 $handle->push_read (chunk => 2, sub {
1179 warn "yay ", unpack "H*", $_[1];
1180 });
1181
1182=cut
1183
1184register_read_type chunk => sub {
532 my ($self, $len, $cb) = @_; 1185 my ($self, $cb, $len) = @_;
533 1186
534 sub { 1187 sub {
535 $len <= length $_[0]{rbuf} or return; 1188 $len <= length $_[0]{rbuf} or return;
536 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, ""); 1189 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, "");
537 1 1190 1
538 } 1191 }
539} 1192};
540 1193
541sub push_read_chunk { 1194=item line => [$eol, ]$cb->($handle, $line, $eol)
542 $_[0]->push_read (&_read_chunk);
543}
544
545
546sub unshift_read_chunk {
547 $_[0]->unshift_read (&_read_chunk);
548}
549
550=item $handle->push_read_line ([$eol, ]$cb->($self, $line, $eol))
551
552=item $handle->unshift_read_line ([$eol, ]$cb->($self, $line, $eol))
553
554Append the given callback to the end of the queue (C<push_read_line>) or
555prepend it (C<unshift_read_line>).
556 1195
557The 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
558line 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
559marker) 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
560the end of line marker as the third argument (C<$eol>). 1199the end of line marker as the third argument (C<$eol>).
571Partial lines at the end of the stream will never be returned, as they are 1210Partial lines at the end of the stream will never be returned, as they are
572not marked by the end of line marker. 1211not marked by the end of line marker.
573 1212
574=cut 1213=cut
575 1214
576sub _read_line($$) { 1215register_read_type line => sub {
577 my $self = shift; 1216 my ($self, $cb, $eol) = @_;
578 my $cb = pop;
579 my $eol = @_ ? shift : qr|(\015?\012)|;
580 my $pos;
581 1217
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 {
582 $eol = quotemeta $eol unless ref $eol; 1227 $eol = quotemeta $eol unless ref $eol;
583 $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};
584 1286
585 sub { 1287 sub {
586 $_[0]{rbuf} =~ s/$eol// or return; 1288 # accept
1289 if ($$rbuf =~ $accept) {
1290 $data .= substr $$rbuf, 0, $+[0], "";
1291 $cb->($self, $data);
1292 return 1;
1293 }
1294
1295 # reject
1296 if ($reject && $$rbuf =~ $reject) {
1297 $self->_error (Errno::EBADMSG);
1298 }
587 1299
588 $cb->($_[0], $1, $2); 1300 # skip
1301 if ($skip && $$rbuf =~ $skip) {
1302 $data .= substr $$rbuf, 0, $+[0], "";
1303 }
1304
1305 ()
1306 }
1307};
1308
1309=item netstring => $cb->($handle, $string)
1310
1311A netstring (http://cr.yp.to/proto/netstrings.txt, this is not an endorsement).
1312
1313Throws an error with C<$!> set to EBADMSG on format violations.
1314
1315=cut
1316
1317register_read_type netstring => sub {
1318 my ($self, $cb) = @_;
1319
1320 sub {
1321 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) {
1322 if ($_[0]{rbuf} =~ /[^0-9]/) {
1323 $self->_error (Errno::EBADMSG);
1324 }
1325 return;
1326 }
1327
1328 my $len = $1;
1329
1330 $self->unshift_read (chunk => $len, sub {
1331 my $string = $_[1];
1332 $_[0]->unshift_read (chunk => 1, sub {
1333 if ($_[1] eq ",") {
1334 $cb->($_[0], $string);
1335 } else {
1336 $self->_error (Errno::EBADMSG);
1337 }
1338 });
1339 });
1340
589 1 1341 1
590 } 1342 }
591} 1343};
592 1344
593sub push_read_line { 1345=item packstring => $format, $cb->($handle, $string)
594 $_[0]->push_read (&_read_line);
595}
596 1346
597sub unshift_read_line { 1347An octet string prefixed with an encoded length. The encoding C<$format>
598 $_[0]->unshift_read (&_read_line); 1348uses the same format as a Perl C<pack> format, but must specify a single
599} 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
1492=back
1493
1494=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args)
1495
1496This function (not method) lets you add your own types to C<push_read>.
1497
1498Whenever the given C<type> is used, C<push_read> will invoke the code
1499reference with the handle object, the callback and the remaining
1500arguments.
1501
1502The code reference is supposed to return a callback (usually a closure)
1503that works as a plain read callback (see C<< ->push_read ($cb) >>).
1504
1505It should invoke the passed callback when it is done reading (remember to
1506pass C<$handle> as first argument as all other callbacks do that).
1507
1508Note that this is a function, and all types registered this way will be
1509global, so try to use unique names.
1510
1511For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>,
1512search for C<register_read_type>)).
600 1513
601=item $handle->stop_read 1514=item $handle->stop_read
602 1515
603=item $handle->start_read 1516=item $handle->start_read
604 1517
605In 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
606socket. 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
607any queued callbacks will be executed then. To start readign again, call 1520any queued callbacks will be executed then. To start reading again, call
608C<start_read>. 1521C<start_read>.
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).
609 1530
610=cut 1531=cut
611 1532
612sub stop_read { 1533sub stop_read {
613 my ($self) = @_; 1534 my ($self) = @_;
614 1535
615 delete $self->{rw}; 1536 delete $self->{_rw} unless $self->{tls};
616} 1537}
617 1538
618sub start_read { 1539sub start_read {
619 my ($self) = @_; 1540 my ($self) = @_;
620 1541
621 unless ($self->{rw} || $self->{eof}) { 1542 unless ($self->{_rw} || $self->{_eof}) {
622 Scalar::Util::weaken $self; 1543 Scalar::Util::weaken $self;
623 1544
624 $self->{rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 1545 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub {
625 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 1546 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
626 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;
627 1548
628 if ($len > 0) { 1549 if ($len > 0) {
629 $self->{filter_r} 1550 $self->{_activity} = AnyEvent->now;
630 ? $self->{filter_r}->($self, $rbuf) 1551
1552 if ($self->{tls}) {
1553 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1554
1555 &_dotls ($self);
1556 } else {
631 : $self->_drain_rbuf; 1557 $self->_drain_rbuf;
1558 }
632 1559
633 } elsif (defined $len) { 1560 } elsif (defined $len) {
634 delete $self->{rw}; 1561 delete $self->{_rw};
635 $self->{eof} = 1; 1562 $self->{_eof} = 1;
636 $self->_drain_rbuf; 1563 $self->_drain_rbuf;
637 1564
638 } elsif ($! != EAGAIN && $! != EINTR) { 1565 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
639 return $self->error; 1566 return $self->_error ($!, 1);
640 } 1567 }
641 }); 1568 });
642 } 1569 }
643} 1570}
644 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.
645sub _dotls { 1600sub _dotls {
646 my ($self) = @_; 1601 my ($self) = @_;
647 1602
1603 my $tmp;
1604
648 if (length $self->{tls_wbuf}) { 1605 if (length $self->{_tls_wbuf}) {
649 my $len = Net::SSLeay::write ($self->{tls}, $self->{tls_wbuf}); 1606 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
650 substr $self->{tls_wbuf}, 0, $len, "" if $len > 0; 1607 substr $self->{_tls_wbuf}, 0, $tmp, "";
651 } 1608 }
652 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
653 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}))) {
654 $self->{wbuf} .= $buf; 1643 $self->{wbuf} .= $tmp;
655 $self->_drain_wbuf; 1644 $self->_drain_wbuf;
656 } 1645 }
657 1646
658 if (defined (my $buf = Net::SSLeay::read ($self->{tls}))) { 1647 $self->{_on_starttls}
659 $self->{rbuf} .= $buf; 1648 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
660 $self->_drain_rbuf; 1649 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
661 } elsif ( 1650}
662 (my $err = Net::SSLeay::get_error ($self->{tls}, -1)) 1651
1652=item $handle->starttls ($tls[, $tls_ctx])
1653
1654Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1655object is created, you can also do that at a later time by calling
1656C<starttls>.
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
1662The first argument is the same as the C<tls> constructor argument (either
1663C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1664
1665The second argument is the optional C<AnyEvent::TLS> object that is used
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.
1669
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.
1674
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
1683sub starttls {
1684 my ($self, $tls, $ctx) = @_;
1685
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};
1688
1689 $self->{tls} = $tls;
1690 $self->{tls_ctx} = $ctx if @_ > 2;
1691
1692 return unless $self->{fh};
1693
1694 require Net::SSLeay;
1695
1696 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
663 != Net::SSLeay::ERROR_WANT_READ () 1697 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
664 ) { 1698
665 if ($err == Net::SSLeay::ERROR_SYSCALL ()) { 1699 $tls = $self->{tls};
666 $self->error; 1700 $ctx = $self->{tls_ctx};
667 } elsif ($err == Net::SSLeay::ERROR_SSL ()) { 1701
668 $! = &Errno::EIO; 1702 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
669 $self->error; 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;
670 } 1712 }
671 1713 }
672 # all others are fine for our purposes
673 } 1714
674} 1715 $self->{tls_ctx} = $ctx || TLS_CTX ();
1716 $self->{tls} = $tls = $self->{tls_ctx}->_get_session ($tls, $self, $self->{peername});
675 1717
676# TODO: maybe document... 1718 # basically, this is deep magic (because SSL_read should have the same issues)
677sub starttls { 1719 # but the openssl maintainers basically said: "trust us, it just works".
678 my ($self, $ssl, $ctx) = @_; 1720 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
679 1721 # and mismaintained ssleay-module doesn't even offer them).
680 if ($ssl eq "accept") { 1722 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
681 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ());
682 Net::SSLeay::set_accept_state ($ssl);
683 } elsif ($ssl eq "connect") {
684 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ());
685 Net::SSLeay::set_connect_state ($ssl);
686 } 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.
1730# Net::SSLeay::CTX_set_mode ($ssl,
1731# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1732# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
1733 Net::SSLeay::CTX_set_mode ($tls, 1|2);
687 1734
688 $self->{tls} = $ssl;
689
690 $self->{tls_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1735 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
691 $self->{tls_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1736 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
692 1737
1738 Net::SSLeay::BIO_write ($self->{_rbio}, delete $self->{rbuf});
1739
693 Net::SSLeay::set_bio ($ssl, $self->{tls_rbio}, $self->{tls_wbio}); 1740 Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});
694 1741
695 $self->{filter_w} = sub { 1742 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
696 $_[0]{tls_wbuf} .= ${$_[1]}; 1743 if $self->{on_starttls};
1744
1745 &_dotls; # need to trigger the initial handshake
1746 $self->start_read; # make sure we actually do read
1747}
1748
1749=item $handle->stoptls
1750
1751Shuts down the SSL connection - this makes a proper EOF handshake by
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.
1755
1756=cut
1757
1758sub stoptls {
1759 my ($self) = @_;
1760
1761 if ($self->{tls}) {
1762 Net::SSLeay::shutdown ($self->{tls});
1763
697 &_dotls; 1764 &_dotls;
1765
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)};
1781}
1782
1783sub DESTROY {
1784 my ($self) = @_;
1785
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
1846}
1847
1848=item AnyEvent::Handle::TLS_CTX
1849
1850This function creates and returns the AnyEvent::TLS object used by default
1851for TLS mode.
1852
1853The context is created by calling L<AnyEvent::TLS> without any arguments.
1854
1855=cut
1856
1857our $TLS_CTX;
1858
1859sub TLS_CTX() {
1860 $TLS_CTX ||= do {
1861 require AnyEvent::TLS;
1862
1863 new AnyEvent::TLS
1864 }
1865}
1866
1867=back
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 (...);
698 }; 1955 };
699 $self->{filter_r} = sub {
700 Net::SSLeay::BIO_write ($_[0]{tls_rbio}, ${$_[1]});
701 &_dotls;
702 };
703}
704 1956
705sub DESTROY { 1957=item I want to contact a TLS/SSL server, I do care about security.
706 my $self = shift;
707 1958
708 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 1959Then you should additionally enable certificate verification, including
709} 1960peername verification, if the protocol you use supports it (see
1961L<AnyEvent::TLS>, C<verify_peername>).
710 1962
711=item AnyEvent::Handle::TLS_CTX 1963E.g. for HTTPS:
712 1964
713This function creates and returns the Net::SSLeay::CTX object used by 1965 tcp_connect $host, $port, sub {
714default for TLS mode. 1966 my ($fh) = @_;
715 1967
716The context is created like this: 1968 my $handle = new AnyEvent::Handle
1969 fh => $fh,
1970 peername => $host,
1971 tls => "connect",
1972 tls_ctx => { verify => 1, verify_peername => "https" },
1973 ...
717 1974
718 Net::SSLeay::load_error_strings; 1975Note that you must specify the hostname you connected to (or whatever
719 Net::SSLeay::SSLeay_add_ssl_algorithms; 1976"peername" the protocol needs) as the C<peername> argument, otherwise no
720 Net::SSLeay::randomize; 1977peername verification will be done.
721 1978
722 my $CTX = Net::SSLeay::CTX_new; 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>:
723 1982
724 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL 1983 tls_ctx => {
1984 verify => 1,
1985 verify_peername => "https",
1986 ca_file => "my-ca-cert.pem",
1987 },
725 1988
726=cut 1989=item I want to create a TLS/SSL server, how do I do that?
727 1990
728our $TLS_CTX; 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).
729 1996
730sub TLS_CTX() { 1997Then create a file with your private key (in PEM format, see
731 $TLS_CTX || do { 1998L<AnyEvent::TLS>), followed by the certificate (also in PEM format). The
732 require Net::SSLeay; 1999file should then look like this:
733 2000
734 Net::SSLeay::load_error_strings (); 2001 -----BEGIN RSA PRIVATE KEY-----
735 Net::SSLeay::SSLeay_add_ssl_algorithms (); 2002 ...header data
736 Net::SSLeay::randomize (); 2003 ... lots of base64'y-stuff
2004 -----END RSA PRIVATE KEY-----
737 2005
738 $TLS_CTX = Net::SSLeay::CTX_new (); 2006 -----BEGIN CERTIFICATE-----
2007 ... lots of base64'y-stuff
2008 -----END CERTIFICATE-----
739 2009
740 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ()); 2010The important bits are the "PRIVATE KEY" and "CERTIFICATE" parts. Then
2011specify this file as C<cert_file>:
741 2012
742 $TLS_CTX 2013 tcp_server undef, $port, sub {
743 } 2014 my ($fh) = @_;
744} 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>.
745 2024
746=back 2025=back
747 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
748=head1 AUTHOR 2057=head1 AUTHOR
749 2058
750Robin 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>.
751 2060
752=cut 2061=cut

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines