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.183 by root, Thu Sep 3 12:45:35 2009 UTC vs.
Revision 1.202 by root, Sat Oct 16 02:01: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.
289 307
290=item keepalive => <boolean> 308=item keepalive => <boolean>
291 309
292Enables (default disable) the SO_KEEPALIVE option on the stream socket: 310Enables (default disable) the SO_KEEPALIVE option on the stream socket:
293normally, TCP connections have no time-out once established, so TCP 311normally, TCP connections have no time-out once established, so TCP
294conenctions, once established, can stay alive forever even when the other 312connections, once established, can stay alive forever even when the other
295side has long gone. TCP keepalives are a cheap way to take down long-lived 313side has long gone. TCP keepalives are a cheap way to take down long-lived
296TCP connections whent he other side becomes unreachable. While the default 314TCP connections when the other side becomes unreachable. While the default
297is OS-dependent, TCP keepalives usually kick in after around two hours, 315is OS-dependent, TCP keepalives usually kick in after around two hours,
298and, if the other side doesn't reply, take down the TCP connection some 10 316and, if the other side doesn't reply, take down the TCP connection some 10
299to 15 minutes later. 317to 15 minutes later.
300 318
301It is harmless to specify this option for file handles that do not support 319It is harmless to specify this option for file handles that do not support
… …
312is enabled) gives you the most portable way of getting urgent data, by 330is enabled) gives you the most portable way of getting urgent data, by
313putting it into the stream. 331putting it into the stream.
314 332
315Since BSD emulation of OOB data on top of TCP's urgent data can have 333Since BSD emulation of OOB data on top of TCP's urgent data can have
316security implications, AnyEvent::Handle sets this flag automatically 334security implications, AnyEvent::Handle sets this flag automatically
317unless explicitly specified. 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.
318 339
319=item read_size => <bytes> 340=item read_size => <bytes>
320 341
321The default read block size (the amount of bytes this module will 342The default read block size (the number of bytes this module will
322try to read during each loop iteration, which affects memory 343try to read during each loop iteration, which affects memory
323requirements). Default: C<8192>. 344requirements). Default: C<8192>.
324 345
325=item low_water_mark => <bytes> 346=item low_water_mark => <bytes>
326 347
327Sets 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
328buffer: 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
329considered empty. 350considered empty.
330 351
331Sometimes it can be beneficial (for performance reasons) to add data to 352Sometimes it can be beneficial (for performance reasons) to add data to
332the 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
333the operating system kernel usually buffers data as well, so the default 354the operating system kernel usually buffers data as well, so the default
334is good in almost all cases. 355is good in almost all cases.
335 356
336=item linger => <seconds> 357=item linger => <seconds>
337 358
338If non-zero (default: C<3600>), then the destructor of the 359If this is non-zero (default: C<3600>), the destructor of the
339AnyEvent::Handle object will check whether there is still outstanding 360AnyEvent::Handle object will check whether there is still outstanding
340write 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
341socket. No errors will be reported (this mostly matches how the operating 362socket. No errors will be reported (this mostly matches how the operating
342system treats outstanding data at socket close time). 363system treats outstanding data at socket close time).
343 364
… …
350A string used to identify the remote site - usually the DNS hostname 371A string used to identify the remote site - usually the DNS hostname
351(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.
352 373
353Apart 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
354peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This 375peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
355verification will be skipped when C<peername> is not specified or 376verification will be skipped when C<peername> is not specified or is
356C<undef>. 377C<undef>.
357 378
358=item tls => "accept" | "connect" | Net::SSLeay::SSL object 379=item tls => "accept" | "connect" | Net::SSLeay::SSL object
359 380
360When this parameter is given, it enables TLS (SSL) mode, that means 381When this parameter is given, it enables TLS (SSL) mode, that means
361AnyEvent 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
362established and will transparently encrypt/decrypt data afterwards. 383established and will transparently encrypt/decrypt data afterwards.
363 384
364All TLS protocol errors will be signalled as C<EPROTO>, with an 385All TLS protocol errors will be signalled as C<EPROTO>, with an
365appropriate error message. 386appropriate error message.
366 387
… …
386B<IMPORTANT:> since Net::SSLeay "objects" are really only integers, 407B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
387passing 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
388happens 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
389segmentation fault. 410segmentation fault.
390 411
391See 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.
392 413
393=item tls_ctx => $anyevent_tls 414=item tls_ctx => $anyevent_tls
394 415
395Use 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
396(unless a connection object was specified directly). If this parameter is 417(unless a connection object was specified directly). If this parameter is
… …
411 432
412TLS 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
413callback 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>.
414 435
415Without this callback, handshake failures lead to C<on_error> being 436Without this callback, handshake failures lead to C<on_error> being
416called, as normal. 437called as usual.
417 438
418Note 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
419need 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
420then call C<< ->starttls >> again. 441then call C<< ->starttls >> again.
421 442
422=item on_stoptls => $cb->($handle) 443=item on_stoptls => $cb->($handle)
423 444
… …
513} 534}
514 535
515sub _start { 536sub _start {
516 my ($self) = @_; 537 my ($self) = @_;
517 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
518 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 545 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
519 546
520 $self->{_activity} = 547 $self->{_activity} =
521 $self->{_ractivity} = 548 $self->{_ractivity} =
522 $self->{_wactivity} = AE::now; 549 $self->{_wactivity} = AE::now;
… …
531 $self->oobinline (exists $self->{oobinline} ? delete $self->{oobinline} : 1); 558 $self->oobinline (exists $self->{oobinline} ? delete $self->{oobinline} : 1);
532 559
533 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}) 560 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
534 if $self->{tls}; 561 if $self->{tls};
535 562
536 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; 563 $self->on_drain (delete $self->{on_drain} ) if $self->{on_drain};
537 564
538 $self->start_read 565 $self->start_read
539 if $self->{on_read} || @{ $self->{_queue} }; 566 if $self->{on_read} || @{ $self->{_queue} };
540 567
541 $self->_drain_wbuf; 568 $self->_drain_wbuf;
… …
548 $message ||= "$!"; 575 $message ||= "$!";
549 576
550 if ($self->{on_error}) { 577 if ($self->{on_error}) {
551 $self->{on_error}($self, $fatal, $message); 578 $self->{on_error}($self, $fatal, $message);
552 $self->destroy if $fatal; 579 $self->destroy if $fatal;
553 } elsif ($self->{fh}) { 580 } elsif ($self->{fh} || $self->{connect}) {
554 $self->destroy; 581 $self->destroy;
555 Carp::croak "AnyEvent::Handle uncaught error: $message"; 582 Carp::croak "AnyEvent::Handle uncaught error: $message";
556 } 583 }
557} 584}
558 585
… …
617=cut 644=cut
618 645
619sub no_delay { 646sub no_delay {
620 $_[0]{no_delay} = $_[1]; 647 $_[0]{no_delay} = $_[1];
621 648
622 eval {
623 local $SIG{__DIE__};
624 setsockopt $_[0]{fh}, Socket::IPPROTO_TCP (), Socket::TCP_NODELAY (), int $_[1] 649 setsockopt $_[0]{fh}, Socket::IPPROTO_TCP (), Socket::TCP_NODELAY (), int $_[1]
625 if $_[0]{fh}; 650 if $_[0]{fh};
626 };
627} 651}
628 652
629=item $handle->keepalive ($boolean) 653=item $handle->keepalive ($boolean)
630 654
631Enables or disables the C<keepalive> setting (see constructor argument of 655Enables or disables the C<keepalive> setting (see constructor argument of
… …
691 715
692Replace 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).
693 717
694=cut 718=cut
695 719
696sub on_starttls { 720sub on_stoptls {
697 $_[0]{on_stoptls} = $_[1]; 721 $_[0]{on_stoptls} = $_[1];
698} 722}
699 723
700=item $handle->rbuf_max ($max_octets) 724=item $handle->rbuf_max ($max_octets)
701 725
… …
740 $_[0]{$on_timeout} = $_[1]; 764 $_[0]{$on_timeout} = $_[1];
741 }; 765 };
742 766
743 *$timeout = sub { 767 *$timeout = sub {
744 my ($self, $new_value) = @_; 768 my ($self, $new_value) = @_;
769
770 $new_value >= 0
771 or Carp::croak "AnyEvent::Handle->$timeout called with negative timeout ($new_value), caught";
745 772
746 $self->{$timeout} = $new_value; 773 $self->{$timeout} = $new_value;
747 delete $self->{$tw}; &$cb; 774 delete $self->{$tw}; &$cb;
748 }; 775 };
749 776
… …
813=item $handle->on_drain ($cb) 840=item $handle->on_drain ($cb)
814 841
815Sets the C<on_drain> callback or clears it (see the description of 842Sets the C<on_drain> callback or clears it (see the description of
816C<on_drain> in the constructor). 843C<on_drain> in the constructor).
817 844
845This method may invoke callbacks (and therefore the handle might be
846destroyed after it returns).
847
818=cut 848=cut
819 849
820sub on_drain { 850sub on_drain {
821 my ($self, $cb) = @_; 851 my ($self, $cb) = @_;
822 852
… …
829=item $handle->push_write ($data) 859=item $handle->push_write ($data)
830 860
831Queues the given scalar to be written. You can push as much data as you 861Queues the given scalar to be written. You can push as much data as you
832want (only limited by the available memory), as C<AnyEvent::Handle> 862want (only limited by the available memory), as C<AnyEvent::Handle>
833buffers it independently of the kernel. 863buffers it independently of the kernel.
864
865This method may invoke callbacks (and therefore the handle might be
866destroyed after it returns).
834 867
835=cut 868=cut
836 869
837sub _drain_wbuf { 870sub _drain_wbuf {
838 my ($self) = @_; 871 my ($self) = @_;
… …
868 }; 901 };
869} 902}
870 903
871our %WH; 904our %WH;
872 905
906# deprecated
873sub register_write_type($$) { 907sub register_write_type($$) {
874 $WH{$_[0]} = $_[1]; 908 $WH{$_[0]} = $_[1];
875} 909}
876 910
877sub push_write { 911sub push_write {
878 my $self = shift; 912 my $self = shift;
879 913
880 if (@_ > 1) { 914 if (@_ > 1) {
881 my $type = shift; 915 my $type = shift;
882 916
917 @_ = ($WH{$type} ||= _load_func "$type\::anyevent_write_type"
883 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 918 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_write")
884 ->($self, @_); 919 ->($self, @_);
885 } 920 }
886 921
922 # we downgrade here to avoid hard-to-track-down bugs,
923 # and diagnose the problem earlier and better.
924
887 if ($self->{tls}) { 925 if ($self->{tls}) {
888 $self->{_tls_wbuf} .= $_[0]; 926 utf8::downgrade $self->{_tls_wbuf} .= $_[0];
889 &_dotls ($self) if $self->{fh}; 927 &_dotls ($self) if $self->{fh};
890 } else { 928 } else {
891 $self->{wbuf} .= $_[0]; 929 utf8::downgrade $self->{wbuf} .= $_[0];
892 $self->_drain_wbuf if $self->{fh}; 930 $self->_drain_wbuf if $self->{fh};
893 } 931 }
894} 932}
895 933
896=item $handle->push_write (type => @args) 934=item $handle->push_write (type => @args)
897 935
898Instead of formatting your data yourself, you can also let this module do 936Instead of formatting your data yourself, you can also let this module
899the job by specifying a type and type-specific arguments. 937do the job by specifying a type and type-specific arguments. You
938can also specify the (fully qualified) name of a package, in which
939case AnyEvent tries to load the package and then expects to find the
940C<anyevent_write_type> function inside (see "custom write types", below).
900 941
901Predefined types are (if you have ideas for additional types, feel free to 942Predefined types are (if you have ideas for additional types, feel free to
902drop by and tell us): 943drop by and tell us):
903 944
904=over 4 945=over 4
… …
1007the peer. 1048the peer.
1008 1049
1009You can rely on the normal read queue and C<on_eof> handling 1050You can rely on the normal read queue and C<on_eof> handling
1010afterwards. This is the cleanest way to close a connection. 1051afterwards. This is the cleanest way to close a connection.
1011 1052
1053This method may invoke callbacks (and therefore the handle might be
1054destroyed after it returns).
1055
1012=cut 1056=cut
1013 1057
1014sub push_shutdown { 1058sub push_shutdown {
1015 my ($self) = @_; 1059 my ($self) = @_;
1016 1060
1017 delete $self->{low_water_mark}; 1061 delete $self->{low_water_mark};
1018 $self->on_drain (sub { shutdown $_[0]{fh}, 1 }); 1062 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
1019} 1063}
1020 1064
1021=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 1065=item custom write types - Package::anyevent_write_type $handle, @args
1022 1066
1023This function (not method) lets you add your own types to C<push_write>. 1067Instead of one of the predefined types, you can also specify the name of
1068a package. AnyEvent will try to load the package and then expects to find
1069a function named C<anyevent_write_type> inside. If it isn't found, it
1070progressively tries to load the parent package until it either finds the
1071function (good) or runs out of packages (bad).
1072
1024Whenever the given C<type> is used, C<push_write> will invoke the code 1073Whenever the given C<type> is used, C<push_write> will the function with
1025reference with the handle object and the remaining arguments. 1074the handle object and the remaining arguments.
1026 1075
1027The code reference is supposed to return a single octet string that will 1076The function is supposed to return a single octet string that will be
1028be appended to the write buffer. 1077appended to the write buffer, so you cna mentally treat this function as a
1078"arguments to on-the-wire-format" converter.
1029 1079
1030Note that this is a function, and all types registered this way will be 1080Example: implement a custom write type C<join> that joins the remaining
1031global, so try to use unique names. 1081arguments using the first one.
1082
1083 $handle->push_write (My::Type => " ", 1,2,3);
1084
1085 # uses the following package, which can be defined in the "My::Type" or in
1086 # the "My" modules to be auto-loaded, or just about anywhere when the
1087 # My::Type::anyevent_write_type is defined before invoking it.
1088
1089 package My::Type;
1090
1091 sub anyevent_write_type {
1092 my ($handle, $delim, @args) = @_;
1093
1094 join $delim, @args
1095 }
1032 1096
1033=cut 1097=cut
1034 1098
1035############################################################################# 1099#############################################################################
1036 1100
… …
1045ways, the "simple" way, using only C<on_read> and the "complex" way, using 1109ways, the "simple" way, using only C<on_read> and the "complex" way, using
1046a queue. 1110a queue.
1047 1111
1048In the simple case, you just install an C<on_read> callback and whenever 1112In the simple case, you just install an C<on_read> callback and whenever
1049new data arrives, it will be called. You can then remove some data (if 1113new data arrives, it will be called. You can then remove some data (if
1050enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna 1114enough is there) from the read buffer (C<< $handle->rbuf >>). Or you can
1051leave the data there if you want to accumulate more (e.g. when only a 1115leave the data there if you want to accumulate more (e.g. when only a
1052partial message has been received so far). 1116partial message has been received so far), or change the read queue with
1117e.g. C<push_read>.
1053 1118
1054In the more complex case, you want to queue multiple callbacks. In this 1119In the more complex case, you want to queue multiple callbacks. In this
1055case, AnyEvent::Handle will call the first queued callback each time new 1120case, AnyEvent::Handle will call the first queued callback each time new
1056data arrives (also the first time it is queued) and removes it when it has 1121data arrives (also the first time it is queued) and remove it when it has
1057done its job (see C<push_read>, below). 1122done its job (see C<push_read>, below).
1058 1123
1059This way you can, for example, push three line-reads, followed by reading 1124This way you can, for example, push three line-reads, followed by reading
1060a chunk of data, and AnyEvent::Handle will execute them in order. 1125a chunk of data, and AnyEvent::Handle will execute them in order.
1061 1126
… …
1192 1257
1193This replaces the currently set C<on_read> callback, or clears it (when 1258This replaces the currently set C<on_read> callback, or clears it (when
1194the new callback is C<undef>). See the description of C<on_read> in the 1259the new callback is C<undef>). See the description of C<on_read> in the
1195constructor. 1260constructor.
1196 1261
1262This method may invoke callbacks (and therefore the handle might be
1263destroyed after it returns).
1264
1197=cut 1265=cut
1198 1266
1199sub on_read { 1267sub on_read {
1200 my ($self, $cb) = @_; 1268 my ($self, $cb) = @_;
1201 1269
… …
1203 $self->_drain_rbuf if $cb; 1271 $self->_drain_rbuf if $cb;
1204} 1272}
1205 1273
1206=item $handle->rbuf 1274=item $handle->rbuf
1207 1275
1208Returns the read buffer (as a modifiable lvalue). 1276Returns the read buffer (as a modifiable lvalue). You can also access the
1277read buffer directly as the C<< ->{rbuf} >> member, if you want (this is
1278much faster, and no less clean).
1209 1279
1210You can access the read buffer directly as the C<< ->{rbuf} >> 1280The only operation allowed on the read buffer (apart from looking at it)
1211member, if you want. However, the only operation allowed on the 1281is removing data from its beginning. Otherwise modifying or appending to
1212read buffer (apart from looking at it) is removing data from its 1282it is not allowed and will lead to hard-to-track-down bugs.
1213beginning. Otherwise modifying or appending to it is not allowed and will
1214lead to hard-to-track-down bugs.
1215 1283
1216NOTE: The read buffer should only be used or modified if the C<on_read>, 1284NOTE: The read buffer should only be used or modified in the C<on_read>
1217C<push_read> or C<unshift_read> methods are used. The other read methods 1285callback or when C<push_read> or C<unshift_read> are used with a single
1218automatically manage the read buffer. 1286callback (i.e. untyped). Typed C<push_read> and C<unshift_read> methods
1287will manage the read buffer on their own.
1219 1288
1220=cut 1289=cut
1221 1290
1222sub rbuf : lvalue { 1291sub rbuf : lvalue {
1223 $_[0]{rbuf} 1292 $_[0]{rbuf}
… …
1240 1309
1241If enough data was available, then the callback must remove all data it is 1310If enough data was available, then the callback must remove all data it is
1242interested in (which can be none at all) and return a true value. After returning 1311interested in (which can be none at all) and return a true value. After returning
1243true, it will be removed from the queue. 1312true, it will be removed from the queue.
1244 1313
1314These methods may invoke callbacks (and therefore the handle might be
1315destroyed after it returns).
1316
1245=cut 1317=cut
1246 1318
1247our %RH; 1319our %RH;
1248 1320
1249sub register_read_type($$) { 1321sub register_read_type($$) {
… …
1255 my $cb = pop; 1327 my $cb = pop;
1256 1328
1257 if (@_) { 1329 if (@_) {
1258 my $type = shift; 1330 my $type = shift;
1259 1331
1332 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
1260 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_read") 1333 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_read")
1261 ->($self, $cb, @_); 1334 ->($self, $cb, @_);
1262 } 1335 }
1263 1336
1264 push @{ $self->{_queue} }, $cb; 1337 push @{ $self->{_queue} }, $cb;
1265 $self->_drain_rbuf; 1338 $self->_drain_rbuf;
… …
1270 my $cb = pop; 1343 my $cb = pop;
1271 1344
1272 if (@_) { 1345 if (@_) {
1273 my $type = shift; 1346 my $type = shift;
1274 1347
1348 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
1275 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::unshift_read") 1349 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::unshift_read")
1276 ->($self, $cb, @_); 1350 ->($self, $cb, @_);
1277 } 1351 }
1278 1352
1279 unshift @{ $self->{_queue} }, $cb; 1353 unshift @{ $self->{_queue} }, $cb;
1280 $self->_drain_rbuf; 1354 $self->_drain_rbuf;
… …
1284 1358
1285=item $handle->unshift_read (type => @args, $cb) 1359=item $handle->unshift_read (type => @args, $cb)
1286 1360
1287Instead of providing a callback that parses the data itself you can chose 1361Instead of providing a callback that parses the data itself you can chose
1288between a number of predefined parsing formats, for chunks of data, lines 1362between a number of predefined parsing formats, for chunks of data, lines
1289etc. 1363etc. You can also specify the (fully qualified) name of a package, in
1364which case AnyEvent tries to load the package and then expects to find the
1365C<anyevent_read_type> function inside (see "custom read types", below).
1290 1366
1291Predefined types are (if you have ideas for additional types, feel free to 1367Predefined types are (if you have ideas for additional types, feel free to
1292drop by and tell us): 1368drop by and tell us):
1293 1369
1294=over 4 1370=over 4
… …
1386the receive buffer when neither C<$accept> nor C<$reject> match, 1462the receive buffer when neither C<$accept> nor C<$reject> match,
1387and everything preceding and including the match will be accepted 1463and everything preceding and including the match will be accepted
1388unconditionally. This is useful to skip large amounts of data that you 1464unconditionally. This is useful to skip large amounts of data that you
1389know cannot be matched, so that the C<$accept> or C<$reject> regex do not 1465know cannot be matched, so that the C<$accept> or C<$reject> regex do not
1390have to start matching from the beginning. This is purely an optimisation 1466have to start matching from the beginning. This is purely an optimisation
1391and is usually worth only when you expect more than a few kilobytes. 1467and is usually worth it only when you expect more than a few kilobytes.
1392 1468
1393Example: expect a http header, which ends at C<\015\012\015\012>. Since we 1469Example: expect a http header, which ends at C<\015\012\015\012>. Since we
1394expect the header to be very large (it isn't in practise, but...), we use 1470expect the header to be very large (it isn't in practice, but...), we use
1395a skip regex to skip initial portions. The skip regex is tricky in that 1471a skip regex to skip initial portions. The skip regex is tricky in that
1396it only accepts something not ending in either \015 or \012, as these are 1472it only accepts something not ending in either \015 or \012, as these are
1397required for the accept regex. 1473required for the accept regex.
1398 1474
1399 $handle->push_read (regex => 1475 $handle->push_read (regex =>
… …
1613 } 1689 }
1614}; 1690};
1615 1691
1616=back 1692=back
1617 1693
1618=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args) 1694=item custom read types - Package::anyevent_read_type $handle, $cb, @args
1619 1695
1620This function (not method) lets you add your own types to C<push_read>. 1696Instead of one of the predefined types, you can also specify the name
1697of a package. AnyEvent will try to load the package and then expects to
1698find a function named C<anyevent_read_type> inside. If it isn't found, it
1699progressively tries to load the parent package until it either finds the
1700function (good) or runs out of packages (bad).
1621 1701
1622Whenever the given C<type> is used, C<push_read> will invoke the code 1702Whenever this type is used, C<push_read> will invoke the function with the
1623reference with the handle object, the callback and the remaining 1703handle object, the original callback and the remaining arguments.
1624arguments.
1625 1704
1626The code reference is supposed to return a callback (usually a closure) 1705The function is supposed to return a callback (usually a closure) that
1627that works as a plain read callback (see C<< ->push_read ($cb) >>). 1706works as a plain read callback (see C<< ->push_read ($cb) >>), so you can
1707mentally treat the function as a "configurable read type to read callback"
1708converter.
1628 1709
1629It should invoke the passed callback when it is done reading (remember to 1710It should invoke the original callback when it is done reading (remember
1630pass C<$handle> as first argument as all other callbacks do that). 1711to pass C<$handle> as first argument as all other callbacks do that,
1712although there is no strict requirement on this).
1631 1713
1632Note that this is a function, and all types registered this way will be
1633global, so try to use unique names.
1634
1635For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>, 1714For examples, see the source of this module (F<perldoc -m
1636search for C<register_read_type>)). 1715AnyEvent::Handle>, search for C<register_read_type>)).
1637 1716
1638=item $handle->stop_read 1717=item $handle->stop_read
1639 1718
1640=item $handle->start_read 1719=item $handle->start_read
1641 1720
… …
1661} 1740}
1662 1741
1663sub start_read { 1742sub start_read {
1664 my ($self) = @_; 1743 my ($self) = @_;
1665 1744
1666 unless ($self->{_rw} || $self->{_eof}) { 1745 unless ($self->{_rw} || $self->{_eof} || !$self->{fh}) {
1667 Scalar::Util::weaken $self; 1746 Scalar::Util::weaken $self;
1668 1747
1669 $self->{_rw} = AE::io $self->{fh}, 0, sub { 1748 $self->{_rw} = AE::io $self->{fh}, 0, sub {
1670 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf}); 1749 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1671 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1750 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;
… …
1764 && ($tmp != $ERROR_SYSCALL || $!); 1843 && ($tmp != $ERROR_SYSCALL || $!);
1765 1844
1766 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) { 1845 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1767 $self->{wbuf} .= $tmp; 1846 $self->{wbuf} .= $tmp;
1768 $self->_drain_wbuf; 1847 $self->_drain_wbuf;
1848 $self->{tls} or return; # tls session might have gone away in callback
1769 } 1849 }
1770 1850
1771 $self->{_on_starttls} 1851 $self->{_on_starttls}
1772 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK () 1852 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1773 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established"); 1853 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
… …
1795context in C<< $handle->{tls_ctx} >> after this call and can be used or 1875context in C<< $handle->{tls_ctx} >> after this call and can be used or
1796changed to your liking. Note that the handshake might have already started 1876changed to your liking. Note that the handshake might have already started
1797when this function returns. 1877when this function returns.
1798 1878
1799Due to bugs in OpenSSL, it might or might not be possible to do multiple 1879Due to bugs in OpenSSL, it might or might not be possible to do multiple
1800handshakes on the same stream. Best do not attempt to use the stream after 1880handshakes on the same stream. It is best to not attempt to use the
1801stopping TLS. 1881stream after stopping TLS.
1882
1883This method may invoke callbacks (and therefore the handle might be
1884destroyed after it returns).
1802 1885
1803=cut 1886=cut
1804 1887
1805our %TLS_CACHE; #TODO not yet documented, should we? 1888our %TLS_CACHE; #TODO not yet documented, should we?
1806 1889
… …
1872 1955
1873=item $handle->stoptls 1956=item $handle->stoptls
1874 1957
1875Shuts down the SSL connection - this makes a proper EOF handshake by 1958Shuts down the SSL connection - this makes a proper EOF handshake by
1876sending a close notify to the other side, but since OpenSSL doesn't 1959sending a close notify to the other side, but since OpenSSL doesn't
1877support non-blocking shut downs, it is not guarenteed that you can re-use 1960support non-blocking shut downs, it is not guaranteed that you can re-use
1878the stream afterwards. 1961the stream afterwards.
1962
1963This method may invoke callbacks (and therefore the handle might be
1964destroyed after it returns).
1879 1965
1880=cut 1966=cut
1881 1967
1882sub stoptls { 1968sub stoptls {
1883 my ($self) = @_; 1969 my ($self) = @_;
1884 1970
1885 if ($self->{tls}) { 1971 if ($self->{tls} && $self->{fh}) {
1886 Net::SSLeay::shutdown ($self->{tls}); 1972 Net::SSLeay::shutdown ($self->{tls});
1887 1973
1888 &_dotls; 1974 &_dotls;
1889 1975
1890# # we don't give a shit. no, we do, but we can't. no...#d# 1976# # we don't give a shit. no, we do, but we can't. no...#d#
… …
1920 push @linger, AE::io $fh, 1, sub { 2006 push @linger, AE::io $fh, 1, sub {
1921 my $len = syswrite $fh, $wbuf, length $wbuf; 2007 my $len = syswrite $fh, $wbuf, length $wbuf;
1922 2008
1923 if ($len > 0) { 2009 if ($len > 0) {
1924 substr $wbuf, 0, $len, ""; 2010 substr $wbuf, 0, $len, "";
1925 } else { 2011 } elsif (defined $len || ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK)) {
1926 @linger = (); # end 2012 @linger = (); # end
1927 } 2013 }
1928 }; 2014 };
1929 push @linger, AE::timer $linger, 0, sub { 2015 push @linger, AE::timer $linger, 0, sub {
1930 @linger = (); 2016 @linger = ();
… …
1967 2053
1968sub AnyEvent::Handle::destroyed::AUTOLOAD { 2054sub AnyEvent::Handle::destroyed::AUTOLOAD {
1969 #nop 2055 #nop
1970} 2056}
1971 2057
2058=item $handle->destroyed
2059
2060Returns false as long as the handle hasn't been destroyed by a call to C<<
2061->destroy >>, true otherwise.
2062
2063Can be useful to decide whether the handle is still valid after some
2064callback possibly destroyed the handle. For example, C<< ->push_write >>,
2065C<< ->starttls >> and other methods can call user callbacks, which in turn
2066can destroy the handle, so work can be avoided by checking sometimes:
2067
2068 $hdl->starttls ("accept");
2069 return if $hdl->destroyed;
2070 $hdl->push_write (...
2071
2072Note that the call to C<push_write> will silently be ignored if the handle
2073has been destroyed, so often you can just ignore the possibility of the
2074handle being destroyed.
2075
2076=cut
2077
2078sub destroyed { 0 }
2079sub AnyEvent::Handle::destroyed::destroyed { 1 }
2080
1972=item AnyEvent::Handle::TLS_CTX 2081=item AnyEvent::Handle::TLS_CTX
1973 2082
1974This function creates and returns the AnyEvent::TLS object used by default 2083This function creates and returns the AnyEvent::TLS object used by default
1975for TLS mode. 2084for TLS mode.
1976 2085
… …
2007 2116
2008=item I get different callback invocations in TLS mode/Why can't I pause 2117=item I get different callback invocations in TLS mode/Why can't I pause
2009reading? 2118reading?
2010 2119
2011Unlike, say, TCP, TLS connections do not consist of two independent 2120Unlike, say, TCP, TLS connections do not consist of two independent
2012communication channels, one for each direction. Or put differently. The 2121communication channels, one for each direction. Or put differently, the
2013read and write directions are not independent of each other: you cannot 2122read and write directions are not independent of each other: you cannot
2014write data unless you are also prepared to read, and vice versa. 2123write data unless you are also prepared to read, and vice versa.
2015 2124
2016This can mean than, in TLS mode, you might get C<on_error> or C<on_eof> 2125This means that, in TLS mode, you might get C<on_error> or C<on_eof>
2017callback invocations when you are not expecting any read data - the reason 2126callback invocations when you are not expecting any read data - the reason
2018is that AnyEvent::Handle always reads in TLS mode. 2127is that AnyEvent::Handle always reads in TLS mode.
2019 2128
2020During the connection, you have to make sure that you always have a 2129During the connection, you have to make sure that you always have a
2021non-empty read-queue, or an C<on_read> watcher. At the end of the 2130non-empty read-queue, or an C<on_read> watcher. At the end of the
… …
2035 my $data = delete $_[0]{rbuf}; 2144 my $data = delete $_[0]{rbuf};
2036 }); 2145 });
2037 2146
2038The reason to use C<on_error> is that TCP connections, due to latencies 2147The reason to use C<on_error> is that TCP connections, due to latencies
2039and packets loss, might get closed quite violently with an error, when in 2148and packets loss, might get closed quite violently with an error, when in
2040fact, all data has been received. 2149fact all data has been received.
2041 2150
2042It is usually better to use acknowledgements when transferring data, 2151It is usually better to use acknowledgements when transferring data,
2043to make sure the other side hasn't just died and you got the data 2152to make sure the other side hasn't just died and you got the data
2044intact. This is also one reason why so many internet protocols have an 2153intact. This is also one reason why so many internet protocols have an
2045explicit QUIT command. 2154explicit QUIT command.
… …
2062consider using C<< ->push_shutdown >> instead. 2171consider using C<< ->push_shutdown >> instead.
2063 2172
2064=item I want to contact a TLS/SSL server, I don't care about security. 2173=item I want to contact a TLS/SSL server, I don't care about security.
2065 2174
2066If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS, 2175If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
2067simply connect to it and then create the AnyEvent::Handle with the C<tls> 2176connect to it and then create the AnyEvent::Handle with the C<tls>
2068parameter: 2177parameter:
2069 2178
2070 tcp_connect $host, $port, sub { 2179 tcp_connect $host, $port, sub {
2071 my ($fh) = @_; 2180 my ($fh) = @_;
2072 2181
… …
2172 2281
2173=item * all members not documented here and not prefixed with an underscore 2282=item * all members not documented here and not prefixed with an underscore
2174are free to use in subclasses. 2283are free to use in subclasses.
2175 2284
2176Of course, new versions of AnyEvent::Handle may introduce more "public" 2285Of course, new versions of AnyEvent::Handle may introduce more "public"
2177member variables, but thats just life, at least it is documented. 2286member variables, but that's just life. At least it is documented.
2178 2287
2179=back 2288=back
2180 2289
2181=head1 AUTHOR 2290=head1 AUTHOR
2182 2291

Diff Legend

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