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.177 by root, Sun Aug 9 00:24:35 2009 UTC vs.
Revision 1.200 by root, Tue Oct 12 06:47:54 2010 UTC

1=head1 NAME 1=head1 NAME
2 2
3AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent 3AnyEvent::Handle - non-blocking I/O on streaming handles via AnyEvent
4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use AnyEvent; 7 use AnyEvent;
8 use AnyEvent::Handle; 8 use AnyEvent::Handle;
… …
14 on_error => sub { 14 on_error => sub {
15 my ($hdl, $fatal, $msg) = @_; 15 my ($hdl, $fatal, $msg) = @_;
16 warn "got error $msg\n"; 16 warn "got error $msg\n";
17 $hdl->destroy; 17 $hdl->destroy;
18 $cv->send; 18 $cv->send;
19 ); 19 };
20 20
21 # send some request line 21 # send some request line
22 $hdl->push_write ("getinfo\015\012"); 22 $hdl->push_write ("getinfo\015\012");
23 23
24 # read the response line 24 # read the response line
… …
30 30
31 $cv->recv; 31 $cv->recv;
32 32
33=head1 DESCRIPTION 33=head1 DESCRIPTION
34 34
35This module is a helper module to make it easier to do event-based I/O on 35This is a helper module to make it easier to do event-based I/O on
36filehandles. 36stream-based filehandles (sockets, pipes, and other stream things).
37 37
38The L<AnyEvent::Intro> tutorial contains some well-documented 38The L<AnyEvent::Intro> tutorial contains some well-documented
39AnyEvent::Handle examples. 39AnyEvent::Handle examples.
40 40
41In the following, when the documentation refers to of "bytes" then this 41In the following, where the documentation refers to "bytes", it means
42means characters. As sysread and syswrite are used for all I/O, their 42characters. As sysread and syswrite are used for all I/O, their
43treatment of characters applies to this module as well. 43treatment of characters applies to this module as well.
44 44
45At the very minimum, you should specify C<fh> or C<connect>, and the 45At the very minimum, you should specify C<fh> or C<connect>, and the
46C<on_error> callback. 46C<on_error> callback.
47 47
… …
60use AnyEvent (); BEGIN { AnyEvent::common_sense } 60use AnyEvent (); BEGIN { AnyEvent::common_sense }
61use AnyEvent::Util qw(WSAEWOULDBLOCK); 61use AnyEvent::Util qw(WSAEWOULDBLOCK);
62 62
63our $VERSION = $AnyEvent::VERSION; 63our $VERSION = $AnyEvent::VERSION;
64 64
65sub _load_func($) {
66 my $func = $_[0];
67
68 unless (defined &$func) {
69 my $pkg = $func;
70 do {
71 $pkg =~ s/::[^:]+$//
72 or return;
73 eval "require $pkg";
74 } until defined &$func;
75 }
76
77 \&$func
78}
79
65=head1 METHODS 80=head1 METHODS
66 81
67=over 4 82=over 4
68 83
69=item $handle = B<new> AnyEvent::TLS fh => $filehandle, key => value... 84=item $handle = B<new> AnyEvent::Handle fh => $filehandle, key => value...
70 85
71The constructor supports these arguments (all as C<< key => value >> pairs). 86The constructor supports these arguments (all as C<< key => value >> pairs).
72 87
73=over 4 88=over 4
74 89
… …
103prepare the file handle with parameters required for the actual connect 118prepare the file handle with parameters required for the actual connect
104(as opposed to settings that can be changed when the connection is already 119(as opposed to settings that can be changed when the connection is already
105established). 120established).
106 121
107The return value of this callback should be the connect timeout value in 122The 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 123seconds (or C<0>, or C<undef>, or the empty list, to indicate that the
109timeout is to be used). 124default timeout is to be used).
110 125
111=item on_connect => $cb->($handle, $host, $port, $retry->()) 126=item on_connect => $cb->($handle, $host, $port, $retry->())
112 127
113This callback is called when a connection has been successfully established. 128This callback is called when a connection has been successfully established.
114 129
115The actual numeric host and port (the socket peername) are passed as 130The peer's numeric host and port (the socket peername) are passed as
116parameters, together with a retry callback. 131parameters, together with a retry callback.
117 132
118When, for some reason, the handle is not acceptable, then calling 133If, for some reason, the handle is not acceptable, calling C<$retry>
119C<$retry> will continue with the next conenction target (in case of 134will continue with the next connection target (in case of multi-homed
120multi-homed hosts or SRV records there can be multiple connection 135hosts or SRV records there can be multiple connection endpoints). At the
121endpoints). When it is called then the read and write queues, eof status, 136time it is called the read and write queues, eof status, tls status and
122tls status and similar properties of the handle are being reset. 137similar properties of the handle will have been reset.
123 138
124In most cases, ignoring the C<$retry> parameter is the way to go. 139In most cases, you should ignore the C<$retry> parameter.
125 140
126=item on_connect_error => $cb->($handle, $message) 141=item on_connect_error => $cb->($handle, $message)
127 142
128This callback is called when the conenction could not be 143This callback is called when the connection could not be
129established. C<$!> will contain the relevant error code, and C<$message> a 144established. C<$!> will contain the relevant error code, and C<$message> a
130message describing it (usually the same as C<"$!">). 145message describing it (usually the same as C<"$!">).
131 146
132If this callback isn't specified, then C<on_error> will be called with a 147If this callback isn't specified, then C<on_error> will be called with a
133fatal error instead. 148fatal error instead.
… …
136 151
137=item on_error => $cb->($handle, $fatal, $message) 152=item on_error => $cb->($handle, $fatal, $message)
138 153
139This is the error callback, which is called when, well, some error 154This is the error callback, which is called when, well, some error
140occured, such as not being able to resolve the hostname, failure to 155occured, such as not being able to resolve the hostname, failure to
141connect or a read error. 156connect, or a read error.
142 157
143Some errors are fatal (which is indicated by C<$fatal> being true). On 158Some errors are fatal (which is indicated by C<$fatal> being true). On
144fatal errors the handle object will be destroyed (by a call to C<< -> 159fatal errors the handle object will be destroyed (by a call to C<< ->
145destroy >>) after invoking the error callback (which means you are free to 160destroy >>) after invoking the error callback (which means you are free to
146examine the handle object). Examples of fatal errors are an EOF condition 161examine the handle object). Examples of fatal errors are an EOF condition
147with active (but unsatisifable) read watchers (C<EPIPE>) or I/O errors. In 162with 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 163cases where the other side can close the connection at will, it is
149often easiest to not report C<EPIPE> errors in this callback. 164often easiest to not report C<EPIPE> errors in this callback.
150 165
151AnyEvent::Handle tries to find an appropriate error code for you to check 166AnyEvent::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 167against, but in some cases (TLS errors), this does not work well. It is
153recommended to always output the C<$message> argument in human-readable 168recommended to always output the C<$message> argument in human-readable
154error messages (it's usually the same as C<"$!">). 169error messages (it's usually the same as C<"$!">).
155 170
156Non-fatal errors can be retried by simply returning, but it is recommended 171Non-fatal errors can be retried by returning, but it is recommended
157to simply ignore this parameter and instead abondon the handle object 172to simply ignore this parameter and instead abondon the handle object
158when this callback is invoked. Examples of non-fatal errors are timeouts 173when this callback is invoked. Examples of non-fatal errors are timeouts
159C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>). 174C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
160 175
161On callback entrance, the value of C<$!> contains the operating system 176On entry to the callback, the value of C<$!> contains the operating
162error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or 177system error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
163C<EPROTO>). 178C<EPROTO>).
164 179
165While not mandatory, it is I<highly> recommended to set this callback, as 180While not mandatory, it is I<highly> recommended to set this callback, as
166you will not be notified of errors otherwise. The default simply calls 181you will not be notified of errors otherwise. The default just calls
167C<croak>. 182C<croak>.
168 183
169=item on_read => $cb->($handle) 184=item on_read => $cb->($handle)
170 185
171This sets the default read callback, which is called when data arrives 186This sets the default read callback, which is called when data arrives
… …
176To access (and remove data from) the read buffer, use the C<< ->rbuf >> 191To access (and remove data from) the read buffer, use the C<< ->rbuf >>
177method or access the C<< $handle->{rbuf} >> member directly. Note that you 192method 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 193must not enlarge or modify the read buffer, you can only remove data at
179the beginning from it. 194the beginning from it.
180 195
196You can also call C<< ->push_read (...) >> or any other function that
197modifies the read queue. Or do both. Or ...
198
181When an EOF condition is detected then AnyEvent::Handle will first try to 199When an EOF condition is detected, AnyEvent::Handle will first try to
182feed all the remaining data to the queued callbacks and C<on_read> before 200feed all the remaining data to the queued callbacks and C<on_read> before
183calling the C<on_eof> callback. If no progress can be made, then a fatal 201calling the C<on_eof> callback. If no progress can be made, then a fatal
184error will be raised (with C<$!> set to C<EPIPE>). 202error will be raised (with C<$!> set to C<EPIPE>).
185 203
186Note that, unlike requests in the read queue, an C<on_read> callback 204Note that, unlike requests in the read queue, an C<on_read> callback
… …
205set, then a fatal error will be raised with C<$!> set to <0>. 223set, then a fatal error will be raised with C<$!> set to <0>.
206 224
207=item on_drain => $cb->($handle) 225=item on_drain => $cb->($handle)
208 226
209This sets the callback that is called when the write buffer becomes empty 227This sets the callback that is called when the write buffer becomes empty
210(or when the callback is set and the buffer is empty already). 228(or immediately if the buffer is empty already).
211 229
212To append to the write buffer, use the C<< ->push_write >> method. 230To append to the write buffer, use the C<< ->push_write >> method.
213 231
214This callback is useful when you don't want to put all of your write data 232This 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 233into the queue at once, for example, when you want to write the contents
… …
227many seconds pass without a successful read or write on the underlying 245many 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 246file 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> 247will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>
230error will be raised). 248error will be raised).
231 249
232There are three variants of the timeouts that work fully independent 250There are three variants of the timeouts that work independently
233of each other, for both read and write, just read, and just write: 251of each other, for both read and write, just read, and just write:
234C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks 252C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks
235C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions 253C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions
236C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>. 254C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>.
237 255
238Note that timeout processing is also active when you currently do not have 256Note that timeout processing is active even when you do not have
239any outstanding read or write requests: If you plan to keep the connection 257any outstanding read or write requests: If you plan to keep the connection
240idle then you should disable the timout temporarily or ignore the timeout 258idle then you should disable the timeout temporarily or ignore the timeout
241in the C<on_timeout> callback, in which case AnyEvent::Handle will simply 259in the C<on_timeout> callback, in which case AnyEvent::Handle will simply
242restart the timeout. 260restart the timeout.
243 261
244Zero (the default) disables this timeout. 262Zero (the default) disables this timeout.
245 263
… …
261amount of data without a callback ever being called as long as the line 279amount of data without a callback ever being called as long as the line
262isn't finished). 280isn't finished).
263 281
264=item autocork => <boolean> 282=item autocork => <boolean>
265 283
266When disabled (the default), then C<push_write> will try to immediately 284When disabled (the default), C<push_write> will try to immediately
267write the data to the handle, if possible. This avoids having to register 285write 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 286a write watcher and wait for the next event loop iteration, but can
269be inefficient if you write multiple small chunks (on the wire, this 287be inefficient if you write multiple small chunks (on the wire, this
270disadvantage is usually avoided by your kernel's nagle algorithm, see 288disadvantage is usually avoided by your kernel's nagle algorithm, see
271C<no_delay>, but this option can save costly syscalls). 289C<no_delay>, but this option can save costly syscalls).
272 290
273When enabled, then writes will always be queued till the next event loop 291When enabled, writes will always be queued till the next event loop
274iteration. This is efficient when you do many small writes per iteration, 292iteration. 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 293but less efficient when you do a single write only per iteration (or when
276the write buffer often is full). It also increases write latency. 294the write buffer often is full). It also increases write latency.
277 295
278=item no_delay => <boolean> 296=item no_delay => <boolean>
… …
282the Nagle algorithm, and usually it is beneficial. 300the Nagle algorithm, and usually it is beneficial.
283 301
284In some situations you want as low a delay as possible, which can be 302In some situations you want as low a delay as possible, which can be
285accomplishd by setting this option to a true value. 303accomplishd by setting this option to a true value.
286 304
287The default is your opertaing system's default behaviour (most likely 305The default is your operating system's default behaviour (most likely
288enabled), this option explicitly enables or disables it, if possible. 306enabled). This option explicitly enables or disables it, if possible.
307
308=item keepalive => <boolean>
309
310Enables (default disable) the SO_KEEPALIVE option on the stream socket:
311normally, TCP connections have no time-out once established, so TCP
312connections, once established, can stay alive forever even when the other
313side has long gone. TCP keepalives are a cheap way to take down long-lived
314TCP connections when the other side becomes unreachable. While the default
315is OS-dependent, TCP keepalives usually kick in after around two hours,
316and, if the other side doesn't reply, take down the TCP connection some 10
317to 15 minutes later.
318
319It is harmless to specify this option for file handles that do not support
320keepalives, and enabling it on connections that are potentially long-lived
321is usually a good idea.
322
323=item oobinline => <boolean>
324
325BSD majorly fucked up the implementation of TCP urgent data. The result
326is that almost no OS implements TCP according to the specs, and every OS
327implements it slightly differently.
328
329If you want to handle TCP urgent data, then setting this flag (the default
330is enabled) gives you the most portable way of getting urgent data, by
331putting it into the stream.
332
333Since BSD emulation of OOB data on top of TCP's urgent data can have
334security implications, AnyEvent::Handle sets this flag automatically
335unless explicitly specified. Note that setting this flag after
336establishing a connection I<may> be a bit too late (data loss could
337already have occured on BSD systems), but at least it will protect you
338from most attacks.
289 339
290=item read_size => <bytes> 340=item read_size => <bytes>
291 341
292The default read block size (the amount of bytes this module will 342The default read block size (the number of bytes this module will
293try to read during each loop iteration, which affects memory 343try to read during each loop iteration, which affects memory
294requirements). Default: C<8192>. 344requirements). Default: C<8192>.
295 345
296=item low_water_mark => <bytes> 346=item low_water_mark => <bytes>
297 347
298Sets the amount of bytes (default: C<0>) that make up an "empty" write 348Sets the number of bytes (default: C<0>) that make up an "empty" write
299buffer: If the write reaches this size or gets even samller it is 349buffer: If the buffer reaches this size or gets even samller it is
300considered empty. 350considered empty.
301 351
302Sometimes it can be beneficial (for performance reasons) to add data to 352Sometimes 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 353the 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 354the operating system kernel usually buffers data as well, so the default
305is good in almost all cases. 355is good in almost all cases.
306 356
307=item linger => <seconds> 357=item linger => <seconds>
308 358
309If non-zero (default: C<3600>), then the destructor of the 359If this is non-zero (default: C<3600>), the destructor of the
310AnyEvent::Handle object will check whether there is still outstanding 360AnyEvent::Handle object will check whether there is still outstanding
311write data and will install a watcher that will write this data to the 361write 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 362socket. No errors will be reported (this mostly matches how the operating
313system treats outstanding data at socket close time). 363system treats outstanding data at socket close time).
314 364
… …
321A string used to identify the remote site - usually the DNS hostname 371A string used to identify the remote site - usually the DNS hostname
322(I<not> IDN!) used to create the connection, rarely the IP address. 372(I<not> IDN!) used to create the connection, rarely the IP address.
323 373
324Apart from being useful in error messages, this string is also used in TLS 374Apart from being useful in error messages, this string is also used in TLS
325peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This 375peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
326verification will be skipped when C<peername> is not specified or 376verification will be skipped when C<peername> is not specified or is
327C<undef>. 377C<undef>.
328 378
329=item tls => "accept" | "connect" | Net::SSLeay::SSL object 379=item tls => "accept" | "connect" | Net::SSLeay::SSL object
330 380
331When this parameter is given, it enables TLS (SSL) mode, that means 381When this parameter is given, it enables TLS (SSL) mode, that means
332AnyEvent will start a TLS handshake as soon as the conenction has been 382AnyEvent will start a TLS handshake as soon as the connection has been
333established and will transparently encrypt/decrypt data afterwards. 383established and will transparently encrypt/decrypt data afterwards.
334 384
335All TLS protocol errors will be signalled as C<EPROTO>, with an 385All TLS protocol errors will be signalled as C<EPROTO>, with an
336appropriate error message. 386appropriate error message.
337 387
… …
357B<IMPORTANT:> since Net::SSLeay "objects" are really only integers, 407B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
358passing in the wrong integer will lead to certain crash. This most often 408passing 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 409happens when one uses a stylish C<< tls => 1 >> and is surprised about the
360segmentation fault. 410segmentation fault.
361 411
362See the C<< ->starttls >> method for when need to start TLS negotiation later. 412Use the C<< ->starttls >> method if you need to start TLS negotiation later.
363 413
364=item tls_ctx => $anyevent_tls 414=item tls_ctx => $anyevent_tls
365 415
366Use the given C<AnyEvent::TLS> object to create the new TLS connection 416Use the given C<AnyEvent::TLS> object to create the new TLS connection
367(unless a connection object was specified directly). If this parameter is 417(unless a connection object was specified directly). If this parameter is
… …
382 432
383TLS handshake failures will not cause C<on_error> to be invoked when this 433TLS 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>. 434callback is in effect, instead, the error message will be passed to C<on_starttls>.
385 435
386Without this callback, handshake failures lead to C<on_error> being 436Without this callback, handshake failures lead to C<on_error> being
387called, as normal. 437called as usual.
388 438
389Note that you cannot call C<starttls> right again in this callback. If you 439Note that you cannot just call C<starttls> again in this callback. If you
390need to do that, start an zero-second timer instead whose callback can 440need to do that, start an zero-second timer instead whose callback can
391then call C<< ->starttls >> again. 441then call C<< ->starttls >> again.
392 442
393=item on_stoptls => $cb->($handle) 443=item on_stoptls => $cb->($handle)
394 444
… …
450 delete $self->{_skip_drain_rbuf}; 500 delete $self->{_skip_drain_rbuf};
451 $self->_start; 501 $self->_start;
452 502
453 $self->{on_connect} 503 $self->{on_connect}
454 and $self->{on_connect}($self, $host, $port, sub { 504 and $self->{on_connect}($self, $host, $port, sub {
455 delete @$self{qw(fh _tw _ww _rw _eof _queue rbuf _wbuf tls _tls_rbuf _tls_wbuf)}; 505 delete @$self{qw(fh _tw _rtw _wtw _ww _rw _eof _queue rbuf _wbuf tls _tls_rbuf _tls_wbuf)};
456 $self->{_skip_drain_rbuf} = 1; 506 $self->{_skip_drain_rbuf} = 1;
457 &$retry; 507 &$retry;
458 }); 508 });
459 509
460 } else { 510 } else {
… …
484} 534}
485 535
486sub _start { 536sub _start {
487 my ($self) = @_; 537 my ($self) = @_;
488 538
539 # too many clueless people try to use udp and similar sockets
540 # with AnyEvent::Handle, do them a favour.
541 my $type = getsockopt $self->{fh}, Socket::SOL_SOCKET (), Socket::SO_TYPE ();
542 Carp::croak "AnyEvent::Handle: only stream sockets supported, anything else will NOT work!"
543 if Socket::SOCK_STREAM () != (unpack "I", $type) && defined $type;
544
489 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 545 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
490 546
491 $self->{_activity} = 547 $self->{_activity} =
492 $self->{_ractivity} = 548 $self->{_ractivity} =
493 $self->{_wactivity} = AE::now; 549 $self->{_wactivity} = AE::now;
494 550
495 $self->timeout (delete $self->{timeout} ) if $self->{timeout}; 551 $self->timeout (delete $self->{timeout} ) if $self->{timeout};
496 $self->rtimeout (delete $self->{rtimeout}) if $self->{rtimeout}; 552 $self->rtimeout (delete $self->{rtimeout} ) if $self->{rtimeout};
497 $self->wtimeout (delete $self->{wtimeout}) if $self->{wtimeout}; 553 $self->wtimeout (delete $self->{wtimeout} ) if $self->{wtimeout};
498 554
499 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay}; 555 $self->no_delay (delete $self->{no_delay} ) if exists $self->{no_delay} && $self->{no_delay};
556 $self->keepalive (delete $self->{keepalive}) if exists $self->{keepalive} && $self->{keepalive};
500 557
558 $self->oobinline (exists $self->{oobinline} ? delete $self->{oobinline} : 1);
559
501 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}) 560 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
502 if $self->{tls}; 561 if $self->{tls};
503 562
504 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; 563 $self->on_drain (delete $self->{on_drain} ) if $self->{on_drain};
505 564
506 $self->start_read 565 $self->start_read
507 if $self->{on_read} || @{ $self->{_queue} }; 566 if $self->{on_read} || @{ $self->{_queue} };
508 567
509 $self->_drain_wbuf; 568 $self->_drain_wbuf;
510} 569}
511
512#sub _shutdown {
513# my ($self) = @_;
514#
515# delete @$self{qw(_tw _rw _ww fh wbuf on_read _queue)};
516# $self->{_eof} = 1; # tell starttls et. al to stop trying
517#
518# &_freetls;
519#}
520 570
521sub _error { 571sub _error {
522 my ($self, $errno, $fatal, $message) = @_; 572 my ($self, $errno, $fatal, $message) = @_;
523 573
524 $! = $errno; 574 $! = $errno;
525 $message ||= "$!"; 575 $message ||= "$!";
526 576
527 if ($self->{on_error}) { 577 if ($self->{on_error}) {
528 $self->{on_error}($self, $fatal, $message); 578 $self->{on_error}($self, $fatal, $message);
529 $self->destroy if $fatal; 579 $self->destroy if $fatal;
530 } elsif ($self->{fh}) { 580 } elsif ($self->{fh} || $self->{connect}) {
531 $self->destroy; 581 $self->destroy;
532 Carp::croak "AnyEvent::Handle uncaught error: $message"; 582 Carp::croak "AnyEvent::Handle uncaught error: $message";
533 } 583 }
534} 584}
535 585
… …
594=cut 644=cut
595 645
596sub no_delay { 646sub no_delay {
597 $_[0]{no_delay} = $_[1]; 647 $_[0]{no_delay} = $_[1];
598 648
649 setsockopt $_[0]{fh}, Socket::IPPROTO_TCP (), Socket::TCP_NODELAY (), int $_[1]
650 if $_[0]{fh};
651}
652
653=item $handle->keepalive ($boolean)
654
655Enables or disables the C<keepalive> setting (see constructor argument of
656the same name for details).
657
658=cut
659
660sub keepalive {
661 $_[0]{keepalive} = $_[1];
662
599 eval { 663 eval {
600 local $SIG{__DIE__}; 664 local $SIG{__DIE__};
601 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1] 665 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
602 if $_[0]{fh}; 666 if $_[0]{fh};
603 }; 667 };
604} 668}
605 669
670=item $handle->oobinline ($boolean)
671
672Enables or disables the C<oobinline> setting (see constructor argument of
673the same name for details).
674
675=cut
676
677sub oobinline {
678 $_[0]{oobinline} = $_[1];
679
680 eval {
681 local $SIG{__DIE__};
682 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_OOBINLINE (), int $_[1]
683 if $_[0]{fh};
684 };
685}
686
687=item $handle->keepalive ($boolean)
688
689Enables or disables the C<keepalive> setting (see constructor argument of
690the same name for details).
691
692=cut
693
694sub keepalive {
695 $_[0]{keepalive} = $_[1];
696
697 eval {
698 local $SIG{__DIE__};
699 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
700 if $_[0]{fh};
701 };
702}
703
606=item $handle->on_starttls ($cb) 704=item $handle->on_starttls ($cb)
607 705
608Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument). 706Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument).
609 707
610=cut 708=cut
… …
617 715
618Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument). 716Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
619 717
620=cut 718=cut
621 719
622sub on_starttls { 720sub on_stoptls {
623 $_[0]{on_stoptls} = $_[1]; 721 $_[0]{on_stoptls} = $_[1];
624} 722}
625 723
626=item $handle->rbuf_max ($max_octets) 724=item $handle->rbuf_max ($max_octets)
627 725
… …
739=item $handle->on_drain ($cb) 837=item $handle->on_drain ($cb)
740 838
741Sets the C<on_drain> callback or clears it (see the description of 839Sets the C<on_drain> callback or clears it (see the description of
742C<on_drain> in the constructor). 840C<on_drain> in the constructor).
743 841
842This method may invoke callbacks (and therefore the handle might be
843destroyed after it returns).
844
744=cut 845=cut
745 846
746sub on_drain { 847sub on_drain {
747 my ($self, $cb) = @_; 848 my ($self, $cb) = @_;
748 849
… …
755=item $handle->push_write ($data) 856=item $handle->push_write ($data)
756 857
757Queues the given scalar to be written. You can push as much data as you 858Queues the given scalar to be written. You can push as much data as you
758want (only limited by the available memory), as C<AnyEvent::Handle> 859want (only limited by the available memory), as C<AnyEvent::Handle>
759buffers it independently of the kernel. 860buffers it independently of the kernel.
861
862This method may invoke callbacks (and therefore the handle might be
863destroyed after it returns).
760 864
761=cut 865=cut
762 866
763sub _drain_wbuf { 867sub _drain_wbuf {
764 my ($self) = @_; 868 my ($self) = @_;
… …
794 }; 898 };
795} 899}
796 900
797our %WH; 901our %WH;
798 902
903# deprecated
799sub register_write_type($$) { 904sub register_write_type($$) {
800 $WH{$_[0]} = $_[1]; 905 $WH{$_[0]} = $_[1];
801} 906}
802 907
803sub push_write { 908sub push_write {
804 my $self = shift; 909 my $self = shift;
805 910
806 if (@_ > 1) { 911 if (@_ > 1) {
807 my $type = shift; 912 my $type = shift;
808 913
914 @_ = ($WH{$type} ||= _load_func "$type\::anyevent_write_type"
809 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 915 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_write")
810 ->($self, @_); 916 ->($self, @_);
811 } 917 }
812 918
919 # we downgrade here to avoid hard-to-track-down bugs,
920 # and diagnose the problem earlier and better.
921
813 if ($self->{tls}) { 922 if ($self->{tls}) {
814 $self->{_tls_wbuf} .= $_[0]; 923 utf8::downgrade $self->{_tls_wbuf} .= $_[0];
815 &_dotls ($self) if $self->{fh}; 924 &_dotls ($self) if $self->{fh};
816 } else { 925 } else {
817 $self->{wbuf} .= $_[0]; 926 utf8::downgrade $self->{wbuf} .= $_[0];
818 $self->_drain_wbuf if $self->{fh}; 927 $self->_drain_wbuf if $self->{fh};
819 } 928 }
820} 929}
821 930
822=item $handle->push_write (type => @args) 931=item $handle->push_write (type => @args)
823 932
824Instead of formatting your data yourself, you can also let this module do 933Instead of formatting your data yourself, you can also let this module
825the job by specifying a type and type-specific arguments. 934do the job by specifying a type and type-specific arguments. You
935can also specify the (fully qualified) name of a package, in which
936case AnyEvent tries to load the package and then expects to find the
937C<anyevent_write_type> function inside (see "custom write types", below).
826 938
827Predefined types are (if you have ideas for additional types, feel free to 939Predefined types are (if you have ideas for additional types, feel free to
828drop by and tell us): 940drop by and tell us):
829 941
830=over 4 942=over 4
… …
887Other languages could read single lines terminated by a newline and pass 999Other languages could read single lines terminated by a newline and pass
888this line into their JSON decoder of choice. 1000this line into their JSON decoder of choice.
889 1001
890=cut 1002=cut
891 1003
1004sub json_coder() {
1005 eval { require JSON::XS; JSON::XS->new->utf8 }
1006 || do { require JSON; JSON->new->utf8 }
1007}
1008
892register_write_type json => sub { 1009register_write_type json => sub {
893 my ($self, $ref) = @_; 1010 my ($self, $ref) = @_;
894 1011
895 require JSON; 1012 my $json = $self->{json} ||= json_coder;
896 1013
897 $self->{json} ? $self->{json}->encode ($ref) 1014 $json->encode ($ref)
898 : JSON::encode_json ($ref)
899}; 1015};
900 1016
901=item storable => $reference 1017=item storable => $reference
902 1018
903Freezes the given reference using L<Storable> and writes it to the 1019Freezes the given reference using L<Storable> and writes it to the
… …
929the peer. 1045the peer.
930 1046
931You can rely on the normal read queue and C<on_eof> handling 1047You can rely on the normal read queue and C<on_eof> handling
932afterwards. This is the cleanest way to close a connection. 1048afterwards. This is the cleanest way to close a connection.
933 1049
1050This method may invoke callbacks (and therefore the handle might be
1051destroyed after it returns).
1052
934=cut 1053=cut
935 1054
936sub push_shutdown { 1055sub push_shutdown {
937 my ($self) = @_; 1056 my ($self) = @_;
938 1057
939 delete $self->{low_water_mark}; 1058 delete $self->{low_water_mark};
940 $self->on_drain (sub { shutdown $_[0]{fh}, 1 }); 1059 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
941} 1060}
942 1061
943=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 1062=item custom write types - Package::anyevent_write_type $handle, @args
944 1063
945This function (not method) lets you add your own types to C<push_write>. 1064Instead of one of the predefined types, you can also specify the name of
1065a package. AnyEvent will try to load the package and then expects to find
1066a function named C<anyevent_write_type> inside. If it isn't found, it
1067progressively tries to load the parent package until it either finds the
1068function (good) or runs out of packages (bad).
1069
946Whenever the given C<type> is used, C<push_write> will invoke the code 1070Whenever the given C<type> is used, C<push_write> will the function with
947reference with the handle object and the remaining arguments. 1071the handle object and the remaining arguments.
948 1072
949The code reference is supposed to return a single octet string that will 1073The function is supposed to return a single octet string that will be
950be appended to the write buffer. 1074appended to the write buffer, so you cna mentally treat this function as a
1075"arguments to on-the-wire-format" converter.
951 1076
952Note that this is a function, and all types registered this way will be 1077Example: implement a custom write type C<join> that joins the remaining
953global, so try to use unique names. 1078arguments using the first one.
1079
1080 $handle->push_write (My::Type => " ", 1,2,3);
1081
1082 # uses the following package, which can be defined in the "My::Type" or in
1083 # the "My" modules to be auto-loaded, or just about anywhere when the
1084 # My::Type::anyevent_write_type is defined before invoking it.
1085
1086 package My::Type;
1087
1088 sub anyevent_write_type {
1089 my ($handle, $delim, @args) = @_;
1090
1091 join $delim, @args
1092 }
954 1093
955=cut 1094=cut
956 1095
957############################################################################# 1096#############################################################################
958 1097
… …
967ways, the "simple" way, using only C<on_read> and the "complex" way, using 1106ways, the "simple" way, using only C<on_read> and the "complex" way, using
968a queue. 1107a queue.
969 1108
970In the simple case, you just install an C<on_read> callback and whenever 1109In the simple case, you just install an C<on_read> callback and whenever
971new data arrives, it will be called. You can then remove some data (if 1110new data arrives, it will be called. You can then remove some data (if
972enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna 1111enough is there) from the read buffer (C<< $handle->rbuf >>). Or you can
973leave the data there if you want to accumulate more (e.g. when only a 1112leave the data there if you want to accumulate more (e.g. when only a
974partial message has been received so far). 1113partial message has been received so far), or change the read queue with
1114e.g. C<push_read>.
975 1115
976In the more complex case, you want to queue multiple callbacks. In this 1116In the more complex case, you want to queue multiple callbacks. In this
977case, AnyEvent::Handle will call the first queued callback each time new 1117case, AnyEvent::Handle will call the first queued callback each time new
978data arrives (also the first time it is queued) and removes it when it has 1118data arrives (also the first time it is queued) and remove it when it has
979done its job (see C<push_read>, below). 1119done its job (see C<push_read>, below).
980 1120
981This way you can, for example, push three line-reads, followed by reading 1121This way you can, for example, push three line-reads, followed by reading
982a chunk of data, and AnyEvent::Handle will execute them in order. 1122a chunk of data, and AnyEvent::Handle will execute them in order.
983 1123
… …
1114 1254
1115This replaces the currently set C<on_read> callback, or clears it (when 1255This replaces the currently set C<on_read> callback, or clears it (when
1116the new callback is C<undef>). See the description of C<on_read> in the 1256the new callback is C<undef>). See the description of C<on_read> in the
1117constructor. 1257constructor.
1118 1258
1259This method may invoke callbacks (and therefore the handle might be
1260destroyed after it returns).
1261
1119=cut 1262=cut
1120 1263
1121sub on_read { 1264sub on_read {
1122 my ($self, $cb) = @_; 1265 my ($self, $cb) = @_;
1123 1266
… …
1125 $self->_drain_rbuf if $cb; 1268 $self->_drain_rbuf if $cb;
1126} 1269}
1127 1270
1128=item $handle->rbuf 1271=item $handle->rbuf
1129 1272
1130Returns the read buffer (as a modifiable lvalue). 1273Returns the read buffer (as a modifiable lvalue). You can also access the
1274read buffer directly as the C<< ->{rbuf} >> member, if you want (this is
1275much faster, and no less clean).
1131 1276
1132You can access the read buffer directly as the C<< ->{rbuf} >> 1277The only operation allowed on the read buffer (apart from looking at it)
1133member, if you want. However, the only operation allowed on the 1278is removing data from its beginning. Otherwise modifying or appending to
1134read buffer (apart from looking at it) is removing data from its 1279it is not allowed and will lead to hard-to-track-down bugs.
1135beginning. Otherwise modifying or appending to it is not allowed and will
1136lead to hard-to-track-down bugs.
1137 1280
1138NOTE: The read buffer should only be used or modified if the C<on_read>, 1281NOTE: The read buffer should only be used or modified in the C<on_read>
1139C<push_read> or C<unshift_read> methods are used. The other read methods 1282callback or when C<push_read> or C<unshift_read> are used with a single
1140automatically manage the read buffer. 1283callback (i.e. untyped). Typed C<push_read> and C<unshift_read> methods
1284will manage the read buffer on their own.
1141 1285
1142=cut 1286=cut
1143 1287
1144sub rbuf : lvalue { 1288sub rbuf : lvalue {
1145 $_[0]{rbuf} 1289 $_[0]{rbuf}
… …
1162 1306
1163If enough data was available, then the callback must remove all data it is 1307If enough data was available, then the callback must remove all data it is
1164interested in (which can be none at all) and return a true value. After returning 1308interested in (which can be none at all) and return a true value. After returning
1165true, it will be removed from the queue. 1309true, it will be removed from the queue.
1166 1310
1311These methods may invoke callbacks (and therefore the handle might be
1312destroyed after it returns).
1313
1167=cut 1314=cut
1168 1315
1169our %RH; 1316our %RH;
1170 1317
1171sub register_read_type($$) { 1318sub register_read_type($$) {
… …
1177 my $cb = pop; 1324 my $cb = pop;
1178 1325
1179 if (@_) { 1326 if (@_) {
1180 my $type = shift; 1327 my $type = shift;
1181 1328
1329 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
1182 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_read") 1330 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_read")
1183 ->($self, $cb, @_); 1331 ->($self, $cb, @_);
1184 } 1332 }
1185 1333
1186 push @{ $self->{_queue} }, $cb; 1334 push @{ $self->{_queue} }, $cb;
1187 $self->_drain_rbuf; 1335 $self->_drain_rbuf;
… …
1192 my $cb = pop; 1340 my $cb = pop;
1193 1341
1194 if (@_) { 1342 if (@_) {
1195 my $type = shift; 1343 my $type = shift;
1196 1344
1345 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
1197 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::unshift_read") 1346 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::unshift_read")
1198 ->($self, $cb, @_); 1347 ->($self, $cb, @_);
1199 } 1348 }
1200
1201 1349
1202 unshift @{ $self->{_queue} }, $cb; 1350 unshift @{ $self->{_queue} }, $cb;
1203 $self->_drain_rbuf; 1351 $self->_drain_rbuf;
1204} 1352}
1205 1353
… …
1207 1355
1208=item $handle->unshift_read (type => @args, $cb) 1356=item $handle->unshift_read (type => @args, $cb)
1209 1357
1210Instead of providing a callback that parses the data itself you can chose 1358Instead of providing a callback that parses the data itself you can chose
1211between a number of predefined parsing formats, for chunks of data, lines 1359between a number of predefined parsing formats, for chunks of data, lines
1212etc. 1360etc. You can also specify the (fully qualified) name of a package, in
1361which case AnyEvent tries to load the package and then expects to find the
1362C<anyevent_read_type> function inside (see "custom read types", below).
1213 1363
1214Predefined types are (if you have ideas for additional types, feel free to 1364Predefined types are (if you have ideas for additional types, feel free to
1215drop by and tell us): 1365drop by and tell us):
1216 1366
1217=over 4 1367=over 4
… …
1309the receive buffer when neither C<$accept> nor C<$reject> match, 1459the receive buffer when neither C<$accept> nor C<$reject> match,
1310and everything preceding and including the match will be accepted 1460and everything preceding and including the match will be accepted
1311unconditionally. This is useful to skip large amounts of data that you 1461unconditionally. This is useful to skip large amounts of data that you
1312know cannot be matched, so that the C<$accept> or C<$reject> regex do not 1462know cannot be matched, so that the C<$accept> or C<$reject> regex do not
1313have to start matching from the beginning. This is purely an optimisation 1463have to start matching from the beginning. This is purely an optimisation
1314and is usually worth only when you expect more than a few kilobytes. 1464and is usually worth it only when you expect more than a few kilobytes.
1315 1465
1316Example: expect a http header, which ends at C<\015\012\015\012>. Since we 1466Example: expect a http header, which ends at C<\015\012\015\012>. Since we
1317expect the header to be very large (it isn't in practise, but...), we use 1467expect the header to be very large (it isn't in practice, but...), we use
1318a skip regex to skip initial portions. The skip regex is tricky in that 1468a skip regex to skip initial portions. The skip regex is tricky in that
1319it only accepts something not ending in either \015 or \012, as these are 1469it only accepts something not ending in either \015 or \012, as these are
1320required for the accept regex. 1470required for the accept regex.
1321 1471
1322 $handle->push_read (regex => 1472 $handle->push_read (regex =>
… …
1457=cut 1607=cut
1458 1608
1459register_read_type json => sub { 1609register_read_type json => sub {
1460 my ($self, $cb) = @_; 1610 my ($self, $cb) = @_;
1461 1611
1462 my $json = $self->{json} ||= 1612 my $json = $self->{json} ||= json_coder;
1463 eval { require JSON::XS; JSON::XS->new->utf8 }
1464 || do { require JSON; JSON->new->utf8 };
1465 1613
1466 my $data; 1614 my $data;
1467 my $rbuf = \$self->{rbuf}; 1615 my $rbuf = \$self->{rbuf};
1468 1616
1469 sub { 1617 sub {
… …
1538 } 1686 }
1539}; 1687};
1540 1688
1541=back 1689=back
1542 1690
1543=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args) 1691=item custom read types - Package::anyevent_read_type $handle, $cb, @args
1544 1692
1545This function (not method) lets you add your own types to C<push_read>. 1693Instead of one of the predefined types, you can also specify the name
1694of a package. AnyEvent will try to load the package and then expects to
1695find a function named C<anyevent_read_type> inside. If it isn't found, it
1696progressively tries to load the parent package until it either finds the
1697function (good) or runs out of packages (bad).
1546 1698
1547Whenever the given C<type> is used, C<push_read> will invoke the code 1699Whenever this type is used, C<push_read> will invoke the function with the
1548reference with the handle object, the callback and the remaining 1700handle object, the original callback and the remaining arguments.
1549arguments.
1550 1701
1551The code reference is supposed to return a callback (usually a closure) 1702The function is supposed to return a callback (usually a closure) that
1552that works as a plain read callback (see C<< ->push_read ($cb) >>). 1703works as a plain read callback (see C<< ->push_read ($cb) >>), so you can
1704mentally treat the function as a "configurable read type to read callback"
1705converter.
1553 1706
1554It should invoke the passed callback when it is done reading (remember to 1707It should invoke the original callback when it is done reading (remember
1555pass C<$handle> as first argument as all other callbacks do that). 1708to pass C<$handle> as first argument as all other callbacks do that,
1709although there is no strict requirement on this).
1556 1710
1557Note that this is a function, and all types registered this way will be
1558global, so try to use unique names.
1559
1560For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>, 1711For examples, see the source of this module (F<perldoc -m
1561search for C<register_read_type>)). 1712AnyEvent::Handle>, search for C<register_read_type>)).
1562 1713
1563=item $handle->stop_read 1714=item $handle->stop_read
1564 1715
1565=item $handle->start_read 1716=item $handle->start_read
1566 1717
… …
1586} 1737}
1587 1738
1588sub start_read { 1739sub start_read {
1589 my ($self) = @_; 1740 my ($self) = @_;
1590 1741
1591 unless ($self->{_rw} || $self->{_eof}) { 1742 unless ($self->{_rw} || $self->{_eof} || !$self->{fh}) {
1592 Scalar::Util::weaken $self; 1743 Scalar::Util::weaken $self;
1593 1744
1594 $self->{_rw} = AE::io $self->{fh}, 0, sub { 1745 $self->{_rw} = AE::io $self->{fh}, 0, sub {
1595 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf}); 1746 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1596 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1747 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;
… …
1689 && ($tmp != $ERROR_SYSCALL || $!); 1840 && ($tmp != $ERROR_SYSCALL || $!);
1690 1841
1691 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) { 1842 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1692 $self->{wbuf} .= $tmp; 1843 $self->{wbuf} .= $tmp;
1693 $self->_drain_wbuf; 1844 $self->_drain_wbuf;
1845 $self->{tls} or return; # tls session might have gone away in callback
1694 } 1846 }
1695 1847
1696 $self->{_on_starttls} 1848 $self->{_on_starttls}
1697 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK () 1849 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1698 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established"); 1850 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
… …
1720context in C<< $handle->{tls_ctx} >> after this call and can be used or 1872context in C<< $handle->{tls_ctx} >> after this call and can be used or
1721changed to your liking. Note that the handshake might have already started 1873changed to your liking. Note that the handshake might have already started
1722when this function returns. 1874when this function returns.
1723 1875
1724Due to bugs in OpenSSL, it might or might not be possible to do multiple 1876Due to bugs in OpenSSL, it might or might not be possible to do multiple
1725handshakes on the same stream. Best do not attempt to use the stream after 1877handshakes on the same stream. It is best to not attempt to use the
1726stopping TLS. 1878stream after stopping TLS.
1879
1880This method may invoke callbacks (and therefore the handle might be
1881destroyed after it returns).
1727 1882
1728=cut 1883=cut
1729 1884
1730our %TLS_CACHE; #TODO not yet documented, should we? 1885our %TLS_CACHE; #TODO not yet documented, should we?
1731 1886
… …
1743 require Net::SSLeay; 1898 require Net::SSLeay;
1744 1899
1745 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL (); 1900 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1746 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ (); 1901 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1747 1902
1748 $tls = $self->{tls}; 1903 $tls = delete $self->{tls};
1749 $ctx = $self->{tls_ctx}; 1904 $ctx = $self->{tls_ctx};
1750 1905
1751 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session 1906 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
1752 1907
1753 if ("HASH" eq ref $ctx) { 1908 if ("HASH" eq ref $ctx) {
… …
1797 1952
1798=item $handle->stoptls 1953=item $handle->stoptls
1799 1954
1800Shuts down the SSL connection - this makes a proper EOF handshake by 1955Shuts down the SSL connection - this makes a proper EOF handshake by
1801sending a close notify to the other side, but since OpenSSL doesn't 1956sending a close notify to the other side, but since OpenSSL doesn't
1802support non-blocking shut downs, it is not guarenteed that you can re-use 1957support non-blocking shut downs, it is not guaranteed that you can re-use
1803the stream afterwards. 1958the stream afterwards.
1959
1960This method may invoke callbacks (and therefore the handle might be
1961destroyed after it returns).
1804 1962
1805=cut 1963=cut
1806 1964
1807sub stoptls { 1965sub stoptls {
1808 my ($self) = @_; 1966 my ($self) = @_;
1809 1967
1810 if ($self->{tls}) { 1968 if ($self->{tls} && $self->{fh}) {
1811 Net::SSLeay::shutdown ($self->{tls}); 1969 Net::SSLeay::shutdown ($self->{tls});
1812 1970
1813 &_dotls; 1971 &_dotls;
1814 1972
1815# # we don't give a shit. no, we do, but we can't. no...#d# 1973# # we don't give a shit. no, we do, but we can't. no...#d#
… …
1892 2050
1893sub AnyEvent::Handle::destroyed::AUTOLOAD { 2051sub AnyEvent::Handle::destroyed::AUTOLOAD {
1894 #nop 2052 #nop
1895} 2053}
1896 2054
2055=item $handle->destroyed
2056
2057Returns false as long as the handle hasn't been destroyed by a call to C<<
2058->destroy >>, true otherwise.
2059
2060Can be useful to decide whether the handle is still valid after some
2061callback possibly destroyed the handle. For example, C<< ->push_write >>,
2062C<< ->starttls >> and other methods can call user callbacks, which in turn
2063can destroy the handle, so work can be avoided by checking sometimes:
2064
2065 $hdl->starttls ("accept");
2066 return if $hdl->destroyed;
2067 $hdl->push_write (...
2068
2069Note that the call to C<push_write> will silently be ignored if the handle
2070has been destroyed, so often you can just ignore the possibility of the
2071handle being destroyed.
2072
2073=cut
2074
2075sub destroyed { 0 }
2076sub AnyEvent::Handle::destroyed::destroyed { 1 }
2077
1897=item AnyEvent::Handle::TLS_CTX 2078=item AnyEvent::Handle::TLS_CTX
1898 2079
1899This function creates and returns the AnyEvent::TLS object used by default 2080This function creates and returns the AnyEvent::TLS object used by default
1900for TLS mode. 2081for TLS mode.
1901 2082
… …
1932 2113
1933=item I get different callback invocations in TLS mode/Why can't I pause 2114=item I get different callback invocations in TLS mode/Why can't I pause
1934reading? 2115reading?
1935 2116
1936Unlike, say, TCP, TLS connections do not consist of two independent 2117Unlike, say, TCP, TLS connections do not consist of two independent
1937communication channels, one for each direction. Or put differently. The 2118communication channels, one for each direction. Or put differently, the
1938read and write directions are not independent of each other: you cannot 2119read and write directions are not independent of each other: you cannot
1939write data unless you are also prepared to read, and vice versa. 2120write data unless you are also prepared to read, and vice versa.
1940 2121
1941This can mean than, in TLS mode, you might get C<on_error> or C<on_eof> 2122This means that, in TLS mode, you might get C<on_error> or C<on_eof>
1942callback invocations when you are not expecting any read data - the reason 2123callback invocations when you are not expecting any read data - the reason
1943is that AnyEvent::Handle always reads in TLS mode. 2124is that AnyEvent::Handle always reads in TLS mode.
1944 2125
1945During the connection, you have to make sure that you always have a 2126During the connection, you have to make sure that you always have a
1946non-empty read-queue, or an C<on_read> watcher. At the end of the 2127non-empty read-queue, or an C<on_read> watcher. At the end of the
… …
1960 my $data = delete $_[0]{rbuf}; 2141 my $data = delete $_[0]{rbuf};
1961 }); 2142 });
1962 2143
1963The reason to use C<on_error> is that TCP connections, due to latencies 2144The reason to use C<on_error> is that TCP connections, due to latencies
1964and packets loss, might get closed quite violently with an error, when in 2145and packets loss, might get closed quite violently with an error, when in
1965fact, all data has been received. 2146fact all data has been received.
1966 2147
1967It is usually better to use acknowledgements when transferring data, 2148It is usually better to use acknowledgements when transferring data,
1968to make sure the other side hasn't just died and you got the data 2149to make sure the other side hasn't just died and you got the data
1969intact. This is also one reason why so many internet protocols have an 2150intact. This is also one reason why so many internet protocols have an
1970explicit QUIT command. 2151explicit QUIT command.
… …
1987consider using C<< ->push_shutdown >> instead. 2168consider using C<< ->push_shutdown >> instead.
1988 2169
1989=item I want to contact a TLS/SSL server, I don't care about security. 2170=item I want to contact a TLS/SSL server, I don't care about security.
1990 2171
1991If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS, 2172If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
1992simply connect to it and then create the AnyEvent::Handle with the C<tls> 2173connect to it and then create the AnyEvent::Handle with the C<tls>
1993parameter: 2174parameter:
1994 2175
1995 tcp_connect $host, $port, sub { 2176 tcp_connect $host, $port, sub {
1996 my ($fh) = @_; 2177 my ($fh) = @_;
1997 2178
… …
2097 2278
2098=item * all members not documented here and not prefixed with an underscore 2279=item * all members not documented here and not prefixed with an underscore
2099are free to use in subclasses. 2280are free to use in subclasses.
2100 2281
2101Of course, new versions of AnyEvent::Handle may introduce more "public" 2282Of course, new versions of AnyEvent::Handle may introduce more "public"
2102member variables, but thats just life, at least it is documented. 2283member variables, but that's just life. At least it is documented.
2103 2284
2104=back 2285=back
2105 2286
2106=head1 AUTHOR 2287=head1 AUTHOR
2107 2288

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines