AnyEvent-Handle-UDP
view release on metacpan or search on metacpan
Revision history for AnyEvent-Handle-UDP
0.050 2020-03-26 23:05:21+01:00 Europe/Amsterdam
- Add on_bind and on_connect callbacks
- Allow injecting the socket into the handle
- Allow destroy to be called in on_recv callback
- Fix error handling in address lookup
0.049 2018-05-16 23:53:00+02:00 Europe/Amsterdam
- Remove namespace::clean dependency
0.048 2017-01-12 22:32:02+01:00 Europe/Amsterdam
- Fixed timeout handling in destroy
lib/AnyEvent/Handle/UDP.pm view on Meta::CPAN
If true will enable quick reuse of the bound address
=head2 timeout
=head2 rtimeout
=head2 wtimeout
If non-zero, then these enables an "inactivity" timeout: whenever this many seconds pass without a successful read or write on the underlying file handle (or a call to C<timeout_reset>), the on_timeout callback will be invoked (and if that one is mis...
There are three variants of the timeouts that work independently of each other, for both read and write (triggered when nothing was read OR written), just read (triggered when nothing was read), and just write: timeout, rtimeout and wtimeout, with co...
Note that timeout processing is active even when you do not have any outstanding read or write requests: If you plan to keep the connection idle then you should disable the timeout temporarily or ignore the timeout in the corresponding on_timeout cal...
Calling C<clear_timeout> (or setting it to zero, which does the same) disables the corresponding timeout.
=head2 on_timeout
=head2 on_rtimeout
=head2 on_wtimeout
( run in 1.085 second using v1.01-cache-2.11-cpan-d6f9594c0a5 )