… | |
… | |
14 | |
14 | |
15 | AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent |
15 | AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent |
16 | |
16 | |
17 | =cut |
17 | =cut |
18 | |
18 | |
19 | our $VERSION = 4.3; |
19 | our $VERSION = 4.331; |
20 | |
20 | |
21 | =head1 SYNOPSIS |
21 | =head1 SYNOPSIS |
22 | |
22 | |
23 | use AnyEvent; |
23 | use AnyEvent; |
24 | use AnyEvent::Handle; |
24 | use AnyEvent::Handle; |
… | |
… | |
27 | |
27 | |
28 | my $handle = |
28 | my $handle = |
29 | AnyEvent::Handle->new ( |
29 | AnyEvent::Handle->new ( |
30 | fh => \*STDIN, |
30 | fh => \*STDIN, |
31 | on_eof => sub { |
31 | on_eof => sub { |
32 | $cv->broadcast; |
32 | $cv->send; |
33 | }, |
33 | }, |
34 | ); |
34 | ); |
35 | |
35 | |
36 | # send some request line |
36 | # send some request line |
37 | $handle->push_write ("getinfo\015\012"); |
37 | $handle->push_write ("getinfo\015\012"); |
… | |
… | |
59 | treatment of characters applies to this module as well. |
59 | treatment of characters applies to this module as well. |
60 | |
60 | |
61 | All callbacks will be invoked with the handle object as their first |
61 | All callbacks will be invoked with the handle object as their first |
62 | argument. |
62 | argument. |
63 | |
63 | |
64 | =head2 SIGPIPE is not handled by this module |
|
|
65 | |
|
|
66 | SIGPIPE is not handled by this module, so one of the practical |
|
|
67 | requirements of using it is to ignore SIGPIPE (C<$SIG{PIPE} = |
|
|
68 | 'IGNORE'>). At least, this is highly recommend in a networked program: If |
|
|
69 | you use AnyEvent::Handle in a filter program (like sort), exiting on |
|
|
70 | SIGPIPE is probably the right thing to do. |
|
|
71 | |
|
|
72 | =head1 METHODS |
64 | =head1 METHODS |
73 | |
65 | |
74 | =over 4 |
66 | =over 4 |
75 | |
67 | |
76 | =item B<new (%args)> |
68 | =item B<new (%args)> |
… | |
… | |
92 | Set the callback to be called when an end-of-file condition is detected, |
84 | Set the callback to be called when an end-of-file condition is detected, |
93 | i.e. in the case of a socket, when the other side has closed the |
85 | i.e. in the case of a socket, when the other side has closed the |
94 | connection cleanly. |
86 | connection cleanly. |
95 | |
87 | |
96 | For sockets, this just means that the other side has stopped sending data, |
88 | For sockets, this just means that the other side has stopped sending data, |
97 | you can still try to write data, and, in fact, one can return from the eof |
89 | you can still try to write data, and, in fact, one can return from the EOF |
98 | callback and continue writing data, as only the read part has been shut |
90 | callback and continue writing data, as only the read part has been shut |
99 | down. |
91 | down. |
100 | |
92 | |
101 | While not mandatory, it is I<highly> recommended to set an eof callback, |
93 | While not mandatory, it is I<highly> recommended to set an EOF callback, |
102 | otherwise you might end up with a closed socket while you are still |
94 | otherwise you might end up with a closed socket while you are still |
103 | waiting for data. |
95 | waiting for data. |
104 | |
96 | |
105 | If an EOF condition has been detected but no C<on_eof> callback has been |
97 | If an EOF condition has been detected but no C<on_eof> callback has been |
106 | set, then a fatal error will be raised with C<$!> set to <0>. |
98 | set, then a fatal error will be raised with C<$!> set to <0>. |
… | |
… | |
263 | You can also provide your own TLS connection object, but you have |
255 | You can also provide your own TLS connection object, but you have |
264 | to make sure that you call either C<Net::SSLeay::set_connect_state> |
256 | to make sure that you call either C<Net::SSLeay::set_connect_state> |
265 | or C<Net::SSLeay::set_accept_state> on it before you pass it to |
257 | or C<Net::SSLeay::set_accept_state> on it before you pass it to |
266 | AnyEvent::Handle. |
258 | AnyEvent::Handle. |
267 | |
259 | |
|
|
260 | B<IMPORTANT:> since Net::SSLeay "objects" are really only integers, |
|
|
261 | passing in the wrong integer will lead to certain crash. This most often |
|
|
262 | happens when one uses a stylish C<< tls => 1 >> and is surprised about the |
|
|
263 | segmentation fault. |
|
|
264 | |
268 | See the C<< ->starttls >> method for when need to start TLS negotiation later. |
265 | See the C<< ->starttls >> method for when need to start TLS negotiation later. |
269 | |
266 | |
270 | =item tls_ctx => $ssl_ctx |
267 | =item tls_ctx => $ssl_ctx |
271 | |
268 | |
272 | Use the given C<Net::SSLeay::CTX> object to create the new TLS connection |
269 | Use the given C<Net::SSLeay::CTX> object to create the new TLS connection |
… | |
… | |
334 | |
331 | |
335 | $! = $errno; |
332 | $! = $errno; |
336 | |
333 | |
337 | if ($self->{on_error}) { |
334 | if ($self->{on_error}) { |
338 | $self->{on_error}($self, $fatal); |
335 | $self->{on_error}($self, $fatal); |
339 | } else { |
336 | } elsif ($self->{fh}) { |
340 | Carp::croak "AnyEvent::Handle uncaught error: $!"; |
337 | Carp::croak "AnyEvent::Handle uncaught error: $!"; |
341 | } |
338 | } |
342 | } |
339 | } |
343 | |
340 | |
344 | =item $fh = $handle->fh |
341 | =item $fh = $handle->fh |
… | |
… | |
382 | } |
379 | } |
383 | |
380 | |
384 | =item $handle->autocork ($boolean) |
381 | =item $handle->autocork ($boolean) |
385 | |
382 | |
386 | Enables or disables the current autocork behaviour (see C<autocork> |
383 | Enables or disables the current autocork behaviour (see C<autocork> |
387 | constructor argument). |
384 | constructor argument). Changes will only take effect on the next write. |
388 | |
385 | |
389 | =cut |
386 | =cut |
|
|
387 | |
|
|
388 | sub autocork { |
|
|
389 | $_[0]{autocork} = $_[1]; |
|
|
390 | } |
390 | |
391 | |
391 | =item $handle->no_delay ($boolean) |
392 | =item $handle->no_delay ($boolean) |
392 | |
393 | |
393 | Enables or disables the C<no_delay> setting (see constructor argument of |
394 | Enables or disables the C<no_delay> setting (see constructor argument of |
394 | the same name for details). |
395 | the same name for details). |
… | |
… | |
550 | ->($self, @_); |
551 | ->($self, @_); |
551 | } |
552 | } |
552 | |
553 | |
553 | if ($self->{tls}) { |
554 | if ($self->{tls}) { |
554 | $self->{_tls_wbuf} .= $_[0]; |
555 | $self->{_tls_wbuf} .= $_[0]; |
|
|
556 | |
555 | &_dotls ($self); |
557 | &_dotls ($self); |
556 | } else { |
558 | } else { |
557 | $self->{wbuf} .= $_[0]; |
559 | $self->{wbuf} .= $_[0]; |
558 | $self->_drain_wbuf; |
560 | $self->_drain_wbuf; |
559 | } |
561 | } |
… | |
… | |
1142 | } |
1144 | } |
1143 | }; |
1145 | }; |
1144 | |
1146 | |
1145 | =item json => $cb->($handle, $hash_or_arrayref) |
1147 | =item json => $cb->($handle, $hash_or_arrayref) |
1146 | |
1148 | |
1147 | Reads a JSON object or array, decodes it and passes it to the callback. |
1149 | Reads a JSON object or array, decodes it and passes it to the |
|
|
1150 | callback. When a parse error occurs, an C<EBADMSG> error will be raised. |
1148 | |
1151 | |
1149 | If a C<json> object was passed to the constructor, then that will be used |
1152 | If a C<json> object was passed to the constructor, then that will be used |
1150 | for the final decode, otherwise it will create a JSON coder expecting UTF-8. |
1153 | for the final decode, otherwise it will create a JSON coder expecting UTF-8. |
1151 | |
1154 | |
1152 | This read type uses the incremental parser available with JSON version |
1155 | This read type uses the incremental parser available with JSON version |
… | |
… | |
1169 | my $rbuf = \$self->{rbuf}; |
1172 | my $rbuf = \$self->{rbuf}; |
1170 | |
1173 | |
1171 | my $json = $self->{json} ||= JSON->new->utf8; |
1174 | my $json = $self->{json} ||= JSON->new->utf8; |
1172 | |
1175 | |
1173 | sub { |
1176 | sub { |
|
|
1177 | eval { |
1174 | my $ref = $json->incr_parse ($self->{rbuf}); |
1178 | my $ref = $json->incr_parse ($self->{rbuf}); |
1175 | |
1179 | |
1176 | if ($ref) { |
1180 | if ($ref) { |
|
|
1181 | $self->{rbuf} = $json->incr_text; |
|
|
1182 | $json->incr_text = ""; |
|
|
1183 | $cb->($self, $ref); |
|
|
1184 | |
|
|
1185 | 1 |
|
|
1186 | } else { |
|
|
1187 | $self->{rbuf} = ""; |
|
|
1188 | () |
|
|
1189 | } |
|
|
1190 | |
|
|
1191 | 1 |
|
|
1192 | } or do { |
|
|
1193 | # error case |
|
|
1194 | $json->incr_skip; |
|
|
1195 | |
1177 | $self->{rbuf} = $json->incr_text; |
1196 | $self->{rbuf} = $json->incr_text; |
1178 | $json->incr_text = ""; |
1197 | $json->incr_text = ""; |
1179 | $cb->($self, $ref); |
|
|
1180 | |
1198 | |
1181 | 1 |
1199 | $self->_error (&Errno::EBADMSG); |
1182 | } else { |
|
|
1183 | $self->{rbuf} = ""; |
|
|
1184 | () |
|
|
1185 | } |
1200 | }; |
1186 | } |
1201 | } |
1187 | }; |
1202 | }; |
1188 | |
1203 | |
1189 | =item storable => $cb->($handle, $ref) |
1204 | =item storable => $cb->($handle, $ref) |
1190 | |
1205 | |
… | |
… | |
1291 | if ($len > 0) { |
1306 | if ($len > 0) { |
1292 | $self->{_activity} = AnyEvent->now; |
1307 | $self->{_activity} = AnyEvent->now; |
1293 | |
1308 | |
1294 | if ($self->{tls}) { |
1309 | if ($self->{tls}) { |
1295 | Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf); |
1310 | Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf); |
|
|
1311 | |
1296 | &_dotls ($self); |
1312 | &_dotls ($self); |
1297 | } else { |
1313 | } else { |
1298 | $self->_drain_rbuf unless $self->{_in_drain}; |
1314 | $self->_drain_rbuf unless $self->{_in_drain}; |
1299 | } |
1315 | } |
1300 | |
1316 | |
… | |
… | |
1308 | } |
1324 | } |
1309 | }); |
1325 | }); |
1310 | } |
1326 | } |
1311 | } |
1327 | } |
1312 | |
1328 | |
|
|
1329 | # poll the write BIO and send the data if applicable |
1313 | sub _dotls { |
1330 | sub _dotls { |
1314 | my ($self) = @_; |
1331 | my ($self) = @_; |
1315 | |
1332 | |
1316 | my $buf; |
1333 | my $tmp; |
1317 | |
1334 | |
1318 | if (length $self->{_tls_wbuf}) { |
1335 | if (length $self->{_tls_wbuf}) { |
1319 | while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { |
1336 | while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { |
1320 | substr $self->{_tls_wbuf}, 0, $len, ""; |
1337 | substr $self->{_tls_wbuf}, 0, $tmp, ""; |
1321 | } |
1338 | } |
1322 | } |
1339 | } |
1323 | |
1340 | |
1324 | while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { |
1341 | while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) { |
1325 | unless (length $buf) { |
1342 | unless (length $tmp) { |
1326 | # let's treat SSL-eof as we treat normal EOF |
1343 | # let's treat SSL-eof as we treat normal EOF |
1327 | delete $self->{_rw}; |
1344 | delete $self->{_rw}; |
1328 | $self->{_eof} = 1; |
1345 | $self->{_eof} = 1; |
1329 | &_freetls; |
1346 | &_freetls; |
1330 | } |
1347 | } |
1331 | |
1348 | |
1332 | $self->{rbuf} .= $buf; |
1349 | $self->{rbuf} .= $tmp; |
1333 | $self->_drain_rbuf unless $self->{_in_drain}; |
1350 | $self->_drain_rbuf unless $self->{_in_drain}; |
1334 | $self->{tls} or return; # tls session might have gone away in callback |
1351 | $self->{tls} or return; # tls session might have gone away in callback |
1335 | } |
1352 | } |
1336 | |
1353 | |
1337 | my $err = Net::SSLeay::get_error ($self->{tls}, -1); |
1354 | $tmp = Net::SSLeay::get_error ($self->{tls}, -1); |
1338 | |
1355 | |
1339 | if ($err!= Net::SSLeay::ERROR_WANT_READ ()) { |
1356 | if ($tmp != Net::SSLeay::ERROR_WANT_READ ()) { |
1340 | if ($err == Net::SSLeay::ERROR_SYSCALL ()) { |
1357 | if ($tmp == Net::SSLeay::ERROR_SYSCALL ()) { |
1341 | return $self->_error ($!, 1); |
1358 | return $self->_error ($!, 1); |
1342 | } elsif ($err == Net::SSLeay::ERROR_SSL ()) { |
1359 | } elsif ($tmp == Net::SSLeay::ERROR_SSL ()) { |
1343 | return $self->_error (&Errno::EIO, 1); |
1360 | return $self->_error (&Errno::EIO, 1); |
1344 | } |
1361 | } |
1345 | |
1362 | |
1346 | # all others are fine for our purposes |
1363 | # all other errors are fine for our purposes |
1347 | } |
1364 | } |
1348 | |
1365 | |
1349 | while (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { |
1366 | while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) { |
1350 | $self->{wbuf} .= $buf; |
1367 | $self->{wbuf} .= $tmp; |
1351 | $self->_drain_wbuf; |
1368 | $self->_drain_wbuf; |
1352 | } |
1369 | } |
1353 | } |
1370 | } |
1354 | |
1371 | |
1355 | =item $handle->starttls ($tls[, $tls_ctx]) |
1372 | =item $handle->starttls ($tls[, $tls_ctx]) |
… | |
… | |
1376 | sub starttls { |
1393 | sub starttls { |
1377 | my ($self, $ssl, $ctx) = @_; |
1394 | my ($self, $ssl, $ctx) = @_; |
1378 | |
1395 | |
1379 | require Net::SSLeay; |
1396 | require Net::SSLeay; |
1380 | |
1397 | |
1381 | Carp::croak "it is an error to call starttls more than once on an Anyevent::Handle object" |
1398 | Carp::croak "it is an error to call starttls more than once on an AnyEvent::Handle object" |
1382 | if $self->{tls}; |
1399 | if $self->{tls}; |
1383 | |
1400 | |
1384 | if ($ssl eq "accept") { |
1401 | if ($ssl eq "accept") { |
1385 | $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); |
1402 | $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); |
1386 | Net::SSLeay::set_accept_state ($ssl); |
1403 | Net::SSLeay::set_accept_state ($ssl); |
… | |
… | |
1475 | @linger = (); |
1492 | @linger = (); |
1476 | }); |
1493 | }); |
1477 | } |
1494 | } |
1478 | } |
1495 | } |
1479 | |
1496 | |
|
|
1497 | =item $handle->destroy |
|
|
1498 | |
|
|
1499 | Shuts down the handle object as much as possible - this call ensures that |
|
|
1500 | no further callbacks will be invoked and resources will be freed as much |
|
|
1501 | as possible. You must not call any methods on the object afterwards. |
|
|
1502 | |
|
|
1503 | Normally, you can just "forget" any references to an AnyEvent::Handle |
|
|
1504 | object and it will simply shut down. This works in fatal error and EOF |
|
|
1505 | callbacks, as well as code outside. It does I<NOT> work in a read or write |
|
|
1506 | callback, so when you want to destroy the AnyEvent::Handle object from |
|
|
1507 | within such an callback. You I<MUST> call C<< ->destroy >> explicitly in |
|
|
1508 | that case. |
|
|
1509 | |
|
|
1510 | The handle might still linger in the background and write out remaining |
|
|
1511 | data, as specified by the C<linger> option, however. |
|
|
1512 | |
|
|
1513 | =cut |
|
|
1514 | |
|
|
1515 | sub destroy { |
|
|
1516 | my ($self) = @_; |
|
|
1517 | |
|
|
1518 | $self->DESTROY; |
|
|
1519 | %$self = (); |
|
|
1520 | } |
|
|
1521 | |
1480 | =item AnyEvent::Handle::TLS_CTX |
1522 | =item AnyEvent::Handle::TLS_CTX |
1481 | |
1523 | |
1482 | This function creates and returns the Net::SSLeay::CTX object used by |
1524 | This function creates and returns the Net::SSLeay::CTX object used by |
1483 | default for TLS mode. |
1525 | default for TLS mode. |
1484 | |
1526 | |
… | |
… | |
1516 | |
1558 | |
1517 | |
1559 | |
1518 | =head1 NONFREQUENTLY ASKED QUESTIONS |
1560 | =head1 NONFREQUENTLY ASKED QUESTIONS |
1519 | |
1561 | |
1520 | =over 4 |
1562 | =over 4 |
|
|
1563 | |
|
|
1564 | =item I C<undef> the AnyEvent::Handle reference inside my callback and |
|
|
1565 | still get further invocations! |
|
|
1566 | |
|
|
1567 | That's because AnyEvent::Handle keeps a reference to itself when handling |
|
|
1568 | read or write callbacks. |
|
|
1569 | |
|
|
1570 | It is only safe to "forget" the reference inside EOF or error callbacks, |
|
|
1571 | from within all other callbacks, you need to explicitly call the C<< |
|
|
1572 | ->destroy >> method. |
|
|
1573 | |
|
|
1574 | =item I get different callback invocations in TLS mode/Why can't I pause |
|
|
1575 | reading? |
|
|
1576 | |
|
|
1577 | Unlike, say, TCP, TLS connections do not consist of two independent |
|
|
1578 | communication channels, one for each direction. Or put differently. The |
|
|
1579 | read and write directions are not independent of each other: you cannot |
|
|
1580 | write data unless you are also prepared to read, and vice versa. |
|
|
1581 | |
|
|
1582 | This can mean than, in TLS mode, you might get C<on_error> or C<on_eof> |
|
|
1583 | callback invocations when you are not expecting any read data - the reason |
|
|
1584 | is that AnyEvent::Handle always reads in TLS mode. |
|
|
1585 | |
|
|
1586 | During the connection, you have to make sure that you always have a |
|
|
1587 | non-empty read-queue, or an C<on_read> watcher. At the end of the |
|
|
1588 | connection (or when you no longer want to use it) you can call the |
|
|
1589 | C<destroy> method. |
1521 | |
1590 | |
1522 | =item How do I read data until the other side closes the connection? |
1591 | =item How do I read data until the other side closes the connection? |
1523 | |
1592 | |
1524 | If you just want to read your data into a perl scalar, the easiest way |
1593 | If you just want to read your data into a perl scalar, the easiest way |
1525 | to achieve this is by setting an C<on_read> callback that does nothing, |
1594 | to achieve this is by setting an C<on_read> callback that does nothing, |
… | |
… | |
1535 | |
1604 | |
1536 | The reason to use C<on_error> is that TCP connections, due to latencies |
1605 | The reason to use C<on_error> is that TCP connections, due to latencies |
1537 | and packets loss, might get closed quite violently with an error, when in |
1606 | and packets loss, might get closed quite violently with an error, when in |
1538 | fact, all data has been received. |
1607 | fact, all data has been received. |
1539 | |
1608 | |
1540 | It is usually better to use acknowledgements when transfering data, |
1609 | It is usually better to use acknowledgements when transferring data, |
1541 | to make sure the other side hasn't just died and you got the data |
1610 | to make sure the other side hasn't just died and you got the data |
1542 | intact. This is also one reason why so many internet protocols have an |
1611 | intact. This is also one reason why so many internet protocols have an |
1543 | explicit QUIT command. |
1612 | explicit QUIT command. |
1544 | |
|
|
1545 | |
1613 | |
1546 | =item I don't want to destroy the handle too early - how do I wait until |
1614 | =item I don't want to destroy the handle too early - how do I wait until |
1547 | all data has been written? |
1615 | all data has been written? |
1548 | |
1616 | |
1549 | After writing your last bits of data, set the C<on_drain> callback |
1617 | After writing your last bits of data, set the C<on_drain> callback |