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.11 by root, Sun May 11 17:54:13 2008 UTC vs.
Revision 1.180 by root, Thu Aug 20 22:58:35 2009 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines