… | |
… | |
247 | many seconds pass without a successful read or write on the underlying |
247 | many seconds pass without a successful read or write on the underlying |
248 | file handle (or a call to C<timeout_reset>), the C<on_timeout> callback |
248 | file handle (or a call to C<timeout_reset>), the C<on_timeout> callback |
249 | will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT> |
249 | will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT> |
250 | error will be raised). |
250 | error will be raised). |
251 | |
251 | |
252 | There are three variants of the timeouts that work independently |
252 | There are three variants of the timeouts that work independently of each |
253 | of each other, for both read and write, just read, and just write: |
253 | other, for both read and write (triggered when nothing was read I<OR> |
|
|
254 | written), just read (triggered when nothing was read), and just write: |
254 | C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks |
255 | C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks |
255 | C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions |
256 | C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions |
256 | C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>. |
257 | C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>. |
257 | |
258 | |
258 | Note that timeout processing is active even when you do not have |
259 | Note that timeout processing is active even when you do not have any |
259 | any outstanding read or write requests: If you plan to keep the connection |
260 | outstanding read or write requests: If you plan to keep the connection |
260 | idle then you should disable the timeout temporarily or ignore the timeout |
261 | idle then you should disable the timeout temporarily or ignore the |
261 | in the C<on_timeout> callback, in which case AnyEvent::Handle will simply |
262 | timeout in the corresponding C<on_timeout> callback, in which case |
262 | restart the timeout. |
263 | AnyEvent::Handle will simply restart the timeout. |
263 | |
264 | |
264 | Zero (the default) disables this timeout. |
265 | Zero (the default) disables the corresponding timeout. |
265 | |
266 | |
266 | =item on_timeout => $cb->($handle) |
267 | =item on_timeout => $cb->($handle) |
|
|
268 | |
|
|
269 | =item on_rtimeout => $cb->($handle) |
|
|
270 | |
|
|
271 | =item on_wtimeout => $cb->($handle) |
267 | |
272 | |
268 | Called whenever the inactivity timeout passes. If you return from this |
273 | Called whenever the inactivity timeout passes. If you return from this |
269 | callback, then the timeout will be reset as if some activity had happened, |
274 | callback, then the timeout will be reset as if some activity had happened, |
270 | so this condition is not fatal in any way. |
275 | so this condition is not fatal in any way. |
271 | |
276 | |
… | |
… | |
536 | }); |
541 | }); |
537 | |
542 | |
538 | } else { |
543 | } else { |
539 | if ($self->{on_connect_error}) { |
544 | if ($self->{on_connect_error}) { |
540 | $self->{on_connect_error}($self, "$!"); |
545 | $self->{on_connect_error}($self, "$!"); |
541 | $self->destroy; |
546 | $self->destroy if $self; |
542 | } else { |
547 | } else { |
543 | $self->_error ($!, 1); |
548 | $self->_error ($!, 1); |
544 | } |
549 | } |
545 | } |
550 | } |
546 | }, |
551 | }, |
… | |
… | |
765 | |
770 | |
766 | sub rbuf_max { |
771 | sub rbuf_max { |
767 | $_[0]{rbuf_max} = $_[1]; |
772 | $_[0]{rbuf_max} = $_[1]; |
768 | } |
773 | } |
769 | |
774 | |
770 | sub rbuf_max { |
775 | sub wbuf_max { |
771 | $_[0]{wbuf_max} = $_[1]; |
776 | $_[0]{wbuf_max} = $_[1]; |
772 | } |
777 | } |
773 | |
778 | |
774 | ############################################################################# |
779 | ############################################################################# |
775 | |
780 | |
… | |
… | |
778 | =item $handle->rtimeout ($seconds) |
783 | =item $handle->rtimeout ($seconds) |
779 | |
784 | |
780 | =item $handle->wtimeout ($seconds) |
785 | =item $handle->wtimeout ($seconds) |
781 | |
786 | |
782 | Configures (or disables) the inactivity timeout. |
787 | Configures (or disables) the inactivity timeout. |
|
|
788 | |
|
|
789 | The timeout will be checked instantly, so this method might destroy the |
|
|
790 | handle before it returns. |
783 | |
791 | |
784 | =item $handle->timeout_reset |
792 | =item $handle->timeout_reset |
785 | |
793 | |
786 | =item $handle->rtimeout_reset |
794 | =item $handle->rtimeout_reset |
787 | |
795 | |
… | |
… | |
1087 | before it was actually written. One way to do that is to replace your |
1095 | before it was actually written. One way to do that is to replace your |
1088 | C<on_drain> handler by a callback that shuts down the socket (and set |
1096 | C<on_drain> handler by a callback that shuts down the socket (and set |
1089 | C<low_water_mark> to C<0>). This method is a shorthand for just that, and |
1097 | C<low_water_mark> to C<0>). This method is a shorthand for just that, and |
1090 | replaces the C<on_drain> callback with: |
1098 | replaces the C<on_drain> callback with: |
1091 | |
1099 | |
1092 | sub { shutdown $_[0]{fh}, 1 } # for push_shutdown |
1100 | sub { shutdown $_[0]{fh}, 1 } |
1093 | |
1101 | |
1094 | This simply shuts down the write side and signals an EOF condition to the |
1102 | This simply shuts down the write side and signals an EOF condition to the |
1095 | the peer. |
1103 | the peer. |
1096 | |
1104 | |
1097 | You can rely on the normal read queue and C<on_eof> handling |
1105 | You can rely on the normal read queue and C<on_eof> handling |
… | |
… | |
1616 | sub { |
1624 | sub { |
1617 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1625 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1618 | defined (my $len = eval { unpack $format, $_[0]{rbuf} }) |
1626 | defined (my $len = eval { unpack $format, $_[0]{rbuf} }) |
1619 | or return; |
1627 | or return; |
1620 | |
1628 | |
1621 | warn "len $len\n";#d# |
|
|
1622 | $format = length pack $format, $len; |
1629 | $format = length pack $format, $len; |
1623 | warn "len2 $format\n";#d# |
|
|
1624 | |
1630 | |
1625 | # bypass unshift if we already have the remaining chunk |
1631 | # bypass unshift if we already have the remaining chunk |
1626 | if ($format + $len <= length $_[0]{rbuf}) { |
1632 | if ($format + $len <= length $_[0]{rbuf}) { |
1627 | my $data = substr $_[0]{rbuf}, $format, $len; |
1633 | my $data = substr $_[0]{rbuf}, $format, $len; |
1628 | substr $_[0]{rbuf}, 0, $format + $len, ""; |
1634 | substr $_[0]{rbuf}, 0, $format + $len, ""; |
… | |
… | |
1775 | Note that AnyEvent::Handle will automatically C<start_read> for you when |
1781 | Note that AnyEvent::Handle will automatically C<start_read> for you when |
1776 | you change the C<on_read> callback or push/unshift a read callback, and it |
1782 | you change the C<on_read> callback or push/unshift a read callback, and it |
1777 | will automatically C<stop_read> for you when neither C<on_read> is set nor |
1783 | will automatically C<stop_read> for you when neither C<on_read> is set nor |
1778 | there are any read requests in the queue. |
1784 | there are any read requests in the queue. |
1779 | |
1785 | |
1780 | These methods will have no effect when in TLS mode (as TLS doesn't support |
1786 | In older versions of this module (<= 5.3), these methods had no effect, |
1781 | half-duplex connections). |
1787 | as TLS does not support half-duplex connections. In current versions they |
|
|
1788 | work as expected, as this behaviour is required to avoid certain resource |
|
|
1789 | attacks, where the program would be forced to read (and buffer) arbitrary |
|
|
1790 | amounts of data before being able to send some data. The drawback is that |
|
|
1791 | some readings of the the SSL/TLS specifications basically require this |
|
|
1792 | attack to be working, as SSL/TLS implementations might stall sending data |
|
|
1793 | during a rehandshake. |
|
|
1794 | |
|
|
1795 | As a guideline, during the initial handshake, you should not stop reading, |
|
|
1796 | and as a client, it might cause problems, depending on your applciation. |
1782 | |
1797 | |
1783 | =cut |
1798 | =cut |
1784 | |
1799 | |
1785 | sub stop_read { |
1800 | sub stop_read { |
1786 | my ($self) = @_; |
1801 | my ($self) = @_; |
1787 | |
1802 | |
1788 | delete $self->{_rw} unless $self->{tls}; |
1803 | delete $self->{_rw}; |
1789 | } |
1804 | } |
1790 | |
1805 | |
1791 | sub start_read { |
1806 | sub start_read { |
1792 | my ($self) = @_; |
1807 | my ($self) = @_; |
1793 | |
1808 | |
… | |
… | |
2043 | if $self->{tls} > 0; |
2058 | if $self->{tls} > 0; |
2044 | |
2059 | |
2045 | delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)}; |
2060 | delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)}; |
2046 | } |
2061 | } |
2047 | |
2062 | |
|
|
2063 | =item $handle->resettls |
|
|
2064 | |
|
|
2065 | This rarely-used method simply resets and TLS state on the handle, usually |
|
|
2066 | causing data loss. |
|
|
2067 | |
|
|
2068 | One case where it may be useful is when you want to skip over the data in |
|
|
2069 | the stream but you are not interested in interpreting it, so data loss is |
|
|
2070 | no concern. |
|
|
2071 | |
|
|
2072 | =cut |
|
|
2073 | |
|
|
2074 | *resettls = \&_freetls; |
|
|
2075 | |
2048 | sub DESTROY { |
2076 | sub DESTROY { |
2049 | my ($self) = @_; |
2077 | my ($self) = @_; |
2050 | |
2078 | |
2051 | &_freetls; |
2079 | &_freetls; |
2052 | |
2080 | |