… | |
… | |
11 | |
11 | |
12 | my $hdl; $hdl = new AnyEvent::Handle |
12 | my $hdl; $hdl = new AnyEvent::Handle |
13 | fh => \*STDIN, |
13 | fh => \*STDIN, |
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 | AE::log error => $msg; |
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 |
25 | $hdl->push_read (line => sub { |
25 | $hdl->push_read (line => sub { |
26 | my ($hdl, $line) = @_; |
26 | my ($hdl, $line) = @_; |
27 | warn "got line <$line>\n"; |
27 | say "got line <$line>"; |
28 | $cv->send; |
28 | $cv->send; |
29 | }); |
29 | }); |
30 | |
30 | |
31 | $cv->recv; |
31 | $cv->recv; |
32 | |
32 | |
… | |
… | |
128 | =item on_connect => $cb->($handle, $host, $port, $retry->()) |
128 | =item on_connect => $cb->($handle, $host, $port, $retry->()) |
129 | |
129 | |
130 | This callback is called when a connection has been successfully established. |
130 | This callback is called when a connection has been successfully established. |
131 | |
131 | |
132 | The peer's numeric host and port (the socket peername) are passed as |
132 | The peer's numeric host and port (the socket peername) are passed as |
133 | parameters, together with a retry callback. |
133 | parameters, together with a retry callback. At the time it is called the |
|
|
134 | read and write queues, EOF status, TLS status and similar properties of |
|
|
135 | the handle will have been reset. |
134 | |
136 | |
|
|
137 | It is not allowed to use the read or write queues while the handle object |
|
|
138 | is connecting. |
|
|
139 | |
135 | If, for some reason, the handle is not acceptable, calling C<$retry> |
140 | If, for some reason, the handle is not acceptable, calling C<$retry> will |
136 | will continue with the next connection target (in case of multi-homed |
141 | continue with the next connection target (in case of multi-homed hosts or |
137 | hosts or SRV records there can be multiple connection endpoints). At the |
142 | SRV records there can be multiple connection endpoints). The C<$retry> |
138 | time it is called the read and write queues, eof status, tls status and |
143 | callback can be invoked after the connect callback returns, i.e. one can |
139 | similar properties of the handle will have been reset. |
144 | start a handshake and then decide to retry with the next host if the |
|
|
145 | handshake fails. |
140 | |
146 | |
141 | In most cases, you should ignore the C<$retry> parameter. |
147 | In most cases, you should ignore the C<$retry> parameter. |
142 | |
148 | |
143 | =item on_connect_error => $cb->($handle, $message) |
149 | =item on_connect_error => $cb->($handle, $message) |
144 | |
150 | |
… | |
… | |
164 | with active (but unsatisfiable) read watchers (C<EPIPE>) or I/O errors. In |
170 | with active (but unsatisfiable) read watchers (C<EPIPE>) or I/O errors. In |
165 | cases where the other side can close the connection at will, it is |
171 | cases where the other side can close the connection at will, it is |
166 | often easiest to not report C<EPIPE> errors in this callback. |
172 | often easiest to not report C<EPIPE> errors in this callback. |
167 | |
173 | |
168 | AnyEvent::Handle tries to find an appropriate error code for you to check |
174 | AnyEvent::Handle tries to find an appropriate error code for you to check |
169 | against, but in some cases (TLS errors), this does not work well. It is |
175 | against, but in some cases (TLS errors), this does not work well. |
170 | recommended to always output the C<$message> argument in human-readable |
176 | |
171 | error messages (it's usually the same as C<"$!">). |
177 | If you report the error to the user, it is recommended to always output |
|
|
178 | the C<$message> argument in human-readable error messages (you don't need |
|
|
179 | to report C<"$!"> if you report C<$message>). |
|
|
180 | |
|
|
181 | If you want to react programmatically to the error, then looking at C<$!> |
|
|
182 | and comparing it against some of the documented C<Errno> values is usually |
|
|
183 | better than looking at the C<$message>. |
172 | |
184 | |
173 | Non-fatal errors can be retried by returning, but it is recommended |
185 | Non-fatal errors can be retried by returning, but it is recommended |
174 | to simply ignore this parameter and instead abondon the handle object |
186 | to simply ignore this parameter and instead abondon the handle object |
175 | when this callback is invoked. Examples of non-fatal errors are timeouts |
187 | when this callback is invoked. Examples of non-fatal errors are timeouts |
176 | C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>). |
188 | C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>). |
… | |
… | |
224 | If an EOF condition has been detected but no C<on_eof> callback has been |
236 | If an EOF condition has been detected but no C<on_eof> callback has been |
225 | set, then a fatal error will be raised with C<$!> set to <0>. |
237 | set, then a fatal error will be raised with C<$!> set to <0>. |
226 | |
238 | |
227 | =item on_drain => $cb->($handle) |
239 | =item on_drain => $cb->($handle) |
228 | |
240 | |
229 | This sets the callback that is called when the write buffer becomes empty |
241 | This sets the callback that is called once when the write buffer becomes |
230 | (or immediately if the buffer is empty already). |
242 | empty (and immediately when the handle object is created). |
231 | |
243 | |
232 | To append to the write buffer, use the C<< ->push_write >> method. |
244 | To append to the write buffer, use the C<< ->push_write >> method. |
233 | |
245 | |
234 | This callback is useful when you don't want to put all of your write data |
246 | This callback is useful when you don't want to put all of your write data |
235 | into the queue at once, for example, when you want to write the contents |
247 | into the queue at once, for example, when you want to write the contents |
… | |
… | |
247 | many seconds pass without a successful read or write on the underlying |
259 | 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 |
260 | 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> |
261 | will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT> |
250 | error will be raised). |
262 | error will be raised). |
251 | |
263 | |
252 | There are three variants of the timeouts that work independently |
264 | 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: |
265 | other, for both read and write (triggered when nothing was read I<OR> |
|
|
266 | written), just read (triggered when nothing was read), and just write: |
254 | C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks |
267 | C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks |
255 | C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions |
268 | C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions |
256 | C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>. |
269 | C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>. |
257 | |
270 | |
258 | Note that timeout processing is active even when you do not have |
271 | 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 |
272 | 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 |
273 | 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 |
274 | timeout in the corresponding C<on_timeout> callback, in which case |
262 | restart the timeout. |
275 | AnyEvent::Handle will simply restart the timeout. |
263 | |
276 | |
264 | Zero (the default) disables this timeout. |
277 | Zero (the default) disables the corresponding timeout. |
265 | |
278 | |
266 | =item on_timeout => $cb->($handle) |
279 | =item on_timeout => $cb->($handle) |
|
|
280 | |
|
|
281 | =item on_rtimeout => $cb->($handle) |
|
|
282 | |
|
|
283 | =item on_wtimeout => $cb->($handle) |
267 | |
284 | |
268 | Called whenever the inactivity timeout passes. If you return from this |
285 | 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, |
286 | callback, then the timeout will be reset as if some activity had happened, |
270 | so this condition is not fatal in any way. |
287 | so this condition is not fatal in any way. |
271 | |
288 | |
… | |
… | |
354 | already have occured on BSD systems), but at least it will protect you |
371 | already have occured on BSD systems), but at least it will protect you |
355 | from most attacks. |
372 | from most attacks. |
356 | |
373 | |
357 | =item read_size => <bytes> |
374 | =item read_size => <bytes> |
358 | |
375 | |
359 | The initial read block size, the number of bytes this module will try to |
376 | The initial read block size, the number of bytes this module will try |
360 | read during each loop iteration. Each handle object will consume at least |
377 | to read during each loop iteration. Each handle object will consume |
361 | this amount of memory for the read buffer as well, so when handling many |
378 | at least this amount of memory for the read buffer as well, so when |
362 | connections requirements). See also C<max_read_size>. Default: C<2048>. |
379 | handling many connections watch out for memory requirements). See also |
|
|
380 | C<max_read_size>. Default: C<2048>. |
363 | |
381 | |
364 | =item max_read_size => <bytes> |
382 | =item max_read_size => <bytes> |
365 | |
383 | |
366 | The maximum read buffer size used by the dynamic adjustment |
384 | The maximum read buffer size used by the dynamic adjustment |
367 | algorithm: Each time AnyEvent::Handle can read C<read_size> bytes in |
385 | algorithm: Each time AnyEvent::Handle can read C<read_size> bytes in |
… | |
… | |
411 | appropriate error message. |
429 | appropriate error message. |
412 | |
430 | |
413 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
431 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
414 | automatically when you try to create a TLS handle): this module doesn't |
432 | automatically when you try to create a TLS handle): this module doesn't |
415 | have a dependency on that module, so if your module requires it, you have |
433 | have a dependency on that module, so if your module requires it, you have |
416 | to add the dependency yourself. |
434 | to add the dependency yourself. If Net::SSLeay cannot be loaded or is too |
|
|
435 | old, you get an C<EPROTO> error. |
417 | |
436 | |
418 | Unlike TCP, TLS has a server and client side: for the TLS server side, use |
437 | Unlike TCP, TLS has a server and client side: for the TLS server side, use |
419 | C<accept>, and for the TLS client side of a connection, use C<connect> |
438 | C<accept>, and for the TLS client side of a connection, use C<connect> |
420 | mode. |
439 | mode. |
421 | |
440 | |
… | |
… | |
536 | }); |
555 | }); |
537 | |
556 | |
538 | } else { |
557 | } else { |
539 | if ($self->{on_connect_error}) { |
558 | if ($self->{on_connect_error}) { |
540 | $self->{on_connect_error}($self, "$!"); |
559 | $self->{on_connect_error}($self, "$!"); |
541 | $self->destroy; |
560 | $self->destroy if $self; |
542 | } else { |
561 | } else { |
543 | $self->_error ($!, 1); |
562 | $self->_error ($!, 1); |
544 | } |
563 | } |
545 | } |
564 | } |
546 | }, |
565 | }, |
… | |
… | |
765 | |
784 | |
766 | sub rbuf_max { |
785 | sub rbuf_max { |
767 | $_[0]{rbuf_max} = $_[1]; |
786 | $_[0]{rbuf_max} = $_[1]; |
768 | } |
787 | } |
769 | |
788 | |
770 | sub rbuf_max { |
789 | sub wbuf_max { |
771 | $_[0]{wbuf_max} = $_[1]; |
790 | $_[0]{wbuf_max} = $_[1]; |
772 | } |
791 | } |
773 | |
792 | |
774 | ############################################################################# |
793 | ############################################################################# |
775 | |
794 | |
… | |
… | |
778 | =item $handle->rtimeout ($seconds) |
797 | =item $handle->rtimeout ($seconds) |
779 | |
798 | |
780 | =item $handle->wtimeout ($seconds) |
799 | =item $handle->wtimeout ($seconds) |
781 | |
800 | |
782 | Configures (or disables) the inactivity timeout. |
801 | Configures (or disables) the inactivity timeout. |
|
|
802 | |
|
|
803 | The timeout will be checked instantly, so this method might destroy the |
|
|
804 | handle before it returns. |
783 | |
805 | |
784 | =item $handle->timeout_reset |
806 | =item $handle->timeout_reset |
785 | |
807 | |
786 | =item $handle->rtimeout_reset |
808 | =item $handle->rtimeout_reset |
787 | |
809 | |
… | |
… | |
871 | |
893 | |
872 | The write queue is very simple: you can add data to its end, and |
894 | The write queue is very simple: you can add data to its end, and |
873 | AnyEvent::Handle will automatically try to get rid of it for you. |
895 | AnyEvent::Handle will automatically try to get rid of it for you. |
874 | |
896 | |
875 | When data could be written and the write buffer is shorter then the low |
897 | When data could be written and the write buffer is shorter then the low |
876 | water mark, the C<on_drain> callback will be invoked. |
898 | water mark, the C<on_drain> callback will be invoked once. |
877 | |
899 | |
878 | =over 4 |
900 | =over 4 |
879 | |
901 | |
880 | =item $handle->on_drain ($cb) |
902 | =item $handle->on_drain ($cb) |
881 | |
903 | |
… | |
… | |
1072 | =cut |
1094 | =cut |
1073 | |
1095 | |
1074 | register_write_type storable => sub { |
1096 | register_write_type storable => sub { |
1075 | my ($self, $ref) = @_; |
1097 | my ($self, $ref) = @_; |
1076 | |
1098 | |
1077 | require Storable; |
1099 | require Storable unless $Storable::VERSION; |
1078 | |
1100 | |
1079 | pack "w/a*", Storable::nfreeze ($ref) |
1101 | pack "w/a*", Storable::nfreeze ($ref) |
1080 | }; |
1102 | }; |
1081 | |
1103 | |
1082 | =back |
1104 | =back |
… | |
… | |
1087 | before it was actually written. One way to do that is to replace your |
1109 | 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 |
1110 | 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 |
1111 | C<low_water_mark> to C<0>). This method is a shorthand for just that, and |
1090 | replaces the C<on_drain> callback with: |
1112 | replaces the C<on_drain> callback with: |
1091 | |
1113 | |
1092 | sub { shutdown $_[0]{fh}, 1 } # for push_shutdown |
1114 | sub { shutdown $_[0]{fh}, 1 } |
1093 | |
1115 | |
1094 | This simply shuts down the write side and signals an EOF condition to the |
1116 | This simply shuts down the write side and signals an EOF condition to the |
1095 | the peer. |
1117 | the peer. |
1096 | |
1118 | |
1097 | You can rely on the normal read queue and C<on_eof> handling |
1119 | You can rely on the normal read queue and C<on_eof> handling |
… | |
… | |
1119 | |
1141 | |
1120 | Whenever the given C<type> is used, C<push_write> will the function with |
1142 | Whenever the given C<type> is used, C<push_write> will the function with |
1121 | the handle object and the remaining arguments. |
1143 | the handle object and the remaining arguments. |
1122 | |
1144 | |
1123 | The function is supposed to return a single octet string that will be |
1145 | The function is supposed to return a single octet string that will be |
1124 | appended to the write buffer, so you cna mentally treat this function as a |
1146 | appended to the write buffer, so you can mentally treat this function as a |
1125 | "arguments to on-the-wire-format" converter. |
1147 | "arguments to on-the-wire-format" converter. |
1126 | |
1148 | |
1127 | Example: implement a custom write type C<join> that joins the remaining |
1149 | Example: implement a custom write type C<join> that joins the remaining |
1128 | arguments using the first one. |
1150 | arguments using the first one. |
1129 | |
1151 | |
… | |
… | |
1423 | data. |
1445 | data. |
1424 | |
1446 | |
1425 | Example: read 2 bytes. |
1447 | Example: read 2 bytes. |
1426 | |
1448 | |
1427 | $handle->push_read (chunk => 2, sub { |
1449 | $handle->push_read (chunk => 2, sub { |
1428 | warn "yay ", unpack "H*", $_[1]; |
1450 | say "yay " . unpack "H*", $_[1]; |
1429 | }); |
1451 | }); |
1430 | |
1452 | |
1431 | =cut |
1453 | =cut |
1432 | |
1454 | |
1433 | register_read_type chunk => sub { |
1455 | register_read_type chunk => sub { |
… | |
… | |
1467 | if (@_ < 3) { |
1489 | if (@_ < 3) { |
1468 | # this is more than twice as fast as the generic code below |
1490 | # this is more than twice as fast as the generic code below |
1469 | sub { |
1491 | sub { |
1470 | $_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return; |
1492 | $_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return; |
1471 | |
1493 | |
1472 | $cb->($_[0], $1, $2); |
1494 | $cb->($_[0], "$1", "$2"); |
1473 | 1 |
1495 | 1 |
1474 | } |
1496 | } |
1475 | } else { |
1497 | } else { |
1476 | $eol = quotemeta $eol unless ref $eol; |
1498 | $eol = quotemeta $eol unless ref $eol; |
1477 | $eol = qr|^(.*?)($eol)|s; |
1499 | $eol = qr|^(.*?)($eol)|s; |
1478 | |
1500 | |
1479 | sub { |
1501 | sub { |
1480 | $_[0]{rbuf} =~ s/$eol// or return; |
1502 | $_[0]{rbuf} =~ s/$eol// or return; |
1481 | |
1503 | |
1482 | $cb->($_[0], $1, $2); |
1504 | $cb->($_[0], "$1", "$2"); |
1483 | 1 |
1505 | 1 |
1484 | } |
1506 | } |
1485 | } |
1507 | } |
1486 | }; |
1508 | }; |
1487 | |
1509 | |
… | |
… | |
1535 | |
1557 | |
1536 | sub { |
1558 | sub { |
1537 | # accept |
1559 | # accept |
1538 | if ($$rbuf =~ $accept) { |
1560 | if ($$rbuf =~ $accept) { |
1539 | $data .= substr $$rbuf, 0, $+[0], ""; |
1561 | $data .= substr $$rbuf, 0, $+[0], ""; |
1540 | $cb->($self, $data); |
1562 | $cb->($_[0], $data); |
1541 | return 1; |
1563 | return 1; |
1542 | } |
1564 | } |
1543 | |
1565 | |
1544 | # reject |
1566 | # reject |
1545 | if ($reject && $$rbuf =~ $reject) { |
1567 | if ($reject && $$rbuf =~ $reject) { |
1546 | $self->_error (Errno::EBADMSG); |
1568 | $_[0]->_error (Errno::EBADMSG); |
1547 | } |
1569 | } |
1548 | |
1570 | |
1549 | # skip |
1571 | # skip |
1550 | if ($skip && $$rbuf =~ $skip) { |
1572 | if ($skip && $$rbuf =~ $skip) { |
1551 | $data .= substr $$rbuf, 0, $+[0], ""; |
1573 | $data .= substr $$rbuf, 0, $+[0], ""; |
… | |
… | |
1567 | my ($self, $cb) = @_; |
1589 | my ($self, $cb) = @_; |
1568 | |
1590 | |
1569 | sub { |
1591 | sub { |
1570 | unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) { |
1592 | unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) { |
1571 | if ($_[0]{rbuf} =~ /[^0-9]/) { |
1593 | if ($_[0]{rbuf} =~ /[^0-9]/) { |
1572 | $self->_error (Errno::EBADMSG); |
1594 | $_[0]->_error (Errno::EBADMSG); |
1573 | } |
1595 | } |
1574 | return; |
1596 | return; |
1575 | } |
1597 | } |
1576 | |
1598 | |
1577 | my $len = $1; |
1599 | my $len = $1; |
1578 | |
1600 | |
1579 | $self->unshift_read (chunk => $len, sub { |
1601 | $_[0]->unshift_read (chunk => $len, sub { |
1580 | my $string = $_[1]; |
1602 | my $string = $_[1]; |
1581 | $_[0]->unshift_read (chunk => 1, sub { |
1603 | $_[0]->unshift_read (chunk => 1, sub { |
1582 | if ($_[1] eq ",") { |
1604 | if ($_[1] eq ",") { |
1583 | $cb->($_[0], $string); |
1605 | $cb->($_[0], $string); |
1584 | } else { |
1606 | } else { |
1585 | $self->_error (Errno::EBADMSG); |
1607 | $_[0]->_error (Errno::EBADMSG); |
1586 | } |
1608 | } |
1587 | }); |
1609 | }); |
1588 | }); |
1610 | }); |
1589 | |
1611 | |
1590 | 1 |
1612 | 1 |
… | |
… | |
1663 | |
1685 | |
1664 | my $data; |
1686 | my $data; |
1665 | my $rbuf = \$self->{rbuf}; |
1687 | my $rbuf = \$self->{rbuf}; |
1666 | |
1688 | |
1667 | sub { |
1689 | sub { |
1668 | my $ref = eval { $json->incr_parse ($self->{rbuf}) }; |
1690 | my $ref = eval { $json->incr_parse ($_[0]{rbuf}) }; |
1669 | |
1691 | |
1670 | if ($ref) { |
1692 | if ($ref) { |
1671 | $self->{rbuf} = $json->incr_text; |
1693 | $_[0]{rbuf} = $json->incr_text; |
1672 | $json->incr_text = ""; |
1694 | $json->incr_text = ""; |
1673 | $cb->($self, $ref); |
1695 | $cb->($_[0], $ref); |
1674 | |
1696 | |
1675 | 1 |
1697 | 1 |
1676 | } elsif ($@) { |
1698 | } elsif ($@) { |
1677 | # error case |
1699 | # error case |
1678 | $json->incr_skip; |
1700 | $json->incr_skip; |
1679 | |
1701 | |
1680 | $self->{rbuf} = $json->incr_text; |
1702 | $_[0]{rbuf} = $json->incr_text; |
1681 | $json->incr_text = ""; |
1703 | $json->incr_text = ""; |
1682 | |
1704 | |
1683 | $self->_error (Errno::EBADMSG); |
1705 | $_[0]->_error (Errno::EBADMSG); |
1684 | |
1706 | |
1685 | () |
1707 | () |
1686 | } else { |
1708 | } else { |
1687 | $self->{rbuf} = ""; |
1709 | $_[0]{rbuf} = ""; |
1688 | |
1710 | |
1689 | () |
1711 | () |
1690 | } |
1712 | } |
1691 | } |
1713 | } |
1692 | }; |
1714 | }; |
… | |
… | |
1702 | =cut |
1724 | =cut |
1703 | |
1725 | |
1704 | register_read_type storable => sub { |
1726 | register_read_type storable => sub { |
1705 | my ($self, $cb) = @_; |
1727 | my ($self, $cb) = @_; |
1706 | |
1728 | |
1707 | require Storable; |
1729 | require Storable unless $Storable::VERSION; |
1708 | |
1730 | |
1709 | sub { |
1731 | sub { |
1710 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1732 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1711 | defined (my $len = eval { unpack "w", $_[0]{rbuf} }) |
1733 | defined (my $len = eval { unpack "w", $_[0]{rbuf} }) |
1712 | or return; |
1734 | or return; |
… | |
… | |
1715 | |
1737 | |
1716 | # bypass unshift if we already have the remaining chunk |
1738 | # bypass unshift if we already have the remaining chunk |
1717 | if ($format + $len <= length $_[0]{rbuf}) { |
1739 | if ($format + $len <= length $_[0]{rbuf}) { |
1718 | my $data = substr $_[0]{rbuf}, $format, $len; |
1740 | my $data = substr $_[0]{rbuf}, $format, $len; |
1719 | substr $_[0]{rbuf}, 0, $format + $len, ""; |
1741 | substr $_[0]{rbuf}, 0, $format + $len, ""; |
|
|
1742 | |
1720 | $cb->($_[0], Storable::thaw ($data)); |
1743 | eval { $cb->($_[0], Storable::thaw ($data)); 1 } |
|
|
1744 | or return $_[0]->_error (Errno::EBADMSG); |
1721 | } else { |
1745 | } else { |
1722 | # remove prefix |
1746 | # remove prefix |
1723 | substr $_[0]{rbuf}, 0, $format, ""; |
1747 | substr $_[0]{rbuf}, 0, $format, ""; |
1724 | |
1748 | |
1725 | # read remaining chunk |
1749 | # read remaining chunk |
1726 | $_[0]->unshift_read (chunk => $len, sub { |
1750 | $_[0]->unshift_read (chunk => $len, sub { |
1727 | if (my $ref = eval { Storable::thaw ($_[1]) }) { |
1751 | eval { $cb->($_[0], Storable::thaw ($_[1])); 1 } |
1728 | $cb->($_[0], $ref); |
|
|
1729 | } else { |
|
|
1730 | $self->_error (Errno::EBADMSG); |
1752 | or $_[0]->_error (Errno::EBADMSG); |
1731 | } |
|
|
1732 | }); |
1753 | }); |
1733 | } |
1754 | } |
1734 | |
1755 | |
1735 | 1 |
1756 | 1 |
1736 | } |
1757 | } |
… | |
… | |
1773 | Note that AnyEvent::Handle will automatically C<start_read> for you when |
1794 | Note that AnyEvent::Handle will automatically C<start_read> for you when |
1774 | you change the C<on_read> callback or push/unshift a read callback, and it |
1795 | you change the C<on_read> callback or push/unshift a read callback, and it |
1775 | will automatically C<stop_read> for you when neither C<on_read> is set nor |
1796 | will automatically C<stop_read> for you when neither C<on_read> is set nor |
1776 | there are any read requests in the queue. |
1797 | there are any read requests in the queue. |
1777 | |
1798 | |
1778 | These methods will have no effect when in TLS mode (as TLS doesn't support |
1799 | In older versions of this module (<= 5.3), these methods had no effect, |
1779 | half-duplex connections). |
1800 | as TLS does not support half-duplex connections. In current versions they |
|
|
1801 | work as expected, as this behaviour is required to avoid certain resource |
|
|
1802 | attacks, where the program would be forced to read (and buffer) arbitrary |
|
|
1803 | amounts of data before being able to send some data. The drawback is that |
|
|
1804 | some readings of the the SSL/TLS specifications basically require this |
|
|
1805 | attack to be working, as SSL/TLS implementations might stall sending data |
|
|
1806 | during a rehandshake. |
|
|
1807 | |
|
|
1808 | As a guideline, during the initial handshake, you should not stop reading, |
|
|
1809 | and as a client, it might cause problems, depending on your application. |
1780 | |
1810 | |
1781 | =cut |
1811 | =cut |
1782 | |
1812 | |
1783 | sub stop_read { |
1813 | sub stop_read { |
1784 | my ($self) = @_; |
1814 | my ($self) = @_; |
1785 | |
1815 | |
1786 | delete $self->{_rw} unless $self->{tls}; |
1816 | delete $self->{_rw}; |
1787 | } |
1817 | } |
1788 | |
1818 | |
1789 | sub start_read { |
1819 | sub start_read { |
1790 | my ($self) = @_; |
1820 | my ($self) = @_; |
1791 | |
1821 | |
… | |
… | |
1832 | my ($self, $err) = @_; |
1862 | my ($self, $err) = @_; |
1833 | |
1863 | |
1834 | return $self->_error ($!, 1) |
1864 | return $self->_error ($!, 1) |
1835 | if $err == Net::SSLeay::ERROR_SYSCALL (); |
1865 | if $err == Net::SSLeay::ERROR_SYSCALL (); |
1836 | |
1866 | |
1837 | my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ()); |
1867 | my $err = Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ()); |
1838 | |
1868 | |
1839 | # reduce error string to look less scary |
1869 | # reduce error string to look less scary |
1840 | $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /; |
1870 | $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /; |
1841 | |
1871 | |
1842 | if ($self->{_on_starttls}) { |
1872 | if ($self->{_on_starttls}) { |
… | |
… | |
1908 | |
1938 | |
1909 | =item $handle->starttls ($tls[, $tls_ctx]) |
1939 | =item $handle->starttls ($tls[, $tls_ctx]) |
1910 | |
1940 | |
1911 | Instead of starting TLS negotiation immediately when the AnyEvent::Handle |
1941 | Instead of starting TLS negotiation immediately when the AnyEvent::Handle |
1912 | object is created, you can also do that at a later time by calling |
1942 | object is created, you can also do that at a later time by calling |
1913 | C<starttls>. |
1943 | C<starttls>. See the C<tls> constructor argument for general info. |
1914 | |
1944 | |
1915 | Starting TLS is currently an asynchronous operation - when you push some |
1945 | Starting TLS is currently an asynchronous operation - when you push some |
1916 | write data and then call C<< ->starttls >> then TLS negotiation will start |
1946 | write data and then call C<< ->starttls >> then TLS negotiation will start |
1917 | immediately, after which the queued write data is then sent. |
1947 | immediately, after which the queued write data is then sent. This might |
|
|
1948 | change in future versions, so best make sure you have no outstanding write |
|
|
1949 | data when calling this method. |
1918 | |
1950 | |
1919 | The first argument is the same as the C<tls> constructor argument (either |
1951 | The first argument is the same as the C<tls> constructor argument (either |
1920 | C<"connect">, C<"accept"> or an existing Net::SSLeay object). |
1952 | C<"connect">, C<"accept"> or an existing Net::SSLeay object). |
1921 | |
1953 | |
1922 | The second argument is the optional C<AnyEvent::TLS> object that is used |
1954 | The second argument is the optional C<AnyEvent::TLS> object that is used |
… | |
… | |
1944 | my ($self, $tls, $ctx) = @_; |
1976 | my ($self, $tls, $ctx) = @_; |
1945 | |
1977 | |
1946 | Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught" |
1978 | Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught" |
1947 | if $self->{tls}; |
1979 | if $self->{tls}; |
1948 | |
1980 | |
|
|
1981 | unless (defined $AnyEvent::TLS::VERSION) { |
|
|
1982 | eval { |
|
|
1983 | require Net::SSLeay; |
|
|
1984 | require AnyEvent::TLS; |
|
|
1985 | 1 |
|
|
1986 | } or return $self->_error (Errno::EPROTO, 1, "TLS support not available on this system"); |
|
|
1987 | } |
|
|
1988 | |
1949 | $self->{tls} = $tls; |
1989 | $self->{tls} = $tls; |
1950 | $self->{tls_ctx} = $ctx if @_ > 2; |
1990 | $self->{tls_ctx} = $ctx if @_ > 2; |
1951 | |
1991 | |
1952 | return unless $self->{fh}; |
1992 | return unless $self->{fh}; |
1953 | |
1993 | |
1954 | require Net::SSLeay; |
|
|
1955 | |
|
|
1956 | $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL (); |
1994 | $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL (); |
1957 | $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ (); |
1995 | $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ (); |
1958 | |
1996 | |
1959 | $tls = delete $self->{tls}; |
1997 | $tls = delete $self->{tls}; |
1960 | $ctx = $self->{tls_ctx}; |
1998 | $ctx = $self->{tls_ctx}; |
1961 | |
1999 | |
1962 | local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session |
2000 | local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session |
1963 | |
2001 | |
1964 | if ("HASH" eq ref $ctx) { |
2002 | if ("HASH" eq ref $ctx) { |
1965 | require AnyEvent::TLS; |
|
|
1966 | |
|
|
1967 | if ($ctx->{cache}) { |
2003 | if ($ctx->{cache}) { |
1968 | my $key = $ctx+0; |
2004 | my $key = $ctx+0; |
1969 | $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx; |
2005 | $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx; |
1970 | } else { |
2006 | } else { |
1971 | $ctx = new AnyEvent::TLS %$ctx; |
2007 | $ctx = new AnyEvent::TLS %$ctx; |
… | |
… | |
1993 | Net::SSLeay::CTX_set_mode ($tls, 1|2); |
2029 | Net::SSLeay::CTX_set_mode ($tls, 1|2); |
1994 | |
2030 | |
1995 | $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
2031 | $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
1996 | $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
2032 | $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
1997 | |
2033 | |
1998 | Net::SSLeay::BIO_write ($self->{_rbio}, delete $self->{rbuf}); |
2034 | Net::SSLeay::BIO_write ($self->{_rbio}, $self->{rbuf}); |
|
|
2035 | $self->{rbuf} = ""; |
1999 | |
2036 | |
2000 | Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio}); |
2037 | Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio}); |
2001 | |
2038 | |
2002 | $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) } |
2039 | $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) } |
2003 | if $self->{on_starttls}; |
2040 | if $self->{on_starttls}; |
… | |
… | |
2040 | $self->{tls_ctx}->_put_session (delete $self->{tls}) |
2077 | $self->{tls_ctx}->_put_session (delete $self->{tls}) |
2041 | if $self->{tls} > 0; |
2078 | if $self->{tls} > 0; |
2042 | |
2079 | |
2043 | delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)}; |
2080 | delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)}; |
2044 | } |
2081 | } |
|
|
2082 | |
|
|
2083 | =item $handle->resettls |
|
|
2084 | |
|
|
2085 | This rarely-used method simply resets and TLS state on the handle, usually |
|
|
2086 | causing data loss. |
|
|
2087 | |
|
|
2088 | One case where it may be useful is when you want to skip over the data in |
|
|
2089 | the stream but you are not interested in interpreting it, so data loss is |
|
|
2090 | no concern. |
|
|
2091 | |
|
|
2092 | =cut |
|
|
2093 | |
|
|
2094 | *resettls = \&_freetls; |
2045 | |
2095 | |
2046 | sub DESTROY { |
2096 | sub DESTROY { |
2047 | my ($self) = @_; |
2097 | my ($self) = @_; |
2048 | |
2098 | |
2049 | &_freetls; |
2099 | &_freetls; |
… | |
… | |
2172 | Probably because your C<on_error> callback is being called instead: When |
2222 | Probably because your C<on_error> callback is being called instead: When |
2173 | you have outstanding requests in your read queue, then an EOF is |
2223 | you have outstanding requests in your read queue, then an EOF is |
2174 | considered an error as you clearly expected some data. |
2224 | considered an error as you clearly expected some data. |
2175 | |
2225 | |
2176 | To avoid this, make sure you have an empty read queue whenever your handle |
2226 | To avoid this, make sure you have an empty read queue whenever your handle |
2177 | is supposed to be "idle" (i.e. connection closes are O.K.). You cna set |
2227 | is supposed to be "idle" (i.e. connection closes are O.K.). You can set |
2178 | an C<on_read> handler that simply pushes the first read requests in the |
2228 | an C<on_read> handler that simply pushes the first read requests in the |
2179 | queue. |
2229 | queue. |
2180 | |
2230 | |
2181 | See also the next question, which explains this in a bit more detail. |
2231 | See also the next question, which explains this in a bit more detail. |
2182 | |
2232 | |
… | |
… | |
2213 | some data and raises the C<EPIPE> error when the connction is dropped |
2263 | some data and raises the C<EPIPE> error when the connction is dropped |
2214 | unexpectedly. |
2264 | unexpectedly. |
2215 | |
2265 | |
2216 | The second variant is a protocol where the client can drop the connection |
2266 | The second variant is a protocol where the client can drop the connection |
2217 | at any time. For TCP, this means that the server machine may run out of |
2267 | at any time. For TCP, this means that the server machine may run out of |
2218 | sockets easier, and in general, it means you cnanot distinguish a protocl |
2268 | sockets easier, and in general, it means you cannot distinguish a protocl |
2219 | failure/client crash from a normal connection close. Nevertheless, these |
2269 | failure/client crash from a normal connection close. Nevertheless, these |
2220 | kinds of protocols are common (and sometimes even the best solution to the |
2270 | kinds of protocols are common (and sometimes even the best solution to the |
2221 | problem). |
2271 | problem). |
2222 | |
2272 | |
2223 | Having an outstanding read request at all times is possible if you ignore |
2273 | Having an outstanding read request at all times is possible if you ignore |
… | |
… | |
2275 | $handle->on_eof (undef); |
2325 | $handle->on_eof (undef); |
2276 | $handle->on_error (sub { |
2326 | $handle->on_error (sub { |
2277 | my $data = delete $_[0]{rbuf}; |
2327 | my $data = delete $_[0]{rbuf}; |
2278 | }); |
2328 | }); |
2279 | |
2329 | |
|
|
2330 | Note that this example removes the C<rbuf> member from the handle object, |
|
|
2331 | which is not normally allowed by the API. It is expressly permitted in |
|
|
2332 | this case only, as the handle object needs to be destroyed afterwards. |
|
|
2333 | |
2280 | The reason to use C<on_error> is that TCP connections, due to latencies |
2334 | The reason to use C<on_error> is that TCP connections, due to latencies |
2281 | and packets loss, might get closed quite violently with an error, when in |
2335 | and packets loss, might get closed quite violently with an error, when in |
2282 | fact all data has been received. |
2336 | fact all data has been received. |
2283 | |
2337 | |
2284 | It is usually better to use acknowledgements when transferring data, |
2338 | It is usually better to use acknowledgements when transferring data, |
… | |
… | |
2294 | C<low_water_mark> this will be called precisely when all data has been |
2348 | C<low_water_mark> this will be called precisely when all data has been |
2295 | written to the socket: |
2349 | written to the socket: |
2296 | |
2350 | |
2297 | $handle->push_write (...); |
2351 | $handle->push_write (...); |
2298 | $handle->on_drain (sub { |
2352 | $handle->on_drain (sub { |
2299 | warn "all data submitted to the kernel\n"; |
2353 | AE::log debug => "All data submitted to the kernel."; |
2300 | undef $handle; |
2354 | undef $handle; |
2301 | }); |
2355 | }); |
2302 | |
2356 | |
2303 | If you just want to queue some data and then signal EOF to the other side, |
2357 | If you just want to queue some data and then signal EOF to the other side, |
2304 | consider using C<< ->push_shutdown >> instead. |
2358 | consider using C<< ->push_shutdown >> instead. |
… | |
… | |
2388 | When you have intermediate CA certificates that your clients might not |
2442 | When you have intermediate CA certificates that your clients might not |
2389 | know about, just append them to the C<cert_file>. |
2443 | know about, just append them to the C<cert_file>. |
2390 | |
2444 | |
2391 | =back |
2445 | =back |
2392 | |
2446 | |
2393 | |
|
|
2394 | =head1 SUBCLASSING AnyEvent::Handle |
2447 | =head1 SUBCLASSING AnyEvent::Handle |
2395 | |
2448 | |
2396 | In many cases, you might want to subclass AnyEvent::Handle. |
2449 | In many cases, you might want to subclass AnyEvent::Handle. |
2397 | |
2450 | |
2398 | To make this easier, a given version of AnyEvent::Handle uses these |
2451 | To make this easier, a given version of AnyEvent::Handle uses these |
… | |
… | |
2424 | |
2477 | |
2425 | Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>. |
2478 | Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>. |
2426 | |
2479 | |
2427 | =cut |
2480 | =cut |
2428 | |
2481 | |
2429 | 1; # End of AnyEvent::Handle |
2482 | 1 |
|
|
2483 | |